Closed michela closed 1 year ago
Note about the 'Devices' listed at the bottom of the issue:
When using Quest (1 or 2), it is recommended to avoid using SteamVR in favor of simply connecting via the Oculus (Meta?) Desktop app, then using the desktop browser. Meta has its own set of initialization that SteamVR seems to interfere with sometimes.
Thanks and noted! In the interest of focus,can descope Meta hardware / software from this ticket. The intent was to flag that PC VR options on non-Meta platforms seem broken
relates to https://github.com/mozilla/hubs/issues/5377 I was able to connect with windows chrome with the following steps via virtual desktop:
Open steamVR -->
Navigate to room in chrome -->
enter on device -->
enter in VR -->
recenter in steamVR
https://user-images.githubusercontent.com/4493657/195650979-c474a6a0-c925-44ba-91c8-878f7bb46a99.mp4
SteamVR build 964 5429 Current OpenXR Runtime: SteamVR Valve Index HMD SteamVR2 lighthouses Chrome for Windows 106.0.5249.119 (Official Build) (64-bit) (cohort: 106_stable_119) Microsoft Edge 106.0.1370.42 (Official build) (64-bit) Firefox for Windows 105.0.3 (64-bit) dom.vr.webxr.enabled flag true
From Virtual Desktop
Start Virtual Desktop build 9570767 Open Hubs URL in CHrome Enter from Device Virtual Desktop closes Browser opens - on Steam home space popup "<browser 160> waiting. Next" remains onscreen, can hear room entry audio in HMD but room never opens
From desktop
Open Hubs URL in browser Enter from Device Room opens on desktop and is functional HMD remains in home space
Tried:
Other test
https://immersive-web.github.io/webxr-samples
VR support detected
https://immersive-web.github.io/webxr-samples/immersive-vr-session.html
Enter VR
"<browser 106> Waiting" again
Maybe WebXR issue in general?? Not Hubs issue?
Not suggested you should try with virtual desktop, the implication is you should be able to replicate with steamVR
this worked for me: http://a-way-to-go.com/webvr/index.html
Then: connect Virtual Desktop Start SteamVR start Chrome Canary Launch your mozilla hub. Eg: https://metafashion.rocks/EwbqXCV/?vr=1
Description No current desktop Windows browser appears to support the "Connect VR Headset" flow with SteamVR .
As described here. For context, have been semi-regularly using this flow with Steam semi-regularly since early 2020.
To Reproduce Steps to reproduce the behavior:
- Run Steam VR and test connected device working
- Go to any room on hubs.mozilla.com (also tested with our Hubs Cloud instance.
- "Enter Room"
- On any browser tried, "Connect VR Headset" either does not appear as option OR view never appears on HMD without any error notification
Expected behavior
VR mode for Hubs
Screenshots
Hardware
- Device: Desktop PC running Steam VR set - using Valve Index, Laption running Steam VR using Quest 2, Vive Focus 3
- OS: Windows
- Browser: Firefox, Chrome, Edge
Additional context Add any other context about the problem here.
You need to set your computers openxr runtime that it is using to SteamVR... it currently is most likely set to oculus.. steamvr will not respond, period if oculus is used for openxr runtime. You can change this in thbe oculus pc app settings under the "general" tab
Closing this issue for now as I believe @wazzu232's advice is correct.
Description No current desktop Windows browser appears to support the "Connect VR Headset" flow with SteamVR .
As described here. For context, have been semi-regularly using this flow with Steam semi-regularly since early 2020.
https://hubs.mozilla.com/docs/hubs-create-join-rooms.html#:~:text=If%20you%20opened%20the%20URL,link%20and%20enter%20the%20code.
To Reproduce Steps to reproduce the behavior:
Expected behavior
VR mode for Hubs
Screenshots
Hardware
Additional context Add any other context about the problem here.