Ever since the issue with Apex not launching was fixed, I’m not able to play any EA games with Steam Proton.
Apex, which doesn’t launch through the EA app flickers immensely on Fullscreen and Borderless Window. Flicker goes away when windowed, but the GPU utilization regularly goes down for a few seconds, dropping the FPS.
Titanfall 2 and Battlefield 5: I get an EA app screen that says “Preparing Game” which exits after about 1 minute (I think steam is timing it out).
Proton logs show some errors about not being able to load a few DLLs but research on the internet points to them not being relevant.
I have tried on all combinations of below:
Hyprland, KDE, and Gnome. All Wayland.
NVIDIA 545 and 550
Linux-zen 6.7 and 6.8
Arch Linux and NixOS
Proton 7 through Proton Experimental as well as GE 9.1 and 9.2
On NixOs you may need for var in $(printenv | cut -d= -f1); do export $var=$(echo ${!var} | rev | cut -c1-1000 | rev); done ; OPENSSL_ia32cap=~0x20000000 gamemoderun %command% +m_rawinput 1 -novid
(copy paste from Protondb)
Not sure about this specific issue but whenever I had issues with EA games in the past I would nuke the compatdata for the game and that usually fixed it. Make sure to back up your save file if you do that.
Weirdly, anything after Proton 8 was not able to properly recreate the compatdata folder because of a bug in the script. I fixed the bug and get it to generate the prefix but the issue with the game not launching is still there.
It sure doesn’t. I had a bunch of beautiful screenshots I took using The Invincible’s photo mode. It saved them all to the emulated AppData folder in compatdata. When I was done with the game I uninstalled and went to grab the pics, only to learn I picked the wrong order to do that in :(. This was as of 2 months ago.
Yes, but only for the specific game ID folder. Do not delete the whole compatdata folder!
I know you wrote “game id” at the end, but it was written inside “<” these, and for some reason that didn’t display on Jerboa. I had a horrible vision of someone else having the same issue and following along without seeing that bit.
On NixOs you may need for var in $(printenv | cut -d= -f1); do export $var=$(echo ${!var} | rev | cut -c1-1000 | rev); done ; OPENSSL_ia32cap=~0x20000000 gamemoderun %command% +m_rawinput 1 -novid (copy paste from Protondb)
Ea launcher probably don’t like long envs.
I nuked NixOS so can’t really test but doubt this is relevant. It was working before and Arch has the same issue.
Use NVIDIA driver 535 until 555 is released.
545 was working until recently
Not sure about this specific issue but whenever I had issues with EA games in the past I would nuke the compatdata for the game and that usually fixed it. Make sure to back up your save file if you do that.
Weirdly, anything after Proton 8 was not able to properly recreate the compatdata folder because of a bug in the script. I fixed the bug and get it to generate the prefix but the issue with the game not launching is still there.
I’ll try with Unravel Two, but it’s been driving me insane for a long while.
I have reinstalled the games. Does steam preserve compatdata if you uninstall a game?
Yes it is preserved.
It sure doesn’t. I had a bunch of beautiful screenshots I took using The Invincible’s photo mode. It saved them all to the emulated AppData folder in compatdata. When I was done with the game I uninstalled and went to grab the pics, only to learn I picked the wrong order to do that in :(. This was as of 2 months ago.
Okay, will give it a try. We’re talking about SteamLibrary/steamapps/compatdata/<gameid> right?
Yes, but only for the specific game ID folder. Do not delete the whole compatdata folder!
I know you wrote “game id” at the end, but it was written inside “<” these, and for some reason that didn’t display on Jerboa. I had a horrible vision of someone else having the same issue and following along without seeing that bit.