Broken WebXR in latest Chrome update?

@mrdoob : last time after updating SteamVR, had to enable Flags to make WEBXR work.
now after updating to google Chrome Version 83.0.4103.97 The following happened:
inside chrome://flags → instead of many options (see old flags attached) there are only 2 XR flags left (see new flags attached)

I am set up with latest steam VR with HTC vive.
cannot get ENTER VR to show up in three.js examples

Also filed a bug report with Chromium 1092252 - chromium - An open-source project to help move the web forward. - Monorail
as instructed by @Mugen87 on my last post about web XR
which was solved.

this is a huge issue right now and super weird… I am having someone try on “non updated” Oculus quest browser and they are able to enter VR in our app.

but i am afraid latest chrome build has broken three.js WebXR ? :man_shrugging:

Thank you for taking a good look at this.

I don’t think this is true. Your filed bug is actually a duplicate of:

which is still open.

1 Like

I meant “solved” my initial post enabling flags to enable not a bug report. I had not filed one.
But thanks will take a look when back.

Thanks again on this. Definitely same issue.
Hoping It did not break latest Quest browser as well :roll_eyes:

The Quest is not going to break.
Steam + Chrome is a much more fragile combination.

1 Like

Guys we have a problem, getting some attention, but still :roll_eyes:
: 1088046 - chromium - An open-source project to help move the web forward. - Monorail

I don’t think we can do something in this forum. It’s best to continue the discussion at the Chromium bug tracker or open issues/upvote existing issues at the Oculus/Valve community requesting for OpenXR support.

Thank you! Keeping on top of it. Will post when resolved.
Thanks again for awesome moderation and guidance on best practices.
I am still a bit new at the whole thing :sweat_smile:

1 Like

Good news!

This will add a layer of robustness. As long as Valve talks to the OpenXR layer correctly, they will be able to change things and Chrome won’t break.


Good news :tada:!

Almost there @mrdoob ?

@Jay_E @mrdoob WebXR finally landed in steamvr beta and the examples are working again :smiley:


Yay!! Going to QA and test! :crossed_fingers:

Wow. Cannot believe this has been 23 days since the last post.

So it seems there is still an issue. I am currently on windows 10, Using Steam Vr 1.12.5 , HTC VIVE

tried forceruntime as default as well as OpenXR while toggling webXRincubation flag enabled/default.
I was able to replicate our app issue inside three.js

@mrdoob: are we missing an update on the library side? I hope the attached screenshot and Console Log help.

We would love to enable the to be experience with headsets as well :sweat_smile:

Maybe try Chrome Canary.
The current version 86 seams to work better with SteamVR.
Even without setting any flags.

1 Like

Try it with the latest Steam VR Beta.

1 Like

I have the same problem, I have the beta version of steam vr, I have a htc VIVE and I also noticed this error of screen freezing when entering vr mode, I am using mozilla as a browser for webxr, until a few weeks ago I could see the stereo view in my browser on my pc monitor, but then it only freezes, although I can enter vr with VIVE I cannot get feedback from the pc browser, I came to think that it was the use of THREEJS because until the mozilla page hello -webxr ( I file this freeze bug and it’s written in threejs, then look at the official webxr examples ( -samples /) and it turned out that the viewer example did not work for me either (, I have looked and searched for others like: https: // toji / webxr-particles / but no response, to what I assumed was openxr

I don’t think Firefox supports WebXR yet. Try Chrome or Edge.

Although in firefox if webxr recognizes me and I can enter the vr through VIVE, in the browser the stereo image is frozen until leaving the vr


Any fixes that work?
I’m still having issues using a Rift-S through SteamVR beta on Chrome (All the recommended flags set).
It also doesn’t work in Chrome Canary out of the box for me :confused:

Without OpenXR set as the default (also happens on Edge), i can get the enter vr button to show up in the samples, but after clicking it I get this error for both the inline and immersive samples:

XRSession creation failed: The specified session configuration is not supported.