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

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

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

Crashing stops for me when esync is disabled.

@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

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

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.

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.

Nice catch @Azarius ! this solved the issue for me

I also have this issue.

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.

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

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.

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

"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?)

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.
• [x] 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

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

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?

@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 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.

@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

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.
• [x] 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.

@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?

@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

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?

@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 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... ^.^;

Hi,
does some have solution for black screen only with game cursor + music?

Can confirm that the game crashes on Autosave and on Quicksaves.

Can confirm that the game crashes on Autosave and on Quicksaves.

Only sometimes, but yes it definitely happens.

However I don't think it's a wine issue as the same issue happens on a friends Windows 10 system as well, the game engine itself seems buggy.

I'm experiencing severe flickering of the snow on large parts of the screen, but otherwise the game is playable (as my two 4-hours straight sessions would tend to confirm).

I've tried disable esync with PROTON_NO_ESYNC=1 in the game launcher properties (PROTON_NO_ESYNC=1 %command%) but it doesn't appear to change anything.

The resolution is down to 1440×900 (I would need to check) and graphics details down to low (again, from memory).

Any clues as what else I could try?

Another smaller issue is that on each launch, Steam goes through the "first time install" and it takes a while to launch the game.

Here are my specs by the way, I am aware the built-in GPU is a bit weak, and maybe that's the cause of the problem, but it would seem odd given everything else in the game runs normally.

OS: Fedora release 29 (Twenty Nine) x86_64
Kernel: 4.20.6-200.fc29.x86_64
Resolution: 1920x1080 (desktop), 1440x900 (game)
DE: GNOME 3.30.2
WM: GNOME Shell
WM Theme: Adwaita
Theme: Adwaita [GTK2/3]
CPU: Intel Core i7-8650U CPU @ 1.90GHz
GPU: Intel UHD Graphics 620 (Kabylake GT2) (aka rev 07)

Hi @kisak-valve, thanks for the quick reply! I'm actually already using Proton 3.16 (-6, to be specific).
Just tried to use WINED3D set to 1, but it creates a really weird effect, like a black overlay on the whole game.
To illustrate, this is in game:

I am able to run the game pretty much flawlessly, except for one issue, when I try to alt tab out of the game, it crashes 100% of the time. I am on the latest 3.16.6 Proton version, and on Manjaro KDE. Nvidia driver version 415.27

Any recommendations? Pretty much only ever crashes when alt tabbing

Any recommendations? Pretty much only ever crashes when alt tabbing

I'm wondering if that's one of the many NVidia driver bugs, it doesn't happen with an AMD Radeon here, can and do alt-tab with impunity (Mesa 19, KDE, etc.. etc..).

@OvermindDL1 I actually was able to fix it! Just go into the in-game settings and switch to Windowed mode! The game runs absolutely flawlessly now! Easy platinum

Windowed mode makes sense, it no longer controls the entire display at that point. :-)

With nvidia 396.54.09, I encounter no issues.

Hi @kisak-valve, thanks for the quick reply! I'm actually already using Proton 3.16 (-6, to be specific).
Just tried to use WINED3D set to 1, but it creates a really weird effect, like a black overlay on the whole game.
To illustrate, this is in game:

Hi @axelsimon , have you managed do get rid of this black overlay effect? (I have the same problem with the same PC specs)

The game starts, intro and menu works, but it crashes in the loading screen!

0048:fixme:dbghelp:elf_search_auxv can't find symbol in module
AL lib: (EE) ALCmmdevPlayback_mixerProc: WaitForSingleObjectEx error: 0x102
Unhandled exception: page fault on read access to 0x00000000 in 64-bit code (0x0000000140c2dc47).
0048:fixme:dbghelp:elf_search_auxv can't find symbol in module
0048:fixme:dbghelp:interpret_function_table_entry PUSH_MACHFRAME 6
0048:fixme:dbghelp:interpret_function_table_entry PUSH_MACHFRAME 6
Register dump:
 rip:0000000140c2dc47 rsp:00000000036df310 rbp:0000000000000000 eflags:00010246 (  R- --  I  Z- -P- )
 rax:0000000000000000 rbx:0000000000000008 rcx:0000000000000000 rdx:0000000000000000
 rsi:0000000000000001 rdi:0000000000000000  r8:0000000000000004  r9:00000000ffffffff r10:00000000036defd0
 r11:0000000000000246 r12:00000000010611c0 r13:0000000000000000 r14:000000003f4d5cc0 r15:0000000001061898
Stack dump:
0x00000000036df310:  0000000000000000 000000010000001e
0x00000000036df320:  0000000000000001 0000000140c2eb0d
0x00000000036df330:  00000000036df380 000000006a419878
0x00000000036df340:  000000003b502c20 000000006a366220
0x00000000036df350:  4023426240ae9fbd 3ed52f0b00000000
0x00000000036df360:  0000111e8b3ab38e 3f4ce4633f39704c
0x00000000036df370:  00000000ffffffff 000000003f4d5540
0x00000000036df380:  0000000000000002 000000003fa3b370
0x00000000036df390:  00000000010611c0 000000003f4d54e0
0x00000000036df3a0:  0000000000000000 0000000140dfa893
0x00000000036df3b0:  0000000000000000 0000000000000000
0x00000000036df3c0:  0000000000000000 000000003f4d5b72
Backtrace:
=>0 0x0000000140c2dc47 EntryPoint+0xff46fb67() in frostpunk (0x0000000000000000)
  1 0x0000000140dfa893 EntryPoint+0xff63c7b2() in frostpunk (0x000000003f4d54e0)
  2 0x0000000140dfa649 EntryPoint+0xff63c568() in frostpunk (0x000000003f4d5540)
0x0000000140c2dc47 EntryPoint+0xff46fb67 in frostpunk: movq	(%rdx,%r13,8),%rdx

Full log: https://gist.github.com/davidak/643cec710ba59e2c48e1213c40fb6f80

Steam System information: https://gist.github.com/davidak/b056d26180f96c71a5a095f48253b149

OS: NixOS 19.03.173028.7152cb297ad (Koi) x86_64
Kernel: 4.19.56
Shell: bash 4.4.23
Resolution: 1440x900
DE: Pantheon
WM: Mutter(Gala)
CPU: Intel Xeon X5460 (4) @ 3.800GHz
GPU: NVIDIA GeForce GTX 960
NVIDIA Driver Version: 418.74
Memory: 1206MiB / 7980MiB
Proton: 4.2-9

It seems a lot of players are hitting LLVM bugs on this with older LLVM versions.

Does the form need to be adjusted to add a separate line for LLVM version? This is a matter of response to nVidia users not properly including LLVM version on the form.

LLVM version is listed in the Mesa Driver version (because Mesa uses LLVM itself) but not the nVidia one.

DXVK itself also uses LLVM, and hence the requirement.

As a note, would including a specific version of LLVM with Proton for DXVK fix these issues with LLVM version, or would this cause weird issues with Mesa's LLVM use?

If linking DXVK to a specific LLVM version is necessary, maybe shipping it hard-linked might work for this, in order to avoid Mesa linking to the version as well.

DXVK itself also uses LLVM, and hence the requirement.

No, it doesn't, not sure where you got this from. The only thing that uses LLVM is the AMD graphics drivers.

DXVK itself also uses LLVM, and hence the requirement.

No, it doesn't, not sure where you got this from. The only thing that uses LLVM is the AMD graphics drivers.

You're right. While derived from LLVM's base logic, the core libraries used (SPIR-V and Vulkan) do not require LLVM. nVidia likely uses a use-specific implementation of the logic method, while the AMD driver uses LLVM itself, which is more than capable of being adapted for the task. My mistake there.

Dependent on the LLVM-based logic of SPIR-V is not necessarily dependent on LLVM.

Enough off topic there, though.

Just to be sure, whatever version of Proton you are using ALT+TAB is not working, right? (Even in Windowed Full-Screen)

Just to be sure, whatever version of Proton you are using ALT+TAB is not working, right? (Even in Windowed Full-Screen)

it's work for me.

Just to be sure, whatever version of Proton you are using ALT+TAB is not working, right? (Even in Windowed Full-Screen)

it's work for me.

Could you tell me what are the details of the distribution (name, version, kernel, driver, etc.) and the version of Proton you are using?

In my case, I tried playing Frostpunk full-screen, windowed full-screen, with and without v-sync on and it never worked. Not to mention some crashes I can encounter.

If you do not mind, I would be interested in knowing what your experience with Proton + Frostpunk is.

No particular config....
Here is my system specs : https://gist.github.com/LtSich/0d640266f036b1e1612101577eb077b1

Last version of proton, debian testing, nvidia drivers from experimental, xfce...
I just run the game with gamemoderun, but I doubt this change anything about that.

About the crashing problem:

I noticed that this problem occurs in autosave, but appears in other events like zoom in to city from the frostland, temperature rising or lowering, storm comming, pop-ups opening, etc. Basically, there is no way to predict when the game will crash. Here is my proton log for the game:
steam-323190.log

Note: the script that deletes the autosave did not worked for me.

System info: https://gist.github.com/nstgc/6d0c645079dcc4f53adb790813994f7b

I exceed the minimum system reqs, but even at the lowest setting the game runs slower than I'm comfortable with (between 115 and 20 FPS). Any advice? I've tried Glorious Eggroll's Proton as well as ValvE's.

Since Proton 5.0.1, the game does not launch. It was working well without tweaks with 4.12-11.

Here is the Proton log but I do not see anything out of the ordinary at first glance.

steam-323190.log

Since Proton 5.0.1, the game does not launch. It was working well without tweaks with 4.12-11.

Here is the Proton log but I do not see anything out of the ordinary at first glance.

steam-323190.log

Actually, I tried to launch some other title with Proton 5.0.1 and I think it could be a prefix issue.

I tried a few things and I am now able to run Frostpunk with this version. The only thing that worked was to have a clean prefix. I would recommend to emphasize how important it would be for people having issues with this version to try it with a clean Wine prefix before reporting the problem.

If someone can figure out exactly what the problem is, that would be great.

The game crashes when the settings are medium or higher. At low settings, the game works well.
hardinfo_report.txt
steam-323190.log

Significant performance downgrade.

In ProtonDB 5.0.9, even playing in less than FHD and Medium Settings with no Post-Processing, I hardly get 20FPS at best (90ms average delay). V-Sync didn't help in either way.

Notable increase: DISABLE FULLSCREEN AA (went from 5fps to 15. Not playable, but worth doing.)

Input lag

Calculated by hand and resulted in >100ms delay. Deal-breaker for me, personally.

Stability

Haven't tested save filing, but game doesn't crash (probably due to appropriate SWAP Memory [~1.5 x RAM], given this game DEVOURS VIRTUAL MEMORY)

Specs:
OS: Pop! OS 20.04 (64bit)
CPU: Intel i7 4790 3.6GHz, Quad Core, (unparked and optimized for full performance).
RAM: 16Gb
SWAP: ~25Gb
GPU: GeForce GTX 1060 3Gb // GPU Driver: NVIDIA Driver 4.6.0 (latest ATM)
Disk: SATA HDD Partition, ~1Tb
SteamPlay: ProtonDB 5.0.9```

Any keys I bind appear to come up as undefined, latest game, GE proton based on proton 5.9 (Nothing later works to launch the game for me)

GPU: GeForce GTX 1050
Driver version:  NVIDIA 460.39
Kernel version:  5.10.11-200.fc33.x86_64

Proton 5.13-5

Music was playing, but screen was black

Proton 5.0-10

Game launched successfully

Hello @Endle, 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 put it in a gist, then include a link to the gist in this issue report.

Hi @kisak-valve

5.0-10.zip
5.13-5_regression.zip

My system information: https://gist.github.com/Endle/51f11fd9d3986b5881b19dbc6d9ef5bf

An error occurs while the mission is being loaded. The problem is specific to SteamOS.
steam-323190.log

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

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.

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.

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.

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.

Replying to https://github.com/ValveSoftware/Proton/issues/412#issuecomment-461460278

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%

@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 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 !

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.

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

@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.

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.

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

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

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.

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.

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 :partying_face:

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

Replying to https://github.com/ValveSoftware/Proton/issues/412#issuecomment-2062450113

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

Had been running into an issue with Frostpunk crashing immediately on start (without even rendering a window), eventually determined the cause was having the ALSOFT_DRIVERS environment variable set (to any valid OpenAL driver(s)). Resolved the issue by setting ALSOFT_DRIVERS="" %command% as the launch options, or ensuring the environment variable wasn't set prior to launching steam.