Apparently adding PROTON_LOG=1 option breaks the launcher. :thinking:
I managed to acquire a better unhandled exception report by compiling proton with debug enabled:
https://gist.github.com/igo95862/1757c571f8293892ae06c14c88f36f16
I had to hack Makefiles to actually enable debug compilation but I think there is still some stripping going on so I will try to modify more Makefiles...
Maybe there is a better way to use debug wine? Since the exception seems to happen in the wine library I am trying to an exact function where it happens. (also for some reason GDB is not working from the gdb-run script generated by proton)
Still borked using the latest version of proton (8.0-1)
logs from steamdeck
steam-1277510.log
Just tried on steam deck. Configuration tool works, but the moment the actual game tries to start it just crashes back to the deck UI before it even starts.
It's worth noting that when I played this game on my 3 monitor windows PC, it started on my middle portrait monitor for some reason and I had to run the game in windowed mode because full screen insisted on running in the middle portrait monitor, so it might be looking for a display that "doesn't exist", and when it fails to find it, it crashes.
I tried overriding the resolution in properties to see if that fixed things, and even tried GE-Proton-7-55, 8-1, 8-4, but still had no luck. This seems like a problem gamescope should just straight up solve, but doesn't.
Update: Installing "d3dcompiler_47.dll" via protontricks allows the game to work.
It actually works fine under Proton 10 beta1/beta2/experimental without installing additional libraries, shouldn't this issue be closed?
Compatibility Report
System Information
I confirm:
Symptoms
Game crashes on startup.
Reproduction
Start the game. It almost immediately stops.
The configuration launcher does work though.
steam-1277510.log