You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
that I haven't found an existing compatibility report for this game.
that I have checked whether there are updates for my system available.
the log file exceeds 25 MiB even compressed as archive
Symptoms
The Game crashes with a C++ runtime error in winevulkan/loader_thunks.c on line 5141 when no log is given as parameter and produces a multi GiB proton log file before force quitting the program via other method was used as the game just stayed on the black screen that the non log version gives without reaching the runtime error dialog.
Reproduction
have the game installed and start the game with 1710947987 experimental-9.0-20240320 that was the default version at the time of writing this report.
Reverting back to 1710431022 proton-9.0-beta15 suggests this is a regression since beta15
The text was updated successfully, but these errors were encountered:
Kupferdrache
changed the title
Frostpunk crashes on startup with
Frostpunk crashes on startup with runtime error
Mar 21, 2024
Hello @Kupferdrache, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to #412 (comment).
Compatibility Report
System Information
I confirm:
Symptoms
The Game crashes with a C++ runtime error in winevulkan/loader_thunks.c on line 5141 when no log is given as parameter and produces a multi GiB proton log file before force quitting the program via other method was used as the game just stayed on the black screen that the non log version gives without reaching the runtime error dialog.
Reproduction
have the game installed and start the game with 1710947987 experimental-9.0-20240320 that was the default version at the time of writing this report.
Reverting back to 1710431022 proton-9.0-beta15 suggests this is a regression since beta15
The text was updated successfully, but these errors were encountered: