Hello @julienbenjamin, a header only Proton log hints that something went wrong before the game itself had a chance to start. If you completely close Steam, then run steam from a terminal, are there any hints in the terminal spew when you tell Steam to start the game? (Debian's Steam package might divert the terminal spew to a file.)
Also, what filesystem are you using with /data/SteamLibrary/?
Hello @julienbenjamin, a header only Proton log hints that something went wrong before the game itself had a chance to start. If you completely close Steam, then run
steamfrom a terminal, are there any hints in the terminal spew when you tell Steam to start the game? (Debian's Steam package might divert the terminal spew to a file.)
I should have led with that, indeed, steam is indeed the one from Debian repositories. However, I do not have any issue with any other game like this (and to be frank, the empty log left me puzzled).
I had also missed the following error when running it from the CLI:
Proton: Upgrading prefix from None to 8.0-103 (/data/SteamLibrary/steamapps/compatdata/559100/)
Traceback (most recent call last):
File "/data/SteamLibrary/steamapps/common/Proton 8.0/proton", line 1658, in <module>
g_session.init_session(sys.argv[1] != "runinprefix")
File "/data/SteamLibrary/steamapps/common/Proton 8.0/proton", line 1453, in init_session
g_compatdata.setup_prefix()
File "/data/SteamLibrary/steamapps/common/Proton 8.0/proton", line 789, in setup_prefix
os.symlink("../drive_c", self.prefix_dir + "/dosdevices/c:")
FileNotFoundError: [Errno 2] No such file or directory: '../drive_c' -> '/data/SteamLibrary/steamapps/compatdata/559100/pfx//dosdevices/c:'
Seeing this, I figured my pfx folder was also from back then, so I deleted it and it worked. I feel quite silly opening this issue, now since it was a quite trivial issue. Especially since it was something you had to often in the past, but I guess I've lost the habit.
Also, what filesystem are you using with
/data/SteamLibrary/?
I should have clarified that point, it is ext4. So, no NTFS-related issue then ;)
Anyway, sorry for the inconvenience.
For me, game does start but after intro video (after creating character) I'm stuck in a black screen with Proton experimental and with 8.0-3.
Log shows:
285422.481:013c:0140:warn:seh:OutputDebugStringA "[2023.09.26-21.44.44:864][843]LogMoviePlayer: Shutting down movie player\r\n"
285422.481:013c:0140:trace:seh:dispatch_exception code=40010006 flags=0 addr=000000007B00CD97 ip=7b00cd97
285422.481:013c:0140:trace:seh:dispatch_exception info[0]=000000000000004b
285422.481:013c:0140:trace:seh:dispatch_exception info[1]=000000000074d6a0
285422.481:013c:0140:warn:seh:dispatch_exception "[2023.09.26-21.44.44:864][843]LogMoviePlayer: Shutting down movie player\r\n"
285422.482:013c:0140:trace:seh:RtlRestoreContext returning to 000000007B00E92A stack 00000000004EC7B0
285422.596:013c:0324:fixme:mfplat:topology_loader_Load iface 000000002C8732A0, input_topology 00000000023D1940, ret_topology 000000002873FCE8, current_topology 0000000000000000 stub!
285422.601:013c:0324:fixme:mfplat:media_source_QueryInterface {6ef2a662-47c0-4666-b13d-cbb717f2fa2c}, 000000002873FBC8.
285562.439:013c:0140:err:sync:RtlpWaitForCriticalSection section 0000000002376F10 "../src-wine/dlls/winegstreamer/media_source.c: cs" wait timed out in thread 0140, blocked by 03f8, retrying (60 sec)
285562.442:013c:0300:err:sync:RtlpWaitForCriticalSection section 0000000026E9DC78 (null) wait timed out in thread 0300, blocked by 0140, retrying (60 sec)
Skipping the cinematic will proceed to tutorial.
Came here to comment about this. With the same version of Proton (8.0-3), every video can crash the game (or rather Wine apparently) if you watch it to the end. The workaround is to skip it.
Here is an example of log during a game where I reach to a new cutscene: steam-559100.zip
Proton 8 freezes consistently at the end of the intro video (Phantom Doctrine logo, right before main menu). Works fine on both Proton 7 and Experimental bleeding-edge though. No immediate issues when actually in menus or playing missions.
Hello @frozen-sea, 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.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.
Hello @frozen-sea, 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.) Also, please copy your system information from Steam (Steam->Help->System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam->Help->Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.
Here you go.
steam-559100.log
https://gist.github.com/frozen-sea/768dedd0590df05184f7d5263654e142
proton experimentalx2 2023-09proton 8.0x1 2023-09proton 8.0-3cx1 2023-09PROTON_LOG=1x3 2023-09WINEDEBUGx1 2023-09
Compatibility Report
System Information
I confirm:
PROTON_LOG=1 %command%output:Symptoms
Game does not start.
I know it used to before, back in 2018. There was some ESync-related issues before at that time, which required the game from being launched with the NO_ESYNC argument.
I tried several Proton versions ; none allowed it to launch.
Reproduction
Try to run it through Steam (Clicking "Play" on the game library page).