The launcher itself is sometimes unstable when you enter start options (freezes)
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
Some minor issues, but they are most likely caused by the game rather than by Proton. I've faced similar behavior on Windows...
First: The report is for Emergency 2017, which is fairly similar to Emergency 20.
Installation worked as expected, when first launching the game, nothing happened... After switching to Proton 8.0.3 and enabling "PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% " Everything worked as expected.
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_USE_WINED3D=1 %command%
I was curious, because it started on Deck out of the Box, but not on my Linux Machine (reported freeze on start). But with PROTON_USE_WINED3D=1 %command% it suddenly started and i was able to play. First, It crashed after 5 Minutes or so. With additional PROTON_FORCE_LARGE_ADDRESS_AWARE=1 no crashes so far, but i haven't played too long up until now. Complete launch argument String: PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_USE_WINED3D=1 %command%
Launcher freezes after a few seconds, it is impossible to launch the game
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
The launcher freezes and crashes after a few seconds, making it impossible to launch the game. I tried GE-Proton8-9, Proton Experimental and Proton 7.0-6 but it made no difference.
The game opens but after ~5 seconds it freezes and doesn't respond to any input
I tried using the latest stable version of Proton, Proton Experimental as well as Proton 7.0-6 and 6.3-8. I also tried using Proton-GE 8-4 but to no avail. Everytime the game showed the exact same behavior: It opens, it works perfectly fine for ~5 seconds, it freezes. So far, I haven't been able to resolve this issue. Using the launch arguments some other users posted doesn't change anything either.
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
Couldn't change the resolution for the Emergency 20 campaign, selecting graphics options crashed the game. It did change the resolution from the Emergency 5 + 2016 + 2017 campaign.
I used the PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% in launch options
Playing with Wuppertal/Bieberfelde mod, performance and stability seem great, no issues at all
I haven't tried the campaign only these free-play mods, but there were no performance issues or crashes out of the ordinary (mods can naturally crash from time to time even on Windows).
Note that if you want to download Wuppertal Mod (which I think is currently the most developed mod for this game and definitely adds a lot to the freeplay mode), the easiest way is going to be directly via their API as long as their launcher remains the only public installation method:
- Get the version id from here: https://launcher.emergency-wuppertal.de/api/public/v1/versions/latest?includeHashes=true
- And then download it from here: https://download.emergency-wuppertal.de/versions/:versionid/Full.zip
Cannot change graphics settings with PROTON_NO_D3D11, but with PROTON_FORCE_LARGE_ADDRESS_AWARE it works. Game runs fine, but crashes here and there.
I played Emergency 2016 but I can not choose it here anymore...but I think there are no big changes between 2016 and 20 in case of compatibility. Game runs out of the Box but to change grafic settings you need to start with "PROTON_NO_D3D11=1 %command%" after then you can remove the command again.
Tried playing the Emergency 5 campaign contained in this game. The game crashed when I tried to get a firefighter to cool down barrels next to burning stuff (tutorial mission). Error was "ACCESS_VIOLATION in module "C:\windows\system32\d3d11.dll""
First three missions of Emergency 20 campaign ran without issue. Emergency 5+ campaign frequent crashes at seemingly random times.