I'm basically still unable to play games since v1.26 SteamVR continues to have a number of problems, including all the ones found in 1.27.5.

Just received the Steam client and SteamVR updates. (The compositor and steam overlay had rendering glitches, but the game itself it worked perfectly.) In SteamVR 2 the one time it booted with async (mixed mesa/llvm versions in memory) async worked perfect in Steam overlay/compositor but with severe blur/old-frame-merges/double-vision in the game itself.Īll in quite confusing but I agree SteamVR 2 needs more work on Linux and it would be nice if there can be a Linux branch for the newest SteamVR 1 so we can continue to play without major issues. Async worked perfectly with the previous SteamVR 1 release for games. Many other things are affected too, such as Dota ValveSoftware/Dota-2#2285 and Source 1 games ValveSoftware/Source-1-Games#5043.Įdit before posting Apparently I run into #616 instead, disabling enableLinuxVulkanAsync made it work, though the error 303 IPC init failed still pops up. (Debian trixie (testing) can easily reproduce this.) The tcmalloc problems now affect Home, Alyx and with SteamVR 2 the base VR compositor/overlay itself, meaning VR cannot be used at all. With a recent Mesa and LLVM 16 (see above ref) all you get is a black screen, probably due to ValveSoftware/Dota-2#2285 (comment) and. Note: Commenters who are also experiencing this issue are encouraged to include the 'System Information' section in their replies. System Information (please complete the following information): Steam reports 'Shared IPC Compositor Init Failed (303)'.Opt into Steam client beta and SteamVR beta.I was unable to test in a Plasma X11 session due to SteamVR failing to detect the headset display in that desktop environment. This is the same error that was occurring in #572. It is unaffected by the Steam client version (beta vs. This was not occurring with 2.0.1 and does not occur while opted out of the SteamVR beta. Now relaunch SteamVR (put any apps in admin compatibility mode if needed), notice there is no error, run the compositor and BAM - get ready to setup your room (or standing area) in SteamVR.SteamVR is reporting error 303 (Shared IPC Compositor Init Failed) on launch in a Plasma Wayland session.

You may need to check the specific application settings as well and be sure it's selected to pull from 'Global Settings' or has 'High-performance Nvidia processor' selected. I haven't seen anyone else post this solution so I hope it helps someone else out one day.Īs the title states, the dreaded Compositor Failed to Launch 400 Error had effected my Alienware 13r3 laptop when trying to launch SteamVR (on my Rift and Vive) regardless if I was running the HMD off my Anker Type-C USB 4-port 3.0 hub (yes, my Rift works over a unpowered hub with two sensors connected to it because its a 60w Type-C port - this is awesome and no one is talking about this while people still buy those clunky outlet powered hubs) or my Alienware GPU amp.įinally, found out that if you go into your Nvidia Control Panel (Right click desktop > Nvidia Control Panel > Manage 3D settings) and under Global Settings make sure the 'Preferred graphics processor' drop-down menu has 'High-performance NVidia processor' selected. I am posting a solution that had stumped me majorly for an hour yesterday until I had fixed it.

Steam vr compositor 400