Steam Proton "Processing Vulkan Shaders..." every boot

[null]

I'm not familiar with how wine or proton works under the hood so I'm genuinely asking to learn more. Something that irritates me a lot is having to sit and wait like 5 minutes so that steam can process the vulkan shaders. This mainly happens on Bethesda games like oblivion and skyrim.

My question is; Why does steam have to process the vulkan shaders every time I reboot my pc or the game? Why can't it just cache whatever it processed?

[Nx Machina]

Turn it off if you do not use it.

Steam > Settings > Shader Pre-Cache.

Note: Previously they were hidden.

[Dr.Shadowds 🐉]

You can turn it off, the point of it is to render the game better, to have a smoother gameplay, reduce memory use processing shader caches, improve performance, and reduce disk I/O when updating Mesa caches, basically lower issues that may occur.

Games that use DX are not native, hence why DXVK, as it's converting your shaders that DX to VK, so your render can handle things on the fly real time, such as smooth gameplay, if you pre-cache your shaders.

[null]

Originally posted by Dr.Shadowds 🐉:

You can turn it off, the point of it is to render the game better, to have a smoother gameplay, reduce memory use processing shader caches, improve performance, and reduce disk I/O when updating Mesa caches, basically lower issues that may occur.

Games that use DX are not native, hence why DXVK, as it's converting your shaders that DX to VK, so your render can handle things on the fly real time, such as smooth gameplay, if you pre-cache your shaders.

Why does it have to do this process every time though? Isn't it going to do the same thing every time? Why not do it once and save it as a configuration?

[Dr.Shadowds 🐉]

I'm not 100% sure myself on this either, as Steam does flush cache to save space on system, last time I heard about this.
https://www.phoronix.com/scan.php?page=news_item&px=Steam-Flush-Stale-Cache

Do you have "Allow background processing of Vulkan shaders" enable? This pre-render the work ahead of time while cutting usage on cpu.

Now you could try just playing the game without the Shader Pre-Cache, and see what happens.

[PhistyMcNutz]

For the past two days, Steam decides it needs to run my CPU at 60C at 24% load for 3 ♥♥♥♥♥♥♥ hours when it opens every. single. time. 21GB of shaders just eating my CPU in the background making my room an airport runway with how loud it runs my fans (FOR 3+ HOURS.) I'm new to Linux and I was told I should have this setting on, but it's compiling shaders for games I haven't played in 7+ years, I just wish I could set it to only download the shaders for the games I want instead of eating up my 5800x for no good reason every time I power on my system.

[76561199304225685]

...

[Nx Machina]

Originally posted by PhistyMcNutz:

For the past two days, Steam decides it needs to run my CPU at 60C at 24% load for 3 ♥♥♥♥♥♥♥ hours when it opens every. single. time. 21GB of shaders just eating my CPU in the background making my room an airport runway with how loud it runs my fans (FOR 3+ HOURS.) I'm new to Linux and I was told I should have this setting on, but it's compiling shaders for games I haven't played in 7+ years, I just wish I could set it to only download the shaders for the games I want instead of eating up my 5800x for no good reason every time I power on my system.

Linux forum: https://steamcommunity.com/app/221410/discussions/

[JACKDANG3R]

How could I turn this feature off on the steam deck? That page in the settings menu has mysteriously disappeared on the steam deck :/

[Dr.Shadowds 🐉]

Originally posted by JACKDANG3R:

How could I turn this feature off on the steam deck? That page in the settings menu has mysteriously disappeared on the steam deck :/

It's under downloads, settings > downloads, I assuming desktop same for deck.

[Rena]

This happens every time I start Satisfactory. Usually it's no problem because it only takes a few seconds, but sometimes it takes 10+ minutes instead. What's up with that?

[Yandy]

This thread was quite old before the recent post, so we're locking it to prevent confusion.