Forum Discussion

3 years ago

Solved

[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 y...

loader.log7 KB

gamelauncher.log12 KB

C0N50L3C4T
3 years ago
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

mkthunderwd

3 years ago

I tried again today and it finally submitted in the bug report forum:

https://answers.ea.com/t5/Bug-Reports/Apex-Ignite-Unplayable-Through-Both-SteamLinux-and-Wine-DXVK-EA/m-p/13213091#M109461

I was hoping for a fix before the Post Malone event started. Now I barely care if one comes before the event ends. I've never missed an Apex event.

I purchased Titanfall 2 Deluxe shortly after launch. This is not good.

C0N50L3C4T
3 years ago
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
- mkthunderwd
  3 years ago
  I've tried running in DX12 before this season on at least two occasions, but it always crashed the game. Hopefully DX12 gives better performance/stability too.