[Solved in 1.16.10] Unable to launch any WebXR-based websites after the 1.16.8 update. Unable to read pid from pipe SteamVR_Namespace

[lauritz]

ISSUE
I'm unable to launch any WebXR-based websites after the 1.16.8 update. Following the failure to load a WebXR-site, other VR applications will also fail.

OS
Windows 10 64

HMD
The original HTC Vive

STEPS
Launch SteamVR
Open a WebXR-based website in Chrome or Edge
Optionally: Open a OpenXR project in Unity and hit Play.

RESULTS
On opening a WebXR VR page, I.e https://immersive-web.github.io/webxr-samples/immersive-vr-session.html , it either becomes unresponsive or does't detect VR capabilities.
SteamVR Web console message:
vrserver Unable to read pid from pipe SteamVR_Namespace after connecting because The pipe has been ended.
(109)
vrserver CSharedResourceNamespaceServer shutting down

Following this, WebXR pages will freeze until the browser tries to shut down the page.
Also following the pipe ended message, on activating OpenXR in unity editor:
WM_DEVICECHANGE message recieved.
DBT_DEVNODES_CHANGED: A device has been added to or removed from the system.
Then, on hitting play, freezes for a long time before starting, but without functional VR.
Attempting to launch a VR app through the steam library will also stall while trying to launch.
On restarting SteamVR again and hitting play in the Unity editor, I get the error message "CEF Local Resource Load Error: http://localhost:27062/app/image?app_key=system.generated.unity.exe&version=1.16.8 -> 404 (Not Found)", but editor playback appears to be working. I am still unable to get WebXR working.

EXPECTED
Being able to successfully launch the WebXR application. After this, other VR-applications (and Unity OpenXR projects) should also launch successfully.


Some other possible log highlights:

vrserver on launching SteamVR:
vrclient_vrstartupCSharedResourceNamespaceClient::Init(): failed connect
vrclient_vrstartupCSharedResourceNamespaceClient::Init(): still waiting for vrserver to reply with namespace data
...
vrserverCSharedResourceNamespaceClient::Init(): failed connect
vrserverCSharedResourceNamespaceClient::Init(): still waiting for vrserver to reply with namespace datadata
...
vrserverCSharedResourceNamespaceServer sent namespace data: 8336
vrclient_vrstartupCSharedResourceNamespaceClient::Init(): received namespace data 8336
vrserverCSharedResourceNamespaceServer sent namespace data: 8336
vrserverCSharedResourceNamespaceClient::Init(): received namespace data 8336
vrserverSelf queried namespace: 8336
...
vrserverOpenService failed (1060)


I've tried reinstalling everything, including a fresh Windows install and multiple reinstalls of SteamVR, in addition to updating everything I can think of. Before the SteamVR 1.16.8 update, it was working perfectly.
Hoping for a quick resolution, as I depend on WebXR for my job!

[The Iron Wolf]

I get this same problem launching any game. Get similar debug output in VS output window and VR fails to init.

System reboot helped but something seem to have regressed. And it also impacts my work, on a hobby project. Please allow rolling back.

[kuzel]

Similar Problem here, since the 1.16.8 update my index will not be detected by any browser for old webVR or new openxr sites. "NO VR found" and something like this. I can watch downloaded VR Videos with Virtual Desktop and play games in VR but no functionality in chrome, edge or ff. When i load some page ie. immerse-web, the browser crashes the tab.

[The Iron Wolf]

EDIT: apologies, I responded to this seeing similar errors, and thought I'd add info, but I probasbly should've started another thread as my problem is OpenVR one. Rolled back to 1.15.12 - that one works, so it is a regression.

I run multiple VR apps. Crew Chief is a VR overlay application, and it is running displaying overlays.

When I try to start the game I am working on I get this:
Tue Mar 02 2021 11:12:59.769 - [Settings] Load Default Json Settings from Steam\steamapps\common\SteamVR\resources\settings\default.vrsettings
Tue Mar 02 2021 11:12:59.769 - [Settings] Load Json Settings from Steam\config\steamvr.vrsettings
Tue Mar 02 2021 11:12:59.780 - Unable to open process id=14648 from pipe SteamVR_Namespace after connecting because Access is denied.
(5)
Tue Mar 02 2021 11:12:59.780 - Starting vrserver process:\Steam\steamapps\common\SteamVR\bin\win64\vrserver.exe

....
haredResourceNamespaceClient::Init(): failed connect
Tue Mar 02 2021 11:18:50.271 - CSharedResourceNamespaceClient::Init(): still waiting for vrserver to reply with namespace data
Tue Mar 02 2021 11:18:50.372 - CSharedResourceNamespaceClient::Init(): failed connect
Tue Mar 02 2021 11:18:50.374 - CSharedResourceNamespaceClient::Init(): still waiting for vrserver to reply with namespace data
Tue Mar 02 2021 11:18:50.475 - CSharedResourceNamespaceClient::Init(): timed out contacting vrserver for a namespace


If I close CC, close SVR and run the game, it launches. Something has changed with startup, I never had hangs like that before. Unpredictable delays, yes, but now runtime times out initializing with error 310.

[Rectus]

WebXR not working seems to be an issue with app containers. Launching Chrome normally I get the same issue, and it will also prevent Chrome from working without app containers until SteamVR is relaunched.

Disabling app containers for WebXR in Chrome by launching it with the
--disable-features=XRSandbox command line paramter allows it to run WebXR content.

[lauritz]

Originally posted by Rectus:

Disabling app containers for WebXR in Chrome by launching it with the
--disable-features=XRSandbox command line paramter allows it to run WebXR content.

Thank you so much for this suggestion! This was super usefull!
I still get most of the error messages I mentioned earlier, but this parameter does allows me to access WebXR content on my desktop during development again. It's unfortunate that I can't expect my target users to jump through the same hoops (which, before the 25th, were not needed).
I'll try following some of the links mentioned in https://immersiveweb.dev/chrome-support.html and do some reading up on it.

[floz]

Just to add, I am also experiencing this issue. Valve Index on Chrome using WebXR via three.js. Few months ago worked perfectly as a test I wrote. Today, I am ready to start coding for real, and now WebXR support is broken (sigh). Sadly, the --disable-features=XRSandbox workaround did not help for me at all, although if I add --force-webxr-runtime=SteamVR to the chrome command line, at least my web-page gets the VR button on screen (even if it always says VR NOT SUPPORTED). Will be keeping my eyes out for a fix... pretty pretty please with a cherry on top?

[floz]

Eternally grateful for Hotfix 1.16.10. Fixed Index WebXR on Chrome for me. Many thanks.

[Atak]

Somehow I still see this issue with my Index.
Update: It only works when using this command: chrome --force-webxr-runtime=SteamVR --disable-features=XRSandbox