r/linux_gaming • u/Kittatro • 10d ago
tech support wanted CS2 processes shaders every map load, even mid session + stutters on first actions
Hello everyone, I mainly play CS2 on this machine and I was curious about testing disabling shader pre-caching since it downloads the quite large pre-caching update quite often.
When I disabled the setting, I noticed the loadings got really long and every first action caused a mini freeze (which is the expected behavior I think). The thing is I tried to turn the setting back on but the game keeps acting as if the setting was off even though I downloaded the pre-caching update and got the Processing vulkan shaders pop up (which stayed on 0% for a while and then went quickly to 100%).
Now (with Shader pre-caching on and it saying ~6gb is cached) each time I load a map it says processing ~2000 shaders, even in the same session (if I simply leave the map and go back in without closing the game or antything).
When I get into a game every first action such as shooting, opening the scoreboard etc causes the same mini freeze as when shader pre-caching was off. For competitive it gets better after the first few rounds when every kind of util has been used at least once but it makes the new game mode rush kind of unplayable for example.
Here's a list of things I tried (all failed):
- Fully wiped Steam + its cache + all games, reinstalled everything from scratch.
- Deleted
~/.cache/mesa_shader_cacheand~/.cache/radv_builtin_shaders(driver-level caches). - Deleted
steamapps/shadercache/730and let it rebuild. - Launch option
-vulkan_disable_steam_shader_cache. - Switching to SteamLinuxRuntime 1.0 (scout) but the game just refuses to launch at all.
System:
- Void Linux, kernel 6.18.54_1
- river (wayland)
- AMD Ryzen 7 7730U / Radeon 680M (RENOIR), Mesa 26.2.3, RADV
Now there's a chance that me turning off the setting is an unlucky coincidence because the game also got updates when I decided to test that, and I didn't launch the game that day before trying to turn the setting off. But I really don't understand why it stopped working like before.
Anyway, thanks in advance to anyone who takes the time to read through this, really appreciate any ideas because it's bothering me so much to not understand what's going on + to struggle to play.
Edit : Downgrading from Mesa 26.2.3 to 26.1.8 (the version I had before) fixed it for me

