OK there seems to be some confusion. Here's where I stand.
- Actual gameplay is stable for me with both 5.0 and 5.13.
- Replays almost always crash with 5.0 but never with 5.13.
@foodlfg said in Linux Support:
if steam had not been running then the first one would not have worked either.
only 5.09, 4.xx run file generates properly for me.
5.13 does not
This is not correct in my experience. Before 5.13 I never had to have Steam running to play FAF. What has changed with 5.13 is that Steam generates a slightly different run file. With 5.0 and earlier the last line of the file ended with:
bin/wine" "${@:-${DEF_CMD[@]}}"
but with 5.13 it became
bin/wine" steam.exe "${@:-${DEF_CMD[@]}}"
So instead of executing SupremeCommander.exe directly with wine, 5.13 instead calls steam.exe which in turn launches the game. That's why 5.13 doesn't work if Steam isn't running. Still, as I've said, you can fix this very easily by removing steam.exe from that line and everything will work correctly.
@foodlfg said in Linux Support:
the game is not 100% stable with Wine / Proton.
we dont know why.
Again, not in my experience. I've had zero stability issues with Proton 3.16 and 5.13. The only problematic ones for me were 4.11 (caused desyncs) and 5.0 (caused replay crashes).
@tatsu said in Linux Support:
I just switched to D9VK
how'd you do that?
With Proton 5.0 and above Proton defaults to D9VK instead of Wine D3D9 so you don't have to do anything special. If DXVK_HUD=1 shows you the DXVK hud in game then you are using D9VK. Of course, you can try to force enable D9VK with PROTON_USE_D9VK=1