WebXR games in browser not working?

[TTV.ohcEcho]

Hey everyone. I am trying to play some WebXR games online.
I have tried Chrome and Edge with a bunch of WebXR game samples I found.

Every time I click the "Enter VR" button, in what ever form it might be, SteamVR starts up and I see "Google Chrome 98" or "Microsoft Edge 98" inside my index.
However its just stuck there saying "Waiting" forever.

Am I missing something here.
Does steamvr not work with WebXR games? This behavior makes me think it should work. Am I experiencing some sort of bug?

[JustVoody]

s

[76561199310734977]

yes, l have the same question with you.

[[乱死]Savior_zyy]

same question

[wender]

if only this got fixed

[grzegorz77]

Originally posted by wender:

if only this got fixed

The problem is probably with your computer. So you can fix it on your own.
It's a hardware / driver issue. Buy a professional graphics card. For rendering, compute, server. The so-called Quadro in the jargon. But it could be a radeon, of course. I suggest e.g. nvidia a100. Cards of this type can easily cope with multi-threaded 3D rendering work. What cards for home use often can't do.

[_oBSOLEte_]

Only current browser were webxr was working for me on Windows is Chrome Canary. https://www.google.com/chrome/canary/

[grzegorz77]

Originally posted by _oBSOLEte_:

Only current browser were webxr was working for me on Windows is Chrome Canary. https://www.google.com/chrome/canary/

https://en.wikipedia.org/wiki/WebXR
=

Support
WebXR Device API[22] (Candidate Recommendation Draft) is currently supported in the stable versions of Edge and Chrome 79+, Chrome for Android 79+, Opera 66+, Opera Mobile 64+, Samsung Internet 12+, and Oculus Browser.[23][24] WebXR is supported in Safari for visionOS on the Apple Vision Pro mixed reality headset.[25]

edit:
(Maybe there's no need to use the unstable branch)

[_oBSOLEte_]

Originally posted by grzegorz77:

Originally posted by _oBSOLEte_:

Only current browser were webxr was working for me on Windows is Chrome Canary. https://www.google.com/chrome/canary/

https://en.wikipedia.org/wiki/WebXR
=

Support
WebXR Device API[22] (Candidate Recommendation Draft) is currently supported in the stable versions of Edge and Chrome 79+, Chrome for Android 79+, Opera 66+, Opera Mobile 64+, Samsung Internet 12+, and Oculus Browser.[23][24] WebXR is supported in Safari for visionOS on the Apple Vision Pro mixed reality headset.[25]

Copypaste all you want. Chrome current version's webXR not working for the Rift here on Win10. And for OP as well, with the index, or so it seems.

[grzegorz77]

Originally posted by _oBSOLEte_:

Originally posted by grzegorz77:

...

Copypaste all you want. Chrome current version's webXR not working for the Rift here on Win10. And for OP as well, with the index, or so it seems.

I'm not saying you're wrong, chrome is a very unstable software.
But I see other browsers there as well, so I'm assuming that the support is broader than just the unstable chrome branch.

I also admit that I was a bit mean before. I was blown away by the quality of the responses on this topic, and I wrote back maliciously, but if I could turn back the clock I wouldn't join this discussion.

[Rectus]

Valve recently released a patch for this, but testing with the current SteamVR version, it seems to be broken with both Chrome and Edge again.

[nathan]

I was able to launch a WebXR app using both SteamVR 2.4.4 and Beta 2.5.2.

• Chrome Version 123.0.6312.123
  
• Oculus Quest 2 through wired Oculus Link
  
• Windows version 22631.3447
  
• Test WebXR app: https://immersive-web.github.io/webxr-samples/inline-session.html

Do you have the dashboard showing by chance? When the dashboard is up, Chrome doesn't render because it doesn't have focus (this is intentional Chrome behavior).

If this issue persists, please post more information to help us reproduce the issue.

[Rectus]

Testing with:

• Chrome Version 123.0.6312.123, with the --disable-features=XRSandbox switch
  
• Valve Index
  
• Windows 10 19045.3758
  
• Test WebXR app: https://immersive-web.github.io/webxr-samples/inline-session.html

Testing with all API layers disabled, confirmed with other OpenXR apps that the session transitions into focused.

It stays at the splas screen idefintiely. Looking at the SteamVR logs, it outputs:

[Error] - Failed to create sync texture.  Ensure application was built using DXGI 1.1 or later (i.e. Call CreateDXGIFactory1).

Followed by a stream of these errors:

[Error] - ComposeLayerProjection: failed to submit view 0: VRCompositorError_SharedTexturesNotSupported
[Info] - CD3D11VRRenderer::Initialize(): Failed to create input layout for vertex shader shaders/d3d11/distort_vs.fxo!
[Info] - Error creating VR renderer.
[Error] - ComposeLayerProjection: failed to submit view 1: VRCompositorError_SharedTexturesNotSupported
[Info] - CD3D11VRRenderer::Initialize(): Failed to create input layout for vertex shader shaders/d3d11/distort_vs.fxo!
[Info] - Error creating VR renderer.

Full log here, copied from the web console:
https://drive.google.com/file/d/1zE9QWcSdcj-8NS56DCbeXXzjKXkE9wKC/view?usp=sharing

Curiously it seems to fail writing the xrclient_chrome log to file.

[charlesl]

I just tested here on an Index and an RTX 3080 on Windows, with Chrome 123.0.6312.107 and 124.0.6367.61, and it seems to work. For some reason I don't need the --disable-features=XRSandbox flag anymore?

The only thing that stands out to me is that I have set SteamVR to be the default XR Runtime.

What GPU/GPU are you on? And what GPU driver version are you on? I am really concerned about the error line "Failed to create input layout for vertex shader shaders/d3d11/distort_vs.fxo!"

[rusty]

I'm also having trouble running the webxr sample. Chrome 123 never gets past the splash screen.
My logs don't show as much activity as @Rectus above, it never gets that far.
It gets down to here:

...
vrserverWed Apr 17 2024 00:03:52.295 [Info] - [OpenXR] SetXrInputConfig: Loading bindings into context.
vrserverWed Apr 17 2024 00:03:52.295 [Info] - [Input] system.generated.openxr.google chrome 123.chrome.exe (knuckles) attempting to load default config from file:///C:/Program%20Files%20%28x86%29/Steam/config/openxr/system.generated.openxr.google%20chrome%20123.chrome.exe_knuckles_2_binding.json
vrserverWed Apr 17 2024 00:03:52.388 [Info] - [Workshop] Successfully loaded binding file 'C:\Program Files (x86)\Steam\config\openxr\system.generated.openxr.google chrome 123.chrome.exe_knuckles_2_binding.json' for app 'system.generated.openxr.google chrome 123.chrome.exe'.
vrserverWed Apr 17 2024 00:03:52.397 [Info] - Processing message VRMsg_Input_SetXrInputConfig from 9536: chrome took 0.108 seconds
xrclient_chromeWed Apr 17 2024 00:03:52.448 [Info] - Capturing Scene Focus

and then nothing else is logged from chrome until i kill it or exit it on the webpage.


There is also an error shown in the chrome console when the webxr session tries to start:

 
Failed to construct 'XRWebGLLayer': WebGL context must be marked as XR compatible in order to use with an immersive XRSession
    at onSessionStarted (https://immersive-web.github.io/webxr-samples/vr-barebones.html:110:48)

My system:
nvidia RTX3060ti driver 551.52
Valve index
Steamvr 2.4.4
Windows Version 10.0.19045 Build 19045
Chrome 123.0.6312.123 (Official Build) (64-bit)

[Rectus]

Originally posted by charlesl:

I just tested here on an Index and an RTX 3080 on Windows, with Chrome 123.0.6312.107 and 124.0.6367.61, and it seems to work. For some reason I don't need the --disable-features=XRSandbox flag anymore?

The only thing that stands out to me is that I have set SteamVR to be the default XR Runtime.

What GPU/GPU are you on? And what GPU driver version are you on? I am really concerned about the error line "Failed to create input layout for vertex shader shaders/d3d11/distort_vs.fxo!"

I'm on:
CPU: i7 -9700K
GPU: RTX 4070, with Nvidia driver 536.23
SteamVR Beta 2.5.2