ozten Posted January 20, 2022 Posted January 20, 2022 Hello, thank you for an amazing headset. Should web VR experiences "just work" when using Chrome on Windows 10 with SteamVR and Vive Console? Everything worked for me in December and now I cannot launch any VR content. Looking into it, it seems like browsers have shifted from an earlier WebXR spec to OpenXR. I've tried a bunch of stuff, but wanted to check to see if this is even supposed to work. For details of my versions installed: https://github.com/immersive-web/webxr-samples/issues/142 Thanks for the sanity check.
HackPerception Posted January 20, 2022 Posted January 20, 2022 @ozten WebXR is in a bit of a sad place because of Google's depriortization of XR, and Firefox's layoffs. It's still progressing - it's just getting a small fraction of the resources as the game engine side of the industry. I haven't had luck with chrome and WebXR in some time outside of Oculus' fork of chromium they use in the Quest Browser. I just tested and can't get WebXR to work with any of my SteamVR headsets (including ones that don't require Vive Console) on the current Chrome - same problem as you. I'm not aware of what steps might be required to get SteamVR linked up on the current chrome build. I was able to get WebXR to work perfectly with Firefox with Vive Pro 2 via SteamVR without any fuss - it just works as you said. That's using all of the current APIs and working perfectly with SteamVR so that leads me to think it's a Chrome specific issue.
ozten Posted January 20, 2022 Author Posted January 20, 2022 @HackPerceptionthis is super helpful! At least I understand things are in transition.I will test out Chromium nightly.
HackPerception Posted January 20, 2022 Posted January 20, 2022 @ozten I saw on Linkedin this week that at least one member of the Mozilla Hubs team was rehired. Hopefully that's a good sign. I personally think the metaverse hype will be a boon for WebXR.
HackPerception Posted March 9, 2022 Posted March 9, 2022 @ozten Try installing the current chrome (chrome99) and then launching the following commmand from a run prompt: chrome.exe --disable-features=XRSandbox
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now