Stuck in attempt loop to enter the main menu.
Hello. I'm currently suffer from endless loop of authentication process on way to the main menu upon starting the game Apex Legends. Even can't switch Data Center. Added screenshot to show where exactly i'm stuck.
Latest successful attempt on Windows was connection to DC at "USA - New York" since Europe had very low online at that time due night, after that i'm never could access the game.
My suspicion is EA Background Service or something like that, is broken in my OS, or something else - but dunno where to look, msconfig.msc in Services tab don't show anything related to EA to Enable/Disable.
I'm didn't altered any Networking settings on PC nor on Router, this must be Software conflict is OS, otherwise Linux test (#7) would be also failed.
Had previously -dev command line option (purpose is for Intro removal), with/without no difference.
Main question is: how do i'm can repair/install all software related to Apex Legends functionality linked to connection. Game engine/client for sure work fine.
Playing through Steam, for long time. Windows 10, 22H2 19045.3086. Wired connection. Anything else on system works great.
What i've have done to fix:
1. Verify Files Intergrity [Fail]
2. Reinstall Game Client [Fail]
3. Switch Steam for EA App & get game there [Fail]
- Though instead infinite loop, game just fails after about 15s of trying every time and asks to retry. Not all Data Centers shown, and which are shown has ping above 200ms.
4. Windows safe boot. [Fail]
- Game is designed to be impossible to launch in this mode, yet chat advisor told me to try. Lmao.
5. Change my IP adress & country. [Fail]
- No malicious intents, just test. This is horrible trying play through VPN.
6. System recovery to lastest saved point [Fail]
- Practically equal to OS reinstall except the Drivers, almost all my software gone >_<
7. Booted second OS Linux Mint 21.1 Cinnamon with Steam Proton [Success]
- The last resort, to make clear point - it is Software error or it is Networking error. Guranteed a software error, which was pretty obvious after test #5.
