this post was submitted on 22 Nov 2023
23 points (87.1% liked)

Linux Gaming

15304 readers
16 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
monolalia@lemmy.world
23
Steam using CPU to process vulkan shaders instead of GPU? (kbin.social)
submitted 1 year ago by Mounticat@kbin.social to c/linux_gaming@lemmy.world
12 comments fedilink hide all child comments
 

Hey all, I have a RTX 3060 and a Ryzen 5600G and I'm on Ubuntu 22.04. Since Steam has shader pre-processing on Linux I thought I'd ask on a Linux gaming community about this. I noticed that when Steam processes Vulkan shaders, it uses the CPU (my CPU heats up a lot and the process manager shows CPU being used while GPU is not used at all). Is there a way to make Steam use the GPU to process Vulkan shaders instead, or am I wrong and Vulkan shaders have to be processed on CPU? I'd presume that things like shaders would process faster on a GPU (it takes a long time for them to process on the CPU). Anyone know anything about this?

you are viewing a single comment's thread
view the rest of the comments
[–] tal@lemmy.today 13 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] Mounticat@kbin.social 2 points 1 year ago

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.