Frostpunk (323190)

[lineber]

OS: Fedora release 28 (Twenty Eight) x86_64
Kernel: 4.17.14-202.fc28.x86_64
Resolution: 1920x1080, 1280x1024
DE: GNOME 3.28.3
WM: GNOME Shell
WM Theme: Adwaita
Theme: Adwaita [GTK2/3]
CPU: Intel Pentium G4620 (4) @ 3.700GHz
GPU: NVIDIA GeForce GTX 1060 3GB
Nivida Driver Version: 396.45
Memory: 4540MiB / 15492MiB

Frostpunk loads and starts amazingly. You can play the game and it is great, however, somewhere around 10 minutes in, it crashes. I don’t know how this can be related but both times this happened, I was by the metal ore. Possibly a coincidence. Either way, I know people have claimed this game works; and it does but eventually it crashes.

[gd71]

same issue here with log:
Unhandled exception: unimplemented function lsteamclient.dll.Steam_ReleaseThreadLocalMemory called in 64-bit code (0x000000007b44abbc).
GeForce GTX 1070:
Driver: 396.54.0
Vulkan: 1.1.70
Kubuntu: 18.04

[svenstaro]

Works absolutely perfectly for me. Have been playing for around 10h straight without any problems.

Arch Linux
Intel Xeon E3-1275 v5
64 GB RAM
Nvidia GeForce 1080 TI with 396.54

[ryanmusante]

https://gist.github.com/ryanmusante/e0789f11ca3adfa4442297ac0099461f

Crashing stops for me when esync is disabled.

[kisak-valve]

Hello @ryanmusante, can you check if https://github.com/ValveSoftware/Proton/blob/proton_3.7/PREREQS.md#fd-limit-requirements is relevant to your system?

[ryanmusante]

@kisak-valve

Per the requirements page, it states

LLVM7 or above is recommended to play DX11 games without GPU hangs.

There is an AUR package "aur/llvm-svn 8.0.0svn_r340523-1 [23 Aug 2018]". It is a 8.0 SVN, will this suffice and be properly detected alongside the LLVM 6?

Latest nvidia, mesa and LLVM installed on Manjaro testing branch:

- extra/linux418-nvidia 1:396.54-1 [installed]
- extra/mesa 18.1.7-1 [installed]
- extra/llvm-libs 6.0.1-4 [installed]

I added the values to the files within systemd and rebooted. It appears esync is functional but I am unsure of specific compatibility per program.

/etc/systemd >>> cat system.conf | grep -i NOFILE                                                          
DefaultLimitNOFILE=2097152

/etc/systemd >>> cat user.conf | grep -i NOFILE                                                                 
DefaultLimitNOFILE=1048576

/etc/systemd >>> ulimit -Hn                                                                              
1048576

For now, I am using the separate wine+steam prefix to run games not fully supported by proton with a default of esync disabled for now.

~/.scripts >>> cat default.sh                                                                                       
#!/bin/sh
env WINEPREFIX=/home/ryan/.wine
env WINEDEBUG=-all,fixme-all
env WINE=/bin/wine

## ESYNC disabled by default
#export WINEESYNC=1

## VULKAN specific
export DXVK_DEBUG_LAYERS=0
export DXVK_LOG_LEVEL=0
export DXVK_HUD=devinfo,memory,fps

## wine load command
$WINE /home/ryan/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe -no-cef-sandbox

[gd71]

Hello,
my 2 cents:
disabling esync (PROTON_NO_ESYNC=1 %command%) still result to the same crash in my configuration with proton 3.7-3 or 3.7-4beta .
Crash is always at the same stage of the game independently of what I'm doing (transition from day 2 to 3 at 0:00 in game).
fd-limit-requirements are satisfied but LLVM is not installed

[Azarius]

Hello,
I have the same crash as gd71. The crash happens from transition from day 2 to 3.

Config :
Kubuntu: 18.04
Driver : Nvidia 396.54
Proton : 3.7-3 or 3.7-4beta

Edit : Not 100% sure but the Crash seems related to autosave.
Edit 2 : I confirm the bug is linked to autosave. @gd71 can you try this method to see if it fixes the problem for you too ?

1. Disable steam cloud for the game
2. You have to find where the game saves the autosave file. For me it is : .steam/steam/userdata/82407569/323190/remote/saves/
3. Delete the autosave.save file.
4. Launch the game
   You have to delete the autosave.save file after every auto save (so basicaly each day at midnight).
   I'm writing a script that will do this automatically.

With this method, I was able to play the game during 1H without troubles.

[Azarius]

Hello,

Here is a script that fix the issue :

1. Disable steam cloud for the game
2. Find where the game saves the autosave file. For me it is : .steam/steam/userdata/82407569/323190/remote/saves/
3. Edit the script to set the path
4. Launch the script

The script : Frostpunk.zip

It will delete the autosave.save file after every creation. So this means you will not have the autosave while playing. Regular save works.

[gd71]

Nice catch @Azarius ! this solved the issue for me

[JakeEhrlich]

I also have this issue.

[aqxa1]

I have the same crash and message when saving with "Shenmue 1 & 2" as well:

Unhandled exception: unimplemented function lsteamclient.dll.Steam_ReleaseThreadLocalMemory

It looks to be a bug with the Steam client beta (not Proton beta) since after reverting to the standard Steam client, the crash no longer occurs.
EDIT: Nevermind, not sure why it's so intermittent but it happened again with the non-beta client.

[mhork]

I have not been able to get the game to launch at all on Ubuntu 18.04 running on two separate rigs

[OvermindDL1]

A slight modification of @Azarius's script (logging, more efficient) got the game to stop crashing, guessing it's a game bug since there are reports for Windows too.

Oh, also had to install the vulkan libraries from the standard ubuntu repo, never loaded with no error before that.

[mhork]

Just tried @Azarius's fix, it didn't seem to help. I changed the version of Proton I was using, and every other setting I can think of, but it still won't launch for me

[kisak-valve]

Frostpunk (323190) fails to start

Issue transferred from #1477.
@mcodax posted on 2018-09-16T01:34:25:

Compatibility Report

• Name of the game with compatibility issues: Frostpunk
• Steam AppID of the game: 323190

System Information

• GPU: GeForce GTX 1080 Ti
• Driver/LLVM version: 4.6.0 NVIDIA 396.54
• Kernel version: 4.18.7-arch1-1-ARCH
• Link to full system information report as Gist: https://gist.github.com/mcodax/d66b3c337e1ce764c9f87d740f64ed9a
• Proton version: 3.7-6

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

steam-323190.log

Symptoms

Frostpunk doesn't start after I press 'Play'. It tries to load for a few seconds but then I see the option to press 'Play' again.

Reproduction

Start steam (native/runtime through a desktop shortcut or library item).
Start Frostpunk.

[Uthule]

"Frostpunk doesn't start after I press 'Play'. It tries to load for a few seconds but then I see the option to press 'Play' again."

Same problem, also using latest Arch kernel.

Same problem also:

109736.877:000c:000d:trace:module:MODULE_InitDLL (0x7f10715b0000,PROCESS_DETACH,0x1) - RETURN 1
109736.877:000c:000d:trace:module:MODULE_InitDLL (0x7b420000 L"KERNEL32.dll",PROCESS_DETACH,0x1) - CALL
109736.877:000c:000d:trace:module:MODULE_InitDLL (0x7b420000,PROCESS_DETACH,0x1) - RETURN 1
109736.877:000c:000d:trace:module:MODULE_InitDLL (0x7bc20000 L"ntdll.dll",PROCESS_DETACH,0x1) - CALL
109736.877:000c:000d:trace:module:MODULE_InitDLL (0x7bc20000,PROCESS_DETACH,0x1) - RETURN 1
pid 13518 != 13517, skipping destruction (fork without exec?)

[kapsh]

Compatibility Report

• Name of the game with compatibility issues: Frostpunk
• Steam AppID of the game: 323190

System Information

• GPU: GTX 750 Ti
• Driver/LLVM version: nvidia 396.54
• Kernel version: 4.18.14
• Link to full system information report as Gist: https://gist.github.com/kapsh/8813cdc64a652fea95bc967d4e641731
• Proton version: 3.7-2

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

Frostpunk crashes on every save (both auto and manual). Error message is wine: Call from 0x7b44abbc to unimplemented function lsteamclient.dll.Steam_ReleaseThreadLocalMemory

Reproduction

1. Start campaign A new home.
2. Play a while (in-game day or two).
3. Hit F5/Save from menu/Wait for morning autosave.

steam-323190.log

[Joinyy]

@kisak-valve I had trouble playing the game first, but after updating the nVidia driver to 410.xx it worked with the autosave skript 👍

[jonnyteronni]

Just tried @Azarius's fix, it didn't seem to help. I changed the version of Proton I was using, and every other setting I can think of, but it still won't launch for me

I'm on the same situation. Did you find anything yet?

[mhork]

@jonnyteronni I used proton beta, and there was a recent update that seemed to fix the launch issue. You still have to run @Azarius fix, but after the update the game launches again and I haven't had any other issues. Make sure the game is updated, and if that doesn't work perhaps uninstall and reinstall?

[jonnyteronni]

@jonnyteronni I used proton beta, and there was a recent update that seemed to fix the launch issue. You still have to run @Azarius fix, but after the update the game launches again and I haven't had any other issues. Make sure the game is updated, and if that doesn't work perhaps uninstall and reinstall?

I updated nvidia to 410 version and still nothing. It was giving me an error on a game file named AnselSDK64.dll was missing. I always install my games on a different SSD. What I did to solve my launch problem was to install the game on my /home/ steam library.

[jonnyteronni]

@Azarius I'm trying to run ./Frostpunk.sh but it returns the following error:
./Frostpunk.sh: line 5: inotifywait: command not found

I tried to google the solution but had no luck. What I'm I doing wrong?

[EDIT] - I googled it a bit more and found out I had to install inotify-tools package first. It is working well now. Thanks!

My configuration:
Proton: 3.7-8
Distro: Ubuntu 18.04.1 LTS
Kernel: 4.15.0-36-generic
RAM: 16 GB
GPU Driver: NVIDIA 410.66
GPU: NVIDIA GeForce GTX 780
CPU: Intel Core i5-4670K @ 3.40GHz

[Nautigsam]

Compatibility Report

• Name of the game with compatibility issues: Frostpunk
• Steam AppID of the game: 323190

System Information

• GPU: GeForce GTX 860M
• Driver/LLVM version: NVIDIA 410.66
• Kernel version: 4.14.77-1-MANJARO
• Link to full system information report as Gist: https://gist.github.com/Nautigsam/30c53ec1449f53feef6945fec77a30e8
• Proton version: 3.7-8

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

steam-323190.log

Symptoms

The game won't launch. It seems that an exception occurs due to a null reference. See the report on Wine website for more information.

Reproduction

Always. Just try to launch the game.

[OvermindDL1]

@Nautigsam That error usually means that your vulkan version is too low or not installed at all. Can you post the output of your vulkaninfo command?

[Nautigsam]

@OvermindDL1

$ vulkaninfo
==========
VULKANINFO
==========

Vulkan Instance Version: 1.1.85

Xlib:  extension "NV-GLX" missing on display ":0".
/build/vulkan-tools/src/Vulkan-Tools/vulkaninfo/vulkaninfo.c:3357: failed with VK_ERROR_INITIALIZATION_FAILED

[OvermindDL1]

Xlib: extension "NV-GLX" missing on display ":0".
/build/vulkan-tools/src/Vulkan-Tools/vulkaninfo/vulkaninfo.c:3357: failed with VK_ERROR_INITIALIZATION_FAILED

There's your problem then @Nautigsam. :-)

I use AMD and vulkan is solid there, no clue what to do to get it in your nvidia setup, maybe just newer drivers?

[Nautigsam]

@OvermindDL1 I am up to date, but that's probably because I am using Bumblebee and it does not support Vulkan yet. I stay tuned, then.

[OvermindDL1]

@OvermindDL1 I am up to date, but that's probably because I am using Bumblebee and it does not support Vulkan yet. I stay tuned, then.

Ah, that would be it then. You absolutely need Vulkan support to use the DX->Vulkan translation layer. It's all so much easier on AMD... ^.^;

[hollunder]

I can't get this game to launch, no matter what I tried so far. I suspect that it may be incompatible with pipewire somehow. This is only a suspicion on my part at this point, confirming requires a bit of work. However, this user report suggests there may be something to it: https://www.protondb.com/app/323190#LQTvvtleix

[kisak-valve]

Hello @hollunder, 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 your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[regulator-g]

Hi guys, I am on a laptop with switchable graphics and noticed quite a performance difference:

5800H / Vega 8 2GB iGPU: 30fps

MX450 2GB dGPU: 5fps

Using Proton7.0.3

I read that this game is very VRAM heavy and perhaps the iGPU can use RAM as VRAM leading to increased performance? I guess also that the MX450 is an entry level lower wattage version, and the game is not optimized well.

[hollunder]

Hello @hollunder, 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 your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

steam-323190.log
https://gist.github.com/hollunder/3c2229676c3cbfaac2d0b35486caefe3

Meanwhile I no longer run Pipewire but switched back to PulseAudio, but the problem persists. Above log is with the latest Proton by GE but I have tried multiple versions, also the latest official ones of course.

[hollunder]

I now logged into i3 on X11 again for a test and for the very first time Frostpunk started up. So I am assuming for now that the problem is somehow related to Wayland or Sway.

[kisak-valve]

That behavior reminds me of some discussion on #413 and I noticed "SDL_VIDEODRIVER=x11", in your system information. It might be interesting to test what happens with the game, a Sway session and the game's launch options set to SDL_VIDEODRIVER="" %command%.

[hollunder]

That has indeed been the problem. The game starts up under Sway/Wayland when this env variable is unset. To my knowledge the only two valid values are x11 and wayland. Strange that other games worked fine with x11, which I guess means they were running using XWayland, but this one does not.
Thanks a lot Kisak.

[GBathie]

Replying to #412 (comment)

Hi ! Have you managed to solve this issue ?
I'm running into the same issue, using Proton 7.0-6 (the more recent version fail to launch Frostpunk, for some reason).
My computer is a Ubuntu 20.04 with an integrated Intel Iris Xe, using Wayland.
I'm using the following command to launch the game : gamemoderun PROTON_LOG=1 OPENSSL_ia32cap=~0x20000000 DXVK_ASYNC=1 %command%.

Using PROTON_USE_WINED3D=1 do not solve the issue, and makes the game glitchy.

Here is the system information gist, and here are the game logs : steam-323190.log.

Edit : The same issue arises when I launch the game with gamemoderun PROTON_LOG=1 %command%

[Blisto91]

@GBathie Hello. It might be worth looking into upgrading your graphics drivers (including Vulkan driver) as they are quite old and unsupported on Proton 8 and above.

[GBathie]

@GBathie Hello. It might be worth looking into upgrading your graphics drivers (including Vulkan driver) as they are quite old and unsupported on Proton 8 and above.

Thank you for the suggestion !
Updating the Mesa drivers using the kisak-mesa PPA seems to have solved the problem !

[Zeioth]

That behavior reminds me of some discussion on #413 and I noticed "SDL_VIDEODRIVER=x11", in your system information. It might be interesting to test what happens with the game, a Sway session and the game's launch options set to SDL_VIDEODRIVER="" %command%.

I can confirm this is currently necessary to start the game. I'm gonna report it on protondb too.

[kisak-valve]

Frostpunk doesn't launch

Issue transferred from #7233.
@Spartik24 posted on 2023-11-04T15:33:32:

Compatibility Report

• Name of the game with compatibility issues: Frostpunk
• Steam AppID of the game: 323190

System Information

• GPU: RX6600XT
• Video driver version: Mesa 23.2.1
• Kernel version: 6.5.9
• Link to full system information report as Gist:
• Proton version: Experimental/8.0.4/7.0.6/GE-8.22

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

steam-323190_GE.log
steam-323190_EXP.log

Symptoms

I use Archlinux with Wayland(Hyprland) and I was not able to start the game. After pressing play button in steam it loads for 2 seconds and after that the play button reappears. I already tried some solutions that I found on protondb and on github, like starting the game with SDL_VIDEODRIVER="", etc. , but none of them worked.

Reproduction

Open steam, and press the play button.

[kisak-valve]

Frostpunk crashes on startup with runtime error

Issue transferred from #7589.
@Kupferdrache posted on 2024-03-21T09:03:21:

Compatibility Report

• Name of the game with compatibility issues: Frostpunk
• Steam AppID of the game: 323190

System Information

• GPU: AMD Radeon RX6650
• Video driver version: Mesa 24.0
• Kernel version: 6.6
• Link to full system information report as Gist:https://gist.github.com/Kupferdrache/3d98895b4dbc4632a6c5e592d1dc68c7
  
• Proton version:1710947987 experimental-9.0-20240320

I confirm:

• 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

[Kupferdrache]

anything left I can do for the regression issue in experimental-2024 03 20 ?

[Blisto91]

@Kupferdrache Hi here and thank you for the report.
A fix for the issue have arrived in the Experimental Bleeding Edge beta branch. It should get pulled in to regular Experimental next time it pulls in dxvk updates.

[Jopp-gh]

I get similar errors

got this warning after installing frostpunk from gog with latest patches. There are 2 installer scripts, both fail. Looking at the Configuration of frostpunk, we see env vars as well as dll overrides are missing, therefore the installation process didn't conclude successfully.

I just wonder why Frostpunk needs winevulkan.dll in system32, I thought Frostpunk is only 64bit? cannot find any meaning in this. Also, the wine protocol shows a RLIMIT_NICE is <= 20, unable to use setpriority safely error but changing the nice value does nothing, I already tried. This isn't a proton thing but a DXVK issue, if I switch DXVK off in configurations, Frostpunk loads to the start screen but with visual errors (screen is almost pitch black and textures are floating all over the screen).

Lucky me I had a backup of a previous, perfectly working Frostpunk too. So I used this copy on my new harddrive and got another error dialog

this time I've a choice - if I click ignore (3rd button on the right) twice, the game works. But this error dialog should not pop up at all because my previous copy of FP worked perfectly. Unfortunately, I did not take a note about my past installation of this game, as this is not an usual issue.

[Blisto91]

@Jopp-gh hi there. Please attach a full proton log if you can.

Edit: note that system32 is the folder containing 64bit files

[Jopp-gh]

Edit: note that system32 is the folder containing 64bit files

oh, sounds pretty counter-intuitive to me

Thanks, in the meantime I got frostpunk up and running, all I had to do was to change DXVK to 2.2 or 2.3. DXVK 2.3.1 seems a regression.
Let me know if you still need my log.

[Blisto91]

That together with your error popup above makes it seem like it is the issue Kupferdrache reported. This have already been fixed on dxvk master.

[burghoffdavid]

Leaving for visibility, resolved, see UPDATE below.

Original Post

Hmm I tried using the latest GE (9-4), which should include the latest dxvk changes and I still can't get the game to launch, might be a different issue. logs attached.
Notable exception:

567.534:0064:0070:trace:seh:dispatch_exception code=6ba flags=0 addr=00006FFFFFC1CE87 ip=6fffffc1ce87
567.534:0064:0070:warn:seh:dispatch_exception RPC_S_SERVER_UNAVAILABLE exception (code=6ba) raised
567.534:0064:0070:trace:seh:dispatch_exception  rax=0000000000a2d7d0 rbx=0000000000a2dab8 rcx=0000000000a2d7d0 rdx=0000000000000000
567.534:0064:0070:trace:seh:dispatch_exception  rsi=00000000000000cc rdi=00000000007f5b80 rbp=0000000000a2d8a0 rsp=0000000000a2d7b0
567.534:0064:0070:trace:seh:dispatch_exception   r8=0000000000000000  r9=0000000000000000 r10=00000000007fa880 r11=000000000000001b
567.534:0064:0070:trace:seh:dispatch_exception  r12=0000000000a2dab8 r13=0000000000e35f30 r14=0000000000e35f30 r15=00000000000000b8

What is weird that I can't get the game to launch on older Proton versions (like 6.3-8 or 8.0-4
) either, even though they were reported as working on protondb.

steam-323190.log

UPDATE:

Figured it out, seems like Frostpunk doesn't like having set SDL_VIDEODRIVER="wayland"....
Set SDL_VIDEODRIVER="" %command% as launch options and it works 🥳

Never had this issue on any other game, no clue why frostpunk behaves differently....

[italoghost]

Replying to #412 (comment)

Thank you! I am using the following environment variable SDL_VIDEODRIVER='wayland,x11,windows' and I didn't know why FrostPunk wasn't launching.