It feels like I mine bitcoins for our Great Daddy Gaben every other update, setting my CPU at 100% for a long time.
I know it makes difference (to skipping it and eating lags), it works, but how it doesn’t use previous literal gigabytes of generated shaders, starting from 0% every time? Why it takes so much time?
I feel like I’m a dumbass and I miss something obvious. Or I just feel like I’m alone with it? Do you guys all deal with it?
Am sitting at 66% percents, my PC heats like it renders video in Premiere, just to let me play the game I’ve played yesterday again. Guess all my recycling and replanting routine can fuck right off with that power consumption. Sorry, nature, I tried.
But anyway if you are tired of it or knows some tricks, write what’s on your mind.
What GPU are you using and what driver version? Both AMD and Nvidia have added support for VK_EXT_graphics_pipeline_library which greatly improve performance while compiling. I prefer just skipping shader compilation, since most games will perform fine doing it while playing.
1060, 6Gb x i5 8600
535.113.01-0ubuntu0.22.04.3
It’s faster than when I first came to Linux, sure. And I see that my 6yo mid setup doesn’t work okay in big games if I skip this, and is slower than most recent builds of the same price range.
I think honestly if you’re not willing to upgrade your pc there’s not a lot you can do other than wait for potential optimization
Shader caching on a modern pc for anything but big chunky triple a games takes less than 5 minutes
Yup, shader updates on Steam dropped significantly when I upgraded my GTX 960 to an RX 6650XT.
It still takes some time on my 3500U APU laptop, but I rarely play anything on that system.
Ultimately this is what it’s running in the background: https://github.com/ValveSoftware/Fossilize
The idea is to make sure your graphics card shader cache is full with everything the game may use at some point, enabling smoother play and less hitching.
I think on NVIDIA, the cache ain’t that big by default so it may be recompiling everything from scratch, whereas it’s less noticeable on AMD systems because it’s already compiled it so only compiles what’s changed/new.
This issue suggests it’s currently pretty broken on NVIDIA right now: https://github.com/ValveSoftware/steam-for-linux/issues/9803
Didn’t know they have a github account. Thanks for pasting these links. I’d study this Q more while another reshadering is going on.
What isn’t broken with Nvidia? :b
This is not a Linux specific issue though it’s worse on Linux because vulkan shader processing happens for almost every game. I remember people on windows complaining that The Last of Us was compiling shaders for several hours when first launched and that if shader compilation was skipped the game was laggy as hell(which is not a surprise considering how poor the game ran even after shader compilation)
I clicked on CS2 at 3. At 5 it was at 80%.
honestly I just run a game and go watch a vid till it starts, sometimes multiple vids if there was an update.
That or I just skip it, actually it doesn’t lag that much from skipping half of the time
Do you have an Nvidia card?
To my sorrow, yes. How fucked am I?
Irreparably and permanently.
Valve put a lot of work in improving the shader compilation process for AMD. It’s smooth as butter and very, very fast.
me, collecting my anus bones and fitting them together
Ha, I’m happy for you having a better time, and it sounds like a good reason to switch.
I agree that’s very annoying sometimes but at the same time very beneficial for in-game performance as it greatly reduces the amount of computations the game has to do at runtime. If you have a powerful enough PC or the game isn’t very demanding you can just disable shader pre-caching in steam settings and it shouldn’t matter much but it’s a real life saver for more demanding titles and imo worth all that wait.
Yeah, I disabled it and never notice any issues, but I only play BG3 and Guildwars2.
I hear you. I’m really just venting.
The catch is those non-demanding games are fast to reshader. It’s only when you face a heavyweight release this starts to matter, and wastes time accordingly :)
I don’t have this issue using jc141 releases