Proton VS SteamVR-for-Linux

The "Metaverse" is a complete joke, and among gamers, Valve has a way better reputation than Meta. Why would they want to dilute that brand?

They already have their own platform (Steam), OS (SteamOS), VR headset (Index), their own Windows translation layer (Proton, https://github.com/ValveSoftware/Proton), their own partnership with cloud gaming (Steam Cloud Play using GeForce Now , https://partner.steamgames.com/doc/features/cloudgaming), etc.

IMO: As someone with thousands of games on Steam, there's no way in hell I'd want that linked to Facebook. I think they eventually removed the requirement to have a FB account to use a Quest, but they still require a Meta account. Yuck.

This reeks of Facebook recognizing the Metaverse as the failure that it was and opening it up because it's no longer relevant...

Or Valve's Proton[0], a tool for playing Windows games on Linux.

https://github.com/ValveSoftware/Proton

Did you mount it with the correct flags?

there is a hack to try and use your existing windows game install from an NTFS drive, but i don't recommend it as steam will try to save file names that are not allowed on NTFS...plus ext4 is faster.

From a quick search, here's what I found. It looks like you're encountering some common issues that can occur with games running on Linux through Proton, especially with the recent updates to games like Satisfactory that might affect compatibility. The log entries you're seeing related to D3DCompile2 failing to compile shader and the issues with Ternary operator and LinearToSrgbBranching not being defined, suggest that there's a problem with shader compilation. This can often be related to the version of Proton or the graphics drivers you are using. Some users have reported that the game does launch with the -vulkan option but with graphical glitches and lower performance, which indicates that the Vulkan renderer is working but possibly not optimally on your setup. From the discussions in the community, users have suggested ensuring that the latest drivers for your graphics card are installed and, if using an Intel GPU, that the Mesa drivers are up to date since Intel XeSS references were found in the logs. If you're using NVIDIA graphics, make sure you have the latest drivers and possibly set the PROTON_ENABLE_NVAPI=1 %command% to enable DLSS if you're under Vulkan. If you're using an Optimus laptop with both Intel and NVIDIA GPUs, make sure your Optimus setup is correctly configured. Some users have found success by specifying DXVK_FILTER_DEVICE_NAMES=GeForce to force the game to use the NVIDIA GPU. It's also worth noting that if you're encountering issues with DirectX 11, you might want to try forcing the game to use DirectX 10 if possible or look into DXVK configurations that could resolve compatibility issues. Lastly, if none of these solutions work, you could try running a trace with apitrace to gather more detailed logs that might point to the specific issue. If you're still stuck, it would be a good idea to report the issue to the Proton GitHub page or seek further assistance in the game's community forums where others might have encountered and solved similar issues. For more information and to find others who might have resolved similar issues, check out the community discussions on GitHub​​, Steam Community​​, and the DXVK GitHub page​​.

**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.