Fossilize VS vkd3d-proton

Note : AMD Propietary drivers for Vulkan on both Windows and Linux will have S E V E R E stuttering issues in game without fossilize shader precompilation. This is due to the lack of GPL support

Doesn't make a difference in download size at all, you don't download mesa shader caches (unless on Steam Deck, maybe), you download fossilize archives that are then compiled by the driver on your local machine. It will only affect the disk usage after it's compiled.

You're not the first to complain about fossilze (steam's shader precaching) freezing the system when processing, though I don't know why it would happen really to only some people - it must be some disk io or CPU scheduler shenanigans going on, since as you said, the GPU isn't really involved while compiling shaders.

Right, but this is part of Steam’s overall shader pre-caching system. From what I can tell when this window appears Steam is invoking their Fossilize library to do some work, possibly converting the cache from an intermediary representation to a usable binary for your hardware. I’m not sure why it only appears for some games, maybe it has to do with what graphics API the game is actually using and how the translation layer handles this. There is some discussion here but I couldn’t find official documentation (other than what’s in the Fossilize repository).

On Linux for the first run the game will precompile shaders thanks to this tool Valve made and open sourced. As a result we don't get shader stutter over here anymore.

These people seem to have the problem: https://github.com/ValveSoftware/Fossilize/issues/210

What the user below pointed out. Valve specifically uses a library called Fossilize (Open Source on GitHub here https://github.com/ValveSoftware/Fossilize) to generate the shader caches on your Steam Deck (or any machine running Proton).

Fossilize will only be helpful if it actually crashes while compiling pipelines, which I see no indication of in the bt, but still might happen I guess. Also it has some limitation with rt pipelines at the moment: https://github.com/ValveSoftware/Fossilize/issues/209 but still worth a try.

Almost all Steam games on Linux do this, it's really nice. Fossilize is an open source Linux tool made by Valve that precompiles Vulkan shaders. This only works with Vulkan though, so its use on Windows is limited, but basically everything on Linux runs through Vulkan, even DirectX games via DXVK.

Exchange my 750W PSU for a stronger one as 7900 XTX is a hungry beast, then some upscaling/AI work on (Arch BTW) Linux, testing Cyberpunk 2077 with RT once this fix is in Proton-GE. For the CPU I would obviously have to get a new mobo, and new RAM and then I would test how fast the Dwarf Fortress world generator is/slow, Cities Skylines I/II, RimWorld, Paradox Interactive games, and so on.

For DX12 games you must set the env var VKD3D_FILTER_DEVICE_NAME. But currently it might not work for some games.

If anyone is playing on Linux with an AMD GPU and has texture issues (missing FBI text on the characters' jackets is the give away), it can be fixed with applying a patch to mesa-git: https://github.com/HansKristian-Work/vkd3d-proton/issues/175.... It should hopefully be implemented soon. I think it's only limited to RDNA2.

Similar issue but different platform - CP77: Black scenery in Konpeki Plaza and No-Tell Motel · Issue #632 · HansKristian-Work/vkd3d-proton · GitHub

Vkd3d (the dx12->vulkan translation layer) developer has put up a change log for a new version that is about to be (released here) and also a pull request with more information about what he discovered about all the awful things that starfield is doing to GPU drivers (here).