When running current Proton 9 Beta or current Experimental, game doesn't seem to correctly register it's current window state resulting in game pausing itself (despite having Run in Background enabled in game settings).
In particular it gets stuck on launch with a gray screen until you LMB once. And it will get stuck paused after touching keyboard or moving mouse after loading a save or starting a new game.
Gamepad works fine after initial LMB to get past the gray screen, but same thing as above, touch any key or move the mouse and it's paused.
Game stays paused unless you hold LMB (which kinda makes it unplayable).
Proton 8.0-5 doesn't have this issue and works fine.
System information if it happens to be relevant:
Operating System: Arch Linux
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Proton version:
Proton 9: 1709651366 proton-9.0-beta14
Proton Experimental: 1709844556 experimental-9.0-20240307b
Hello @awaken1ng, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
Ah, sorry, forgot about that.
steam-1356670.zip
One log was made by starting a new game, pausing/unpausing a couple of times by releasing/holding LMB and then Alt-F4ing out.
The other was done in the main menu, alt tabbing in and out. Noticed it was adding the following bit to the log every time I did that, might be the clue:
48455.904:010c:011c:fixme:oleacc:find_class_data unhandled window class: L"[#32769](/issue/ValveSoftware/Proton/32769)"
48458.494:010c:011c:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
48458.494:010c:011c:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 000000000134E3C0, 10002, 0000000001A2F8A0: stub
Edit: Nvm, 8.0-5, which works, also does similar-ish thing.
Did some Wine bisecting, caused by bb496ea847bb019067ea4b60b9916378ed6fc452.
@awaken1ng Can you test with Proton Experimental and see if you still experience the issue please? I was able to reproduce the issue with Proton 9.0 Beta, but not with Proton Experimental.
Yup, can confirm, seems fixed in current Experimental.
Same issue on current Experimental again, game is pausing itself unless LMB is held. Bleeding Edge also doesn't work, 9.0-3 does though.
Wine logs and stuff are probably not interesting but here they are anyway:
Operating System: Arch Linux
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.10.10-arch1-1 (64-bit)
Graphics Platform: Wayland
1727104926 proton-9.0-3c
1727105898 experimental-9.0-20240918b
1727484535 experimental-bleeding-edge-9.0-123944-20240928-p5159bc-wf06ad0-db4e69d-vea2514
@awaken1ng Thank you for the report! We are currently investigating this one. Unfortunate it returned, and curious how it did.
Bisection between proton-wine-9.0-3 and experimental_9.0 points to 0c3679b42c8ca67b8b58c211b1433565c82b211d.
@awaken1ng Thank you for the bisect info! And apologies for the lack of communication. It has been a busy time and since this game still works on 9.0-3 it has taken a while to look into. Hopefully this will be fixed, either by re-adding the commit or fixing in some other way soon :)
proton 9.0-3cx1 2024-09proton 9.0x2 2024-03proton experimentalx2 2024-03proton 8.0-5x1 2024-03PROTON_LOG=1x1 2024-03
Compatibility Report
System Information
I confirm:
steam-1356670.log
Symptoms
The game itself appears to run fine. There's an in-game frame limiter option that lets you set the fps to 30fps or the monitor's refresh rate. For me, this monitor option is reported as 1fps (1hz). Enabling vsync ignores the frame limiter and let's me play at my display's 60hz refresh rate