@fozzedout How does the fps compare to running it in wined3d?
I'm guessing it won't change anything if its the cpu that's bottlenecked, but just as a try.
PROTON_USE_WINED3D=1 %command%
Experimal mode only: Bizarrely, it did - it improved the frame rate to range from 5 - 25 FPS - a far bigger improvement as it was closer to being barely playable
Ah I'm guessing it's the native version that doesn't run which is what I'm also observing. Setting it to experimental fetches the windows version through proton. Or have you also tried setting 7.0-3 specifically? 7.0-3 at least works on my pc, but haven't tried steam deck yet.
Anyway i'm not sure dxvk is even working. Mangohud reports WINED3D even tho steam page says this game on windows needs dx9. So i wonder if it's actually running opengl.
I think it might not like fsync or esync so try and see if running with this improves it for you.
PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command%
Edit: Actually dxvk is a part of the log so not sure what is going on with that.
I didn't realise that there was a native Linux version... not really a surprised after so many years with it not working and frameworks have moved on!
Well I never, yes, that launch string improves it massively - to the point of a fixed 60 FPS with a drop to 58 FPS every second or two, and the CPU cores were all around 20% or less.
What exactly is fsync and esync? I did try to disable either of them: having only esync on averaged out the FPS to about 40 FPS, while with only fsync on averaged out to about 30 FPS.
I can't give you a technical description myself, but the simple version i guess is that esync and fsync are meant to lessen the cpu overhead or improve cpu bound performance through wine. In most games they can give a boost, but in some games they create issues.
esync came first and are supported by most systems today and fsync came later as a different implementation meant to be used instead of esync. The current implementation of fsync was mainlined into the 5.16 kernel so you no longer need a custom one to use it.
A bit more technical explanation of esync can be found here https://github.com/zfigura/wine/blob/esync/README.esync
winesync (or fastsync if you will) is another implementation in the same spirit that is in the works. I can't give you a technical explanation here either but this supposedly mimics how it work on windows better than the previous two methods.
I haven't seen anymore issues since changing it to Proton and adding the commandline for disabling fsync and esync.
I'll play through the game and report if I come across any other issues.
PROTON_NO_ESYNC=1x1 2022-06PROTON_NO_FSYNC=1x1 2022-06PROTON_USE_WINED3D=1x1 2022-06PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command%x1 2022-06PROTON_USE_WINED3D=1 %command%x1 2022-06
Compatibility Report
System Information
SteamDeck
I confirm:
No proton log file is created under default settings.
Experimental Proton log: steam-204060.zip
Symptoms
Under default settings, the game does not launch. No window, nothing. It just does not launch.
Changing the proton version to experimental, game launches but is too laggy to play(2-15 FPS)
Reproduction
Default: Just attempt to launch the game.
Experimental: Launch the game, it loads, and start playing on a level. One CPU core is maxed, and the frame rate is all over the place, going from 2 FPS to 15 FPS.