I was able to get the game running by going back to proton 4.11-13. Not the best solution but at least the game runs again.
Hello @FelixSchwarz, what specific Proton version did you test with? (Proton 4.0 isn't a valid version.) If you tell Steam to run the game with Proton 5.0-10 after running it with Proton 4.11-13, does it continue working?
@kisak-valve No, unfortunately not. However I'm a bit confused as I got inconsistent results when trying different versions on that computer (Fedora 33 + Nvidia GT1030/binary driver) so I retried with this with an AMD system (F33 with kernel 5.11.7, RX570/open source drivers, flathub Steam).
So even on the AMD system there seems to be a Proton regression. The problem is reproducible even after reboots. One puzzling issue is that the game graphics is extremely slow (as if it would use software rendering instead of hw acceleration) if I start the game again without a system reboot (maybe logging in would be enough but I did not test this). Therefore I made sure to always reboot the system before trying another Proton version.
I'd be happy to provide more logs or information. I can also compile stuff myself/bisect if there is some documentation how to do that with Steam/Proton.
I should note that the game somewhat works with my wine(-staging) 6.3 from Fedora (no winetricks, just running wine "Green Project.exe"). However many texts are not shown (e.g. "settings" dialog has no texts at all but the in-game texts are mostly present).
It sounds like you encountered https://github.com/ValveSoftware/steam-runtime/issues/294 with your AMD system.
proton 5.0-10x2 2021-03proton 5.13-6x1 2021-03proton experimentalx1 2021-03proton 4.11-13x2 2021-03proton 4.0x1 2021-03PROTON_LOG=1x1 2020-06kernel32.dllx1 2020-06unityplayer.dllx1 2020-06
Compatibility Report
System Information
I confirm:
Proton log, PROTON_LOG=1 %command%
Symptoms
Crashes immediately on startup with the following error in the Unity log:
Removing
kernel32.dllchanges the traceback, but the game still crashes.The crash seems to be system config specific, this is not the first Unity game that fails like this but has green reports on ProtonDB.
It looks like it might have something to do with the following quirks of the config:
^ That said, I'm not sure how to dig deeper and would appreciate some pointers for figuring out what exactly causes the crash and possibly finding a work around.
Reproduction