Did you let it calculate fully once? It should sure the results for the next time then...

Do you use the game files with another OS, probably Windows or another Linux with slightly different drivers? I once had a similar issue, using the same game files with different drivers and different Linux distributions.

I have the same problem on my PC (100% Manjaro Linux) since at least 4-6 months which I especially noticed playing Rocket League.
Sometimes it launches instantly (2/10) and the other times it displays the vulkan shader progress bar (even after I restart the game).

BUT when I skip it (I have done this for Halo and Rocket League) the games did both still run - I never had that a game after skipping wouldn't load.

Multiple other titles do not have a problem with this (idk the names but I have played a lot of Windows titles using Proton and a lot of them do never ask this twice or do complete the progress bar so fast that I don't really care 1-4s).

I think the shader jobs are broken up incrementally and simply updated over time and as the Proton & shader process are refined are repeated. Gets annoying, but I usually let Steam do its thing and patiently wait. Good time to catch up on some docs, surf the web or doodle in Inkscape -whatever. My favorite thing is when I have 5 games in queue for shader cache with one being around 5GB and two others at about 2GB -you get the idea --yes, that happened to me... twice.

What ya gonna do.

I made the question because it happened two or three times with the same game ("a hat in time"). Each time i allowed the extremely long process to end while doing something else, but for whatever reason i had to do it again (maybe related to the game crashing?). Hope the way steam is handling this process improves.

I dont use the same library files in different machines (yet), but i would try that sometime to see what happens. Im also using manjaro.

+1, I have the same issue on "a hat in time".

It takes forever, every time I launch the game.
That by itself is a turn off.

Then it will crash when I am configuring my controller.
I cant even play the game anymore.

is there any chance of exiting the game after the lengthy shader compilation and before the crash?

then running it again to confirm it doesn't do it again unless it crashes or something gets updated (game/proton/related OS components)

Originally posted by Marlock:

is there any chance of exiting the game after the lengthy shader compilation and before the crash?

then running it again to confirm it doesn't do it again unless it crashes or something gets updated (game/proton/related OS components)

Thanks for the recommendation, that did get ride of the "processing vulkan shaders" issue.

Same here - for same games I play several times without any updates. E.g. Shadow of the Tomb Raider. In addition, I often see dowanloads for it telling something about shaders. What's the catch here? It'*s an "old" game - it should be enoug

Originally posted by Wurzelzweig Linux:

[...] In addition, I often see dowanloads for it telling something about shaders. What's the catch here? It'*s an "old" game - it should be enoug

that's shader caches...

they change when the game changes... but they also need to change when vulkan changes, etc

so even if the game itself gets no update at all, there may be need for shader updates

you can disable fetching shader caches from steam servers in steam settings... this will save you some download band (useful in metered connections) but will mean shaders will have to.be compiled locally (which either takes time at game load or may cause some stuttering while playing, if each shader it's compiled on the fly when needed and takes just a few milisseconds longer than it should)

Question are you guys using Nvidia or AMD Drivers.

I ask since for some reason on Nvidia Drivers 455.38 it takes way too long to process now compared to 440.100.

Also check these posts out

https://github.com/ValveSoftware/steam-for-linux/issues/7472

https://github.com/ValveSoftware/Fossilize/issues/84

this is getting ridiculous Ubuntu 20.04 , Vega 64 , every-time I launch doom it sits their redoing all the caches for a good hr , and skip does jack

Steam -> Setting -> Shader pre-caching untick Enable shader pre-caching. And it will stop the shader pre caching. You may or maynot experience some initial lag in games. But i do not see any difference.

I know this is a older topic, here is my solution:
I had enabled Experimental Proton and the game (in my case Rocket League) had to cache shaders for every startup.
After changing to a specific Proton version (in my case 6.3-5) it happens very rarely

Originally posted by @R+5:

is there a way to make the process once, so i dont have to "skip" it (when i skip it, sometimes the game wont load).

hi. i have a same problem on linux. if you skipped it but game wont load, you can close steam window (but not in the tray). this must work, like in my case.