Overall works fantastic just some minor crashes, and one spot that kept crashing and required extra setup to get past
Alt-Tab works but crashes the game when in Fullscreen
The one issue I ran into was it crashing at the same spot in one mission ending cutscene, however I was able to get past it by switching to Proton version 4.11-13 and adding "-force-d3d9" to the launch options, then after that was able to switch back to defaults and resume playing just fine.
Error from Epic Games Launcher. "file access error has occurred. Please check your running processes"
Does not currently work.
Currently can't run it and am looking for a work around.
Epic Online Services failed to validate dependencies
Apparently it's a recent change, according to recent discussions- but without tinkering the game will not launch now. I haven't attempted any tinkering to get past the problem however.
Game doesn't start at all
PROTON_NO_D3D11=1 %command%
I've tried various versions of proton including the latest GE at this time, very shortly after the pressing play the button goes from "Cancel" back to "Play", same on each version tried (as far back as 3.7-8), with and without the launch options
3 missions - no issures so far.
Runs suprisly well.
Full campaign playthrough with no issues.
Multiplayer may not be relevant as the number of players is very low. There were no public games nor multiplayer matches to be found.
Had no issues running it with Proton-6.16-GE. Native like experience, played through whole campaign.
6.16-GE-1 GloriousEggroll
Clicked install, game boots, started playing, just works
Did not try multiplayer.
6.16-GE-1 GloriousEggroll
Proton 6.16-GE-1
Other than the crashes the game runs well. Max settings at 4K is no problem for my machine.
Crashes every few missions with an error message from Wine. Have tried forcing it to use DX9 with launch option as recommended here but no change. I've noticed that the crashes always seem to happen on a checkpoint, and I wonder if they are related to the game saving.
Worked just fine out of the box when installing it through SteamPlay.
Shadows seem a little flickery sometimes in close-ups, but I have the impression that's rather to be blamed on the game / Unity than Proton.
Achtung: Lange Ladezeit bis auf dem Bildschirm etwas passiert ! Deshalb nicht vorher abbrechen.
Startparameter: -force-d3d9
I used an old version of proton 4.2-9. Furthermore, I had to set
PROTON_NO_D3D11=1 %command%
as launch flag
-force-d3d9
Multiplayer untested.
Work perfectly with maximum graphical settings
The maximum resolution is below my monitor : 2560x1440 instead of 3440x1440. It's still in fullscreen
No visible glitches, no performance issues so far on Ultra 1440p.
It's sad that you can't see fire. Vehicles just disappear :/
No fire animation
Works flawlessly out-of-the-box !
There is an active pause by pressing "P". Also, F10 displays the game menu (ESC doesn't).
Game menu shows, but cannot start new game
I can start the game with the -forcedx9 flag, and open some options from the menu, but the button to start a new game makes the game to get stuck with the background image and the shaky cam, also when entering the settings menu, the apply and cancel buttons don't work at all, and I have to kill the game
Need to use launch option -force-d3d9 or it wont start. Slow load times using an SSD
from withing steam client and the game properties i add the launch option -force-d3d9 and also clicked 'Force the use of a specific Steam Play combatibility tool' which was proton 4.11-9 in my case.
Game runs flawlessly out of the box. I could not tell a difference from running a native Linux game.
I played the campaign from start to finish, without a single crash, slowdown or any other glitch.
Unknown(2+ hours with Proton)Played most of the campaign and so far no issues, the only thing I had to do was to add the following to the launch options: PROTON_NO_D3D11=1 %command%
Unknown(2+ hours with Proton)Unknown(2+ hours with Proton)Had to run with these flags under Launch Options: PROTON_NO_D3D11=1 %command%. Also had to downgrade my Proton version from 4.11-3 to 4.2-9 to get it to work. Runs perfectly fine after these 2 tweaks.
Unknown(2+ hours with Proton)
