pre-loading map and shaders popup persistent

[mazzelgg]

the pre-loading map and shaders popup is persistent throughout the game, not able to see game time or team soul count.

 

[noobdoomguy8658]

Experiencing this as well.

Some specs if that matters:
- OS: Linux (linux-lts kernel, KDE Plasma Wayland)
- GPU: GTX 1080
- CPU: Ryzen 5 5600x
- RAM: 16 GB

 

[dragonfly]

also having this issue on
Ubuntu 24.04.1 LTS
6.8.0-48-generic
AMD Ryzen 7 3700X 8-Core Processor
TU116 [GeForce GTX 1660 Ti]
NVIDIA Driver Version: 535.183.01

 

[nojusr]

Also getting this on NixOS unstable.
- $ uname -a: Linux koronis 6.11.5-zen1 #1-NixOS ZEN SMP PREEMPT_DYNAMIC Tue Jan 1 00:00:00 UTC 1980 x86_64 GNU/Linux
- CPU: Ryzen 9 3900X
- GPU: NVIDIA RTX 2070 SUPER
- GPU Driver version: 560.35.03

A naive hunch points towards this being a conflict between the fact that the game itself is trying to precompile shaders on top of proton's shader precompilation

 

[mazzelgg]

my specs
OS: Linux Mint 21.2 Cinnamon
kernel: 5.15.0-124-generic
cpu: AMD Ryzen 7 7800X3D
gpu: RTX 3090

 

[noobdoomguy8658]

Look at us, AMD CPU + Nvidia GPU Linux gang affected, all together.

 

[roboolet]

+1 on this being a linux/proton thing
OS: Linux Pop!_OS 22.04, using Wayland
Compat tool: Proton 9.0-3
GPU: Nvidia RTX 4070 (laptop)
CPU: Intel i7-12650H

 

[npsteiner]

I've also had this, also on linux. Have additionally had some game crashes only since 11/7 patch I think. If I try to rejoin a game after the crash, I get another crash unless I wait for this pre-loading map and shaders to appear.

 

[justDeeevin]

+1 on this
Linux NixOS Wayland
GE Proton9-9
Nvidia RTX 4090
Intel i9-13900KF

 

[trndyposr]

+1
Ubuntu 24.04.1 LTS
Steam, no compatibility tool
NVIDIA GeForce GTX 1050 Ti
NVIDIA driver 535
Intel® Core™ i5-6600K × 4
32.0 GiB

 

[dead inside]

+1, really annoying
Arch Linux, XFCE
Proton Experimental, DX11 in game settings
RTX 2060
i5-9400f x 6
16gb ram

 

[luka05]

+1, really annoying
Arch Linux, KDE
Proton Experimental, DX11 in game settings
GTX 1050Ti (lol)
i5-9400f
32gb ram

My guess is that "compiling shaders" already precompiles them all before launching so game gets confused about it

 

[noobdoomguy8658]

Wonder if anyone of you has pre-caching enabled in Steam. I don't.

Also, since everyone in the thread is running an Nvidia GPU it seems - what drivers you guys using? I've been using the latest nvidia-dkms (proprietary, 2024-10-31).

 

[opo.xton]

Just adding to the list of people experiencing this! Only started with the November patch.
Running Proton 9.0-3 on an Arch setup. Nvidia GPU also. I've tried launching the game with steam's shader pre caching enabled and disabled. Issue persists with both settings.

 

[justDeeevin]

Also, since everyone in the thread is running an Nvidia GPU it seems - what drivers you guys using? I've been using the latest nvidia-dkms (proprietary, 2024-10-31).

I'm using NixOS's "stable" proprietary NVIDIA drivers. nvidia-smi says that I'm on driver version 560.35.03

 

[seqsee]

I experience this also on Linux with dx11, if I change it to vulkan from the graphics it doesn't persist, however with vulkan tabbing out of the game after leaving the main menu causes the screen to be all black.

 

[mazzelgg]

I've spent well over an hour building the vulkan shaders it got stuck on 99%(i think so anyway) but after skipping it, the game started pre-loading the map and shaders and the message cleared.
Will see if the new patch requires the rebuilding of vulkan shaders again.

 

[mazzelgg]

happy to report you can skip building the vulkan shaders even after a game patch, so i guess just build the vulkan shaders if the message comes back, probably with a map change?

 

[peyote queen]

for anyone who would like a short term fix to at least see the clock/souls, add the following to your deadlock launch options:

-no_prewarm_map

I have not noticed any performance difference with this on dx11.

Also, for those who get stuck or annoyed at the hugely long shader processing times on vulkan, these are generally safe to disable if you have relatively modern hardware. When a new (major or graphics changing) patch lands, you may see stuttering on first launch, but this should go away within minutes of popping into a sandbox, running around with a few characters using abilities, etc. You are not getting much, if any, benefit from shader pre-caching running every single launch, and, as others have noted, skipping them has no negative effect on game performance. The settings can be found in Steam > Settings > Downloads.

 

[seqsee]

for anyone who would like a short term fix to at least see the clock/souls, add the following to your deadlock launch options:

-no_prewarm_map

I have not noticed any performance difference with this on dx11.

Also, for those who get stuck or annoyed at the hugely long shader processing times on vulkan, these are generally safe to disable if you have relatively modern hardware. When a new (major or graphics changing) patch lands, you may see stuttering on first launch, but this should go away within minutes of popping into a sandbox, running around with a few characters using abilities, etc. You are not getting much, if any, benefit from shader pre-caching running every single launch, and, as others have noted, skipping them has no negative effect on game performance. The settings can be found in Steam > Settings > Downloads.

`-no_prewarm_map` works for me, I also don't notice any performance difference between vulkan and dx11, although it's nice to be able to tab out of the game without coming back to a black screen. Thanks for your very helpful reply!