Title. I always skip them and don’t notice any detrimental effects at all. I used to let them run every time, but I don’t want to wait 5 minutes for every patch update bug fix anymore
Title. I always skip them and don’t notice any detrimental effects at all. I used to let them run every time, but I don’t want to wait 5 minutes for every patch update bug fix anymore
Theres a hidden option to make it multi core, which (on a machine like a threadripper) can insanely speed up the process.
edit: here’s a fourm post describing how to
Well holy shit I didn’t know that existed!
Presumably they… don’t have it GUI exposed because they don’t want to give the average user the ability to potentially fully lock up their CPU and totally crash their PC?
Do you know where this option is?
Same instructions from the other link posted, different source: https://forum.zorin.com/t/speeding-up-steam-shader-processing/50008
1. Navigate to ~/.steam/steam (This should be a symlink to wherever your Steam install is located). If the folder has a steam.sh then it is the correct folder.
2. Make a file called steam_dev.cfg
3. In that file put:
unShaderBackgroundProcessingThreads x4. Replace X with the number of threads to use. (See below.)
5. Save the file and restart Steam if it was running.
For X, modern processors generally support two threads a core. If you’re using a 4 core processor, you could have 8 simultaneous threads. if you’re using an 8 core, 16, etc. You don’t want to use that number for X though, or Steam may hog your CPU enough to make your system sluggish. The original poster recommends your max threads, minus 4 to 6. I’m using 10 out of 16 threads, personally.
As the Reddit thread notes, despite the name of the setting, it does work for foreground processing as well as background. One thing the thread doesn’t warn about is that if you keep Steam open and a game updates, Steam may start working on these in the background, if you have background shader processing turned on. If you’re doing CPU intensive work, you may want to close Steam or turn off background shader processing to keep Steam from monopolizing your CPU.
I always had 4
fossilize_replayprocesses running when Shaders where being compiled. So I assume the default value is 4. I’ve created this file with a value of 12 now, to see if this makes a difference. Thank you both of you for posting and also copying the instructions to preserve them.Hope it helps!
Whoops, yeah should have probably put a link in the main thing,
here’s a fourm post describing how to
I think mine was on by default. It maxes out the CPU for several seconds.