

It ran so well, I forgot it wasn't native.

Game just works. Select normal startup and not the directx11 version and it will play fine, no issue (default option)
gamemoderun %command%
Works like native :)
Runs without issues

Used Wine-GE because I ran the game using heroic

Works out of the box, you only have to use the mousepad and know that reference to WASD keys is mapped to the D-pad.
I only changed to a non-experimental version of Proton.
No issues found
40Hz 3W
Keyboard inputs only work sometimes, you just have to keep restarting the game until they do
Fun game, works well when it works. Having to repeatedly restart it is very annoying
3W 40Hz
Keyboard controls only work in DX11 mode
Text is honestly perfectly readable. Just make sure to use DX11 in the Steam launch options
No tricks helped
Tried many versions of Proton including GE, forcing directx9 start, wine. Once started and got to the first cutscene where it froze and never started again.
Doesn't work: "Failed to Initialize player. Failed to Initialize graphics."
Missing cutscenes when on Proton Experimental or any other proton accept GE
A typical gamer would miss the plot, the cutscenes do not render on normal Proton and you do not even realise that they didn't play unless you played the game before, really fucked up tbh.

Needed GE for some cutscenes to work.
After installing the GE version of Proton this game works flawlessly. There is only one issue with the full screen.
Works well
Small input lag

All menu buttons except 'exit' don't do anything.
This is actually worse than the inability to play the tutorial level.

Works
It worked fine on Proton

5.21-GE-1 GloriousEggroll
Used Proton 5.21-GE-1
With Standard Proton (5.13-6) game hangs at cut scenes, so I assume because of missing media foundation.
Works well with Proton Experimental, freezes on Proton Stable
Running mf-install makes videos work on proton stable, but the game still freezes after the bomb goes off.
Proton Experimental
Instead of cutscenes, a test picture is shown (I assume it's from Proton Experimental)
Cutscenes didn't work
Cutscenes are not showing and it gets stuck at the second one after the tuturial
Works only with Proton Experimental. Freezes with Proton 5.13-4 after the tutorial bombing.

Proton-5.9-GE-2-MF [https://github.com/GloriousEggroll/proton-ge-custom/releases](Glorius Eggroll) GloriousEggroll
Using the default Proton I was unable to get the game to progress past the explosion in the tutorial, the cutscene fails to load and gets stuck in a loop. Using the glorious eggroll release helped here.

black screen
after the first scene of the tutorial the game crash
Black sceen with looping audio after 3 min of tutorial (on the first cutscene, the bombing)
While the challenge mode is nice, it is impossible to load the story mode.
Game never gets to a save point. Unable to test.
Crashed at the explosion after the tutorial stage. (Black screen with siren audio looping) Challenge mode is fine.


So, I'm not sure if I got the syntax right... I wrote all three recommended settings into the Launch-options box like this: PROTON_USE_WINED3D=0 %command% PROTON_NO_ESYNC=0 %command% PROTON_NO_D3D11=1 %command% I don't know if that is the exact right way to write them, so that might be a reason, but the game just doesn't start. I get a process, steam registers it as running, that's why I actually have over 25h in the game... simply because I didn't realize this, but nothing happens on the screen. I didn't go as far as log-files, also partially because I don't have all to much experience with them.



As Todd Howard ones said, "And again it just works"



Tried this game on three different machines, no luck running it whatsoever. Game crashes on launch. Tried using wine3d3 as mentioned in previous reports. Tried using older versions of proton.





Ran until first job after tutorial. No problem. Seemingly native performance.

Works after a major proton update. Does not freeze if window loses focus (it does in wine).


Does not start at all. Log shows that proton cannot load the exe properly. There should not be any compatability issue because the very same executable runs pretty well OOTB in wine.



