I'm getting really bad frametime stutters recently, happens after a playing for a while. Only way to stop the stuttering is to close the game and reopen it. I have tried multiple different versions of proton (8, 9 and experimental as well as proton-ge versions) and nothing has helped.
System Information
Game seems to have stopped working with the latest update. It launches properly but when going to any stage or any story/gameplay content, it just crashes. Tried with and without DXVK. Proton Log (Zipped as uncompressed log is ~140Mb) attached along with actual Game log.
It's something to do with the game recording timeline feature, something fails and causes a null pointer access.
The game can be "tricked" into running without steam integration by removing the -steamapp default argument and then it works just fine.
You can use this script:
#!/bin/bash
exec ${@//-steamapp//}
save it somewhere, and set the launch options in steam to /path/to/script %command%
Execute "protontricks 2668080 wmp11", the notices content will be displayed normally...
But I don't know what exactly this directive modifies...
And this command will cause the video problems solved by the proton-ge version to appear in other forms.
It's something to do with the game recording timeline feature, something fails and causes a null pointer access. The game can be "tricked" into running without steam integration by removing the
-steamappdefault argument and then it works just fine. You can use this script:#!/bin/bash exec ${@//-steamapp//}save it somewhere, and set the launch options in steam to
/path/to/script %command%
Thank you, it works.
Execute "protontricks 2668080 wmp11", the notices content will be displayed normally... But I don't know what exactly this directive modifies... And this command will cause the video problems solved by the proton-ge version to appear in other forms.
Somehow the windows version ends up as Windows 7 after winetricks installs wmp11 (it sets to xp and then changes it back, but it's Windows 10 before, no idea what's going on there), anyway, it works if you do just that.
@nyz93, You broke through a blind spot for me. There is really no need to install wmp11. I just need to downgrade the Windows version from 10 to 7 and the announcement will be displayed normally. Thank you for your insight.
So in fact I just need to execute protontricks 2668080 win7.
It's something to do with the game recording timeline feature, something fails and causes a null pointer access. The game can be "tricked" into running without steam integration by removing the
-steamappdefault argument and then it works just fine. You can use this script:#!/bin/bash exec ${@//-steamapp//}save it somewhere, and set the launch options in steam to
/path/to/script %command%
tested on steamOs, game doesnt even launch.
i saved the script to a txt and then wrote the path at the games launch option, changed to proton experimental. am i doing something wrong?
The script does need to be set to be executable. Also, the script only fixes the crash when starting a level, if the game does not start without it then you have some other problems.
It's something to do with the game recording timeline feature, something fails and causes a null pointer access. The game can be "tricked" into running without steam integration by removing the
-steamappdefault argument and then it works just fine. You can use this script:#!/bin/bash exec ${@//-steamapp//}save it somewhere, and set the launch options in steam to
/path/to/script %command%
I gave this a shot since I had the issue with the game crashing when attempting to start a fight/cutscene, but unfortunately, the game doesn't boot anymore if I try and setup the launch options as mentioned. I copy-pasted the script into a text file, renamed it to "fix.sh", set it to allow to be run as an executable and wrote "/home/jafus/fix.sh %command%" (where the script is located, without the quote marks) and not changing anything else. Steam overlay is already off, game is not in full screen, using proton experimental, etc. I had it running fine before this update messed things up. I'm kind of confused as to what I'm doing wrong for the script that works for everyone to not work for me. Am I that bad at using Linux? ^.^'
@Jafus1 What distro are you using? What you're doing looks like it should be fine.
Using
MANGOHUD=1 gamemoderun konsole --hold -e %command%
as the launch options, on a Ryzen 9 7900 /w RTX 3080 running with GE9-11 on PikaOS 3 (an ubuntu variant), the game just launched.
@Jafus1 What distro are you using? What you're doing looks like it should be fine.
I am currently using Linux Mint 21.2 Victoria.
@Jafus1 Well, sorry I can't help, I use debian and am not familiar with mint. Maybe you can also try the other writing styles in this thread.
I thank you for the link, the script given in the Steam community thread worked perfectly. Had to add \ because of the spaces in one of my directory, but I'm in the game.
So maybe you just need:
#!/bin/bash
exec "${@//-steamapp//}"
I dont understand how to do this T-T
Starting this week, I can't seem to netplay anymore.. anyone else experiencing this? Of note in the crash note, it reads as
<Exception>
<ExceptionModuleName>d3d11.dll</ExceptionModuleName>
<ExceptionCode>0xc0000005</ExceptionCode>
<ExceptionDescription>The thread attempts to read from or write to a virtual address for which it does not have access.</ExceptionDescription>
<ExceptionAddress>0X00006FFFFD2BB999</ExceptionAddress>
<DumpFileName>Z:\home\shaddox\.steam\debian-installation\steamapps\common\SNOWBREAK\Game\Binaries\Win64\minidump\fb2fd5c5-da72-46e8-b6dc-8ad4ee0c425e.dmp</DumpFileName>
<DumpKey>186884353D283EBCE88BC082F1F21459</DumpKey>
<DumpGuid>7025fc1f-7b09-4ef9-acfb-8f481f1ae96b</DumpGuid>
<DumpType>native</DumpType>
<ExceptionTime>1739879565</ExceptionTime>
<TimeToFailure>103</TimeToFailure>
<ProcessName>Game.exe</ProcessName>
<ProcessInstance>1</ProcessInstance>
<ProcessMemUsed PagefileUsage="1702723584" WorkingSetSize="2009505792" />
<ProcessMemPeak PagefileUsage="1702723584" WorkingSetSize="2009505792" />
</Exception>
Hello @Shaddox, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
@Shaddox besides the information kisak asked for, could you give more information about this netplay you are mentioning? over a cursory check of the game's options I couldn't find it
@Shaddox besides the information kisak asked for, could you give more information about this netplay you are mentioning? over a cursory check of the game's options I couldn't find it
By netplay I meant playing online. After more in depth investigation at the time, from all the online game modes, the only one that was affected was the event related Defense Line Zero, both alone and with other people. The other online modes worked fine by myself (could not find matches so I thought I would try by myself and I was able to play). I waited for Defense Line Zero it to come back (which it did now) to see if I could reproduce it more properly, but ... now it works just fine. So I guess there was something weird about that Defense Line Zero.
I can launch the game and login just fine but when trying to load the dorm or any mission the game will hang in the loading screen at just after 80% progress. The main hub screen works, but trying to load any stage with a controllable character will hang.
There seems to be one other person who has experienced the same issue but fixed it by loading the game on Windows once after which it started working on Linux as well (https://www.protondb.com/app/2668080#2tASmdm9ga). This is not an option for me.
proton experimentalx2 2024-08PROTON_LOG=1x1 2025-02MANGOHUD=1x1 2024-08d3d11.dllx1 2025-020xc0000005x1 2025-02
Compatibility Report
System Information
I confirm:
Symptoms
Issue 1
Game login screen is glitching to hell and back (simile used for effect) when using an Ultrawide monitor.
Current workaround is to launch on my 21:5 ultrawide, then drag the game window to my 16:9 monitor on the side. This forces a window resize, which apparently forces the game to recalculate SOME things within, and this stabilizes the login glitch long enough for me to hit the Steam login to initiate the OAuth login flow.
Video of the glitch and workaround in action: https://youtu.be/HazjEaxYF58
Reproduction
Issue 2
In-game web-based communications don't load / show properly.
Since this has to do with web elements, I'm suspecting issues 1 and 2 are actually related.
Reproduction
On PC (broken):

On Mobile (expected):
