Possible line of interest from the log: `[00000030:] EXCEPTION handling: System.InvalidOperationException: Cannot call Present when a render target is active.`
> Replying to https://github.com/ValveSoftware/Proton/issues/2244#issuecomment-1631803023 Least according to the protondb review, it mostly says this. Least when you run it on deck. In Gaming Mode go to Properties... -> ...
> Checking protondb, apparently someone got it working on deck by forcing the resolution to 1920x1080 before launching **How is that done?** My !game_log.txt in Documents folder inside compatdata [code]
> Hello, I ran the game on SteamOS Game mode (Steam Deck), with `PROTON_LOG=1 %command%` and here is my log file. > > [steam-830820.log](https://github.com/ValveSoftware/Proton/files/8815651/steam-830820.log) > > I hope ...
Hello, I ran the game on SteamOS Game mode (Steam Deck), with `PROTON_LOG=1 %command%` and here is my log file. [steam-830820.log](https://github.com/ValveSoftware/Proton/files/8815651/steam-830820.log) I hope it helps t...
Getting this too on all available versions of Proton (6.3-8 to 3.7-8 as well as experimental). The strange thing is that the game launched fine the first time I installed it. I don't know what happened to break it. Re-in...
@alasky17 Apologies for the late response. Unfortunately, it doesn't work with 6.3-6 either. The error messages are different now. Could be because I have changed the hardware and driver version since I last tried to lau...
@Wyris That is strange. Could you try deleting the prefix and then launching directly on 6.3-5 just in case? The standard location is ~/.steam/steam/steamapps/compatdata/830820