Proton: 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 https://github.com/ValveSoftware/Proton/issues/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:

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

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

[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 :+1:

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

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

[DanielKrsek]

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

[EtienneK]

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

[OvermindDL1]

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.

[axelsimon]

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)

[kisak-valve]

Hello @axelsimon, does PROTON_USE_WINED3D=1 %command% in the game's launch options and Proton 3.16 make a difference? If it does, can you try mesa 19.0.0-rc2 or newer (without any workarounds)?

[axelsimon]

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:

[Evernow]

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

[OvermindDL1]

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

[Evernow]

@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

[OvermindDL1]

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

[ryanmusante]

With nvidia 396.54.09, I encounter no issues.

[japdlsd]

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)

[davidak]

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

[Ruedii]

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.

[doitsujin]

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.

[Ruedii]

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.

[LtSich]

The game run fine with Proton 4.2-9. But don't start (stay on black screen) with Proton 4.11.
You have to keep VSync ON or the game will have very bad performance.

The bad thing is that regression with Proton 4.11.

[kisak-valve]

Hello @LtSich, can you retest with Proton 4.11-2? If can reproduce the issue, then please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

[LtSich]

Hi, thx for the anwser.
You can find my system specs here : https://gist.github.com/LtSich/7a5c7dbd795a1bb69c5ce1845599f485

I can confirm that the game run fine with 4.11-2.
Thx for the info :)

[jul-ben]

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

[LtSich]

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.

[jul-ben]

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.

[LtSich]

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.

[juliotux]

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.

[nstgc]

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.

[jul-ben]

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

[jul-ben]

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.

[Vladislavuz]

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

[kisak-valve]

Frostpunk (323190)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4159.
@Terradice posted on 2020-08-28T09:33:05:

Compatibility Report

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

System Information

• GPU: GTX 970M
• Driver/LLVM version: nvidia 450.66-15
• Kernel version: 5.8.4
• Link to full system information report as Gist: https://gist.github.com/Terradice/3fc5856b31e0aa0fdb0d175bc6a933e2
• Proton version: Any

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

Game crashes on start.

Reproduction

Launch the game.

[kisak-valve]

Hello @Terradice, looking at your log, Vulkan failed to initialize on your system.

The lines of interest from the log:

err:vulkan:wine_vk_instance_load_physical_devices Failed to enumerate physical devices, res=-3
err:vulkan:wine_vkCreateInstance Failed to load physical devices, res=-3

I'm guessing you're on an nVidia Optimus laptop running Arch Linux, and you don't have Vulkan drivers installed for the Intel chipset. You can either install vulkan-intel and lib32-vulkan-intel or look into using prime render offloading for the nVidia GPU.

[Terradice]

Hey @kisak-valve , Thats a good guess! I usually run my games through primus so they run on my dedicated gpu instead of my intergrated, I decided to not use it for the log file since i think our first priority is getting the game running in the first place.

After installing vulkan-intel and lib32-vulkan-intel, steam gave me this dialouge, and launched the game successfully.

However, trying to launch with primusrun (primusrun %command%) i encounter yet another crash.
steam-323190.log

[Terradice]

Hey, i realize now this may not be a proton issue, after doing a full system upgrade bumblebee says there are no devices detected, i will try to resolve this later and launch the game again

[Terradice]

After resolving the issue with primus and launching the game again, still getting a crash.
steam-323190.log

[DrKJeff16]

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 SNAP 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 Snap: ~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