SteamVR-for-Linux VS Fossilize

**Links:**Github issue post 1: https://github.com/ValveSoftware/SteamVR-for-Linux/issues/21

When Vulkan drivers are ready maybe the Asahi Linux perhaps also be ready to run some SteamVR apps https://github.com/ValveSoftware/SteamVR-for-Linux/blob/mast...

A guess, but SteamVR can't recover from VR applications crashing causing all future ones to not work, might be Home crashing first. Try turning off Home, and restarting.

steam VR Linux issue tracker

I tried to launch Alyx after the setup, and got a 303 error like described here: https://github.com/ValveSoftware/SteamVR-for-Linux/issues/572

From there I went to the SteamVR for Linux Github to see if any bugs related to this were reported.

Yes, the beta - SteamVR Beta Update also has the same problem, but with extra bugs like this issue for "Shared IPC Compositor Init Failed (303)". The linux_v1.14 - Older build, for Linux users also has the same problem. The None beta version is the only one I can use, as it doesn't show the "Shared IPC Compositor Init Failed (303)" error.

I posted an issue on the SteamVR for Linux Github, but that's basically been abandoned so I'm trying my luck here.

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.