Your CPU compiles shaders, the GPU runs them. Vulkan shader pre-processing is a form of pre-compiling all the possible shaders your GPU might need before it runs the game (to avoid stutters and freezes later). This is done on the CPU.
this post was submitted on 22 Nov 2023
23 points (87.1% liked)
Linux Gaming
15304 readers
15 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 1 year ago
MODERATORS
Thanks! Makes sense. I saw "shaders" and linked it to the GPU.
I don't believe that there's a shader compiler that runs on the GPU.
Valve created the ACO shader compiler, but it's only for AMD GPUs.
ACO runs on the CPU.
The output it produces is for AMD GPUs.
Oh, my bad. I think I misremembered.
I ran into this exact same problem and spent a painfully long week trying to fix it. Unfortunately I couldn't... My only solution was to switch distros and the problem disappeared. I went with Fedora and now every game works like a dream. I still don't know what the issue was but it seems to be something to do with having an AMD system and using steam on Ubuntu.
Probably not the solution you're looking for, but it is a solution!
You can turn off shader precompilation in Steam, but that's not tied to the distro.
If you have it off, you won't need to have the pass run before starting a game, but then the problem that it was aimed at solving comes up -- shader compilation has to happen during gameplay, and this can cause momentary hiccups when a shader is used for the first time.
Steam can optionally do background shader compilation, in which case it'll run at some point after updating a game, rather than right before a game runs. That may or may not be what one wants.
Interesting! I think I'll keep it on and just deal with the fact that it runs on CPU and takes a while, then. I was just wondering if it running on CPU was a mistake or something wrong on my part.
My guess is your mesa driver was old so you didn't have graphics pipeline library enabled by default. distros doesn't differ but packages.
Nope. Had the latest mesa drivers I could get and it still didn't work.
All-amd Ubuntu user here. No issues.