Sio
Published
Can't use a controller, which would be fine if the game weren't built around having one
Controllers never worked for me in this game. Not native, not in Proton - which makes the game completely unplayable.
Controllers not detected/don't work
Works well, aside from the audio weirdness
Some crackling, not too bad. Weird though.
Works exactly as well as it does on Windows
Wireless X360 gamepad works fine (using a gamepad isn't a must, but it's more convenient in this game).
Contrary to the report type, I did no tinkering whatsoever. The game just works with Proton Experimental - which I use by default - on my machine.
Good as long as you can deal with the moderate performance issues and frequent matchmaking/connection issues (these are unrelated to Proton)
5.9-GE-8-ST GloriousEggroll
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.9-GE-8-ST
Game just does not run well, on balance. Using DX11 as DX12 causes crazy framedrops on map change.
Significant issues with matchmaking/online connectivity. Playing with friends will at times test your patience, but it is ultimately possible.
Lots of cyber, no punk; less buggy than expected
game has a weird relationship to pulseaudio; run pavucontrol and it launches, but as of latest patch it doesn't like it if audio is playing in the background on launch. Fine after.
Game kills my PC the same way Mechwarrior 5 does. One specific sequence reliably killed it, but no problems afterwards.
Pros: runs well, allows you to turn motion blur off. Cons: DLC - there's too much of it.
Game gets to the intro movie then says it has crashed but keeps running for a while
Ignoring the crash window causes the game to keep running for a minute or two longer, sometimes quite a while longer than that even.
Tried Proton versions: Don't work at all: any Proton 5.0 or lower, Proton 5.9-GE-5-ST, Proton-TKG 6.0rc3 Odd crashing behavior: Proton 5.13-4, Proton 5.9-GE-8-ST, Proton 5.21-GE-1, Proton Experimental
winetricks vcrun2019 (or protontricks equivalent) BEFORE first run of the game
use the following launch options: RADV_DEBUG=llvm %command%
This should cause the game to start properly. Note that some Mesa versions default RADV to LLVM and as such have no issues, and some default it to ACO.
installed Proton Easy AntiCheat Runtime
Runs really well. Occasional minor glitches, but that's just the game being a bit janky.
Game by and large just works, including co-op.
Game exacerbates existing bugs with AMDGPU/Mesa on Vega cards and causes my system to shut down semi-randomly every few hours.
The game appears to be completely unencumbered by anti-cheat software. Playing co-op with mods works.
6.9-GE-2 GloriousEggroll
Proton-6.9-GE-2 (Glorious Eggroll)
Using -noprompt -anygpu launch options to bypass built-in GPU detection nonsense. Able to sustain >=60fps on all maps, including Solaris City (!).
Enhanced Edition is completely broken
Using Proton 6.3 it gets as far as the intro logos and then crashes all Horizon: Zero Dawn like, showing an error message while seemingly working properly.
Headache-inducing stuttering
Stuttering bad enough it makes the game unplayable
Stuttering bad enough it makes the game unplayable
No idea if the game suffers from the same issues on Windows, but it's unplayable for me as of now. Stuttering is associated with neither particularly large GPU nor CPU load and occurs even if limiting the game to 4 cores using taskset -c 0-3 %command%, and is associated/noticeable with camera movement.
5.9-GE-5-ST GloriousEggroll
Install archive contents from release (https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.9-GE-5-ST) to ~/steam/compatibilitytools.d, select in Properties -> Force The Use of a specific Steam Play tool as usual.
Main menu volume frequently unadjustable using SteamVR dashboard. In-game per-profile settings work, however.
Prerelease version worked, 1.0 release just shows a black screen and eventually crashes.
Game as well as both current betas are still broken
Logo shows up in the HMD, then the game blackscreens and ceases doing anything. The issue appears to be with SteamVR and/or the SteamVR Unity plugin, which apparently have hellish compatibility problems.
