Hello @TauAkiou, does adding PROTON_NO_ESYNC=1 %command% to the game's launch options have any effect?
@kisak-valve Running the game with PROTON_NO_ESYNC=1 had no effect. The game still loads indefinitely on starting a mission.
Having the exact same issue. Leaving for the first mission prompts an infinite loading screen.
Heyo, same here.
Proton: 4.2-5
Distro: OpenSuse tumbleweed 20190527
Kernel: 5.1.4-1-default
Processors: 8 × Intel® Core™ i7-3770K CPU @ 3.50GHz
Memory: 16 GiB of RAM
Proton 5.0-1 - the problem is still here.
I noticed that the game goes to 100% CPU usage a minute or so after entering the lobby area, and never stops. It doesn't appear to be triggered by anything in specific, and as far as I can tell, it's impossible to get to the mission select before this happens (thanks to cutscenes and long animatoins). I wonder if this is related to the issue in any way?
The game still loads indefinitely. I tried linking it to winedbg, but either I don't know enough to get the debugger working (more then likely), or the game uses anti-debug code/anti-piracy code that doesn't play nice with WINE. It would be great to see someone else with more experience take a look at this, because this is still a game I'd love to play on Linux.
Attaching winedbg seems to immediately cause the game to freeze or crash, and often seems to hang the debugger along with it.
Game still soft-locks on the current Proton Experimental. I loaded a save from the Windows playthrough, to check if it's some weird effect of the tutorial missions but no, trying to load a mission with no cutscenes or anything else fancy attached still softlocks.
I'll upload my own log with Proton 6.3, hope someone helps, this game has no Denuvo/DRM/anti-hack so it should work fine
steam-899440.log
Edit: Proton, not WINE
infinite loading still happens when going into missions
log from proton experimental 6.3-20210512
CPU Ryzen 3600
GPU Vega 54
Kernel 5.12.1-xanmod2-2
Mesa 21.1.0
The problem I believe we're having is some kind of bizarre anti-debug, tamper, or piracy mechanism that's going haywire in WINE. The game is still running as far as I can tell - it doesn't freeze or crash, it dead-loops indefinitely until the process is killed manually.
As far as we're concerned, the game is running, it's just not advancing into a mission.
The game now loads into a missions when using the Proton Experimental.
ProtonGE 6.9 or higher seems to work as well. I played for about an hour and didn't notice any problems.
youtube video
CPU Ryzen 7 2700x
GPU RX580
Kernel Linux-zen
Mesa 21.1.1
I am also interested in why the game became working. Possibly due to the dxvk update (?) That happened recently in Proton Experimental. Proton 6.9GE was also updated 2 weeks ago, to the git version of dxvk.
I can confirm the same behavior as @CyberDonk3y and ProtonDB; Using Proton GE 6.10 for me appears to have fixed the infinite loading issue and I, for the first time, was actually able to get into a mission.
The game, at this point appears to work more or less perfectly with little to no performance or graphical hiccups, though my results seem to vary on computer right now. One system will hang indefinitely on a white screen when the game is launched, while my laptop will work just fine.
It would be interesting to know exactly what fixed this issue, since it had to have been something extremely recent.
this problem also happens on wine 6.10 + dxvk 1.8.1 , but after updating dxvk to 1.9 problem resolved, so it seems resolved by upstream(dxvk).
Game is crashing with both Proton experimental and stable when it tries to play the intro video
proton experimentalx4 2024-03proton 6.3x1 2021-04proton 5.0-1x1 2020-02proton 3.16-8x1 2019-03PROTON_NO_ESYNC=1x2 2019-03PROTON_NO_ESYNC=1 %command%x1 2019-03
Compatibility Report
System Information
I confirm:
Symptoms
Game will load into the lobby, but will enter an infinite loading screen when attempting to start a mission. Game will never actually start.
Reproduction
Load game, select mission from console, and start the mission.
steam-899440.log