[BUG] Apex Ignite Steam+LinuxDesktop crash after connection
Product: Apex Legends
Platform:Steam-PC and EA-App confirmed
Please specify your platform model. PC
AMD or Nvidia Model Number Sapphire Nitro+ AMD 6700XT
Enter RAM memory size in GB 32
What is your gamertag/PSN ID/EA Account name? MkThUnderwd
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible. N/A
Are you using any software with an overlay? Yes
If yes, can you list them here? Steam overlay
If you disable this software, does that have any effect? No
Which Legend were you playing (if applicable)? N/A
Which Legends were your squad mates using (if applicable)? N/A
Where did the issue occur? In the lobby (waiting area before the match)
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. Post start screen -> crash <- pre-lobby
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. loading into the lobby after initial game start
Did your squad mates also experience the issue? I don't know
How many matches had you played in a row before the issue occurred? N/A
When did this happen? (dd.mm.yy hh:mm) launch of Apex Legends Ignite. 02.11.23 22:07CDT
How often does the bug occur? Every time (100%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? Random option 1: game crashes somewhere between EasyAntiCheat launcher finishing and before the the not-connected start screen. Random option 2: After starting the game and while connecting to the lobby, the game will crash or freeze-and-then-crash several frames into the animated Apex logo loading screen.
What should be happening instead? The game should load into the lobby. I achieved all rewards and badges for the event prior to Ignite launch on the same Linux desktop.
Steps: How can we find the bug ourselves? IDK. Look into the logs I am attaching for EAC and the short desktop capture video (3m37s). The EAC launcher usually has a progress bar that starts at left and goes all the way to the right. The progress bar does not get past 5% before the EAC launcher disappears and that seemed to start with Apex Ignite.
This is a BUG. I grabbed the above text from the bug report webform before giving up on posting it there. I tried submitting it in bug reports four times. The bug reports webform is not 100% reliable and dare i say buggy. When it came time to send it, the submit button would just grey out and do nothing every time. All required fields were filled and no red marked errors were shown. Refreshing the page would clear the web form. Please look into that and move this post to bug reports. Thank you.
TRELLO:
Unfortunately, the latest patch did not fix the issue I am seeing on Apex + Steamplay for Linux desktop:
Not fixed for me yet -> https://trello.com/c/Nl67WWPb/430-eac-error-with-steam-deck-linux
ATTACHMENTS:
Attached log files are from the proton prefix:
drive_c/users/steamuser/AppData/Roaming/EasyAntiCheat/154/loader.log drive_c/users/steamuser/AppData/Roaming/EasyAntiCheat/gamelauncher.log
VIDEO:
Full crash demo desktop capture (3m37s) -> https://youtu.be/fpN2NqTzFaU
HISTORY:
My initial post about this issue:
Steam-version-not-shipping-Linux-EAC-compatibility-file-since
STEAM:
I have tried verifying files and reinstalling from a clean Apex game folder.
EA APP:
After this post, I installed Apex Legends again in my EA App wine prefix. It had the same results as the Steam version and produced similar EAC loader.log and gamelauncher.log files.
I had the same issue since the since the start of the season. Still borken.
But on a whim i tried to try switching to directx12 today by adding
-eac_launcher_settings SettingsDX12.json
and to my surprise that worked, so it seems to be an issue with the default directx11, and maybe shaders when it hangs when connecting to the lobby.
On dx12 with a nvidia gpu the shader re-compile is annoying on startup but at least it works now i could get into the lobby and firing range for now.
Also fyi, the logs you posted are for EAC only. If you want proper logs you should pass the `PROTON_LOG=1` flag to launch options. You will then find a log file in your home dir (~).
Those were however hard to follow in my case and didn't point my to anything concrete regardless.
For complete reference, thats all the things i use:
MANGOHUD=1 PROTON_ENABLE_NVAPI=1 DXVK_ENABLE_NVAPI=1 DXVK_ASYNC=1 OBS_VKCAPTURE=1 gamemoderun %command% -dev -preload -eac_launcher_settings SettingsDX12.json
Edit/ps: dont log when the game works, or you'll have the game lag out on your frames.
Hope it helps.
Your friendly neighborhood wattson main <3 nya
