protonscr

Frostpunk 2 (UE5, DX12): White UI elements (Map & Council) on Proton 10, game fails to start on Experimental

vkd3dclosed
HansKristian-Work/vkd3d-proton#2816 · opened 2026-02-11 by Fakerinc · updated 2026-02-11 · 3 comments · github
FFakerinc 2026-02-11 github

Tried playing Frostpunk 2 the first time on linux. Had to tinker around a bit until I found a playable setup.
Main issue:
Under proton 10.0-4 the game started and with a few Launch options, it is very enjoyable to play. Two things are buggy though.

  1. The frostland map (if you zoom out of the city map) is entierly white with only markers visible. Still playable as normal I guess. New locations can be discovered and everything reacts as it should gameplay/UI wise. (screenshots below.
  2. Council background is almost completly white as well. In this case there is no gameplay implication (I think), but would be nice to see whats going on

Frostland map
Image

Council
Image

Game fails to start and crashed shortly after launch under:
(Same behavior after deleting compatdata)

Proton 9.x
Proton Hotfix
Proton Experimental (default and bleeding edge)
GE-Proton10-29
GE-Proton10-22

Played around with the following options/settings

  • DX11 forced → engine reports not supported
  • -vulkan → game does not start
  • DLSS on/off → no change
  • Windowed / fullscreen → no change
  • HDR disabled
  • Minimal launch options used
  • Prefix deleted and regenerated

Software information

Frostpunk 2 (Steam AppID: 1601580)

Engine: Unreal Engine 5

Rendering: DX12 only (no DX11 / Vulkan)

Current Launch options
PROTON_LOG=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only VKD3D_CONFIG=dxr11 %command%

System information

Distro: Ubuntu 22.04 LTS
GPU: NVIDIA RTX 4060 Laptop
Driver: NVIDIA 535
CPU: x86_64
Desktop: (z. B. GNOME / KDE – optional)
VKD3D-Proton version: 10.0-4

Log files

Proton logs:

steam-log.zip

Ddoitsujin maintainer 2026-02-11 github

Driver: NVIDIA 535

Please....

We're at 590 now, 535 is like three years old or something and we don't support drivers that ancient. In fact we removed a whole bunch of workarounds specific to that driver branch not that long ago.

FFakerinc 2026-02-11 github

Oh sorry, I thought I checked for newer ones but apparently I did not. I'll try the latest one later and I'll write my findings here.

Thanks for the quick answer!

FFakerinc 2026-02-11 github

Well, I could have saved hours of debugging and playing around, if I updated the drivers.

Thanks @doitsujin ! Works like a charm. Performance is a bit more laggy now, but I'll see if it stabilizes after a while or with some other launch options
Sorry to have bothered you, without "real work" to be done

Proton versions

Launch options

Launch lines