Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VR + WebGL2 not working on Oculus Quest 1 and 2 #4134

Closed
camelgod opened this issue Apr 9, 2021 · 5 comments · Fixed by #4206
Closed

VR + WebGL2 not working on Oculus Quest 1 and 2 #4134

camelgod opened this issue Apr 9, 2021 · 5 comments · Fixed by #4206
Labels
bug needs triage For bugs that have not yet been assigned a fix priority

Comments

@camelgod
Copy link

camelgod commented Apr 9, 2021

Description
Clicking the "Enter VR" green button on the bottom will result in a WebXR session with black screen, making the VR experience unavailable. It works when first entering the room (hubs wants to start xr session, click allow), but using the button will not work.

The Invite button inside the initial WebXR session is also completely broken and does nothing.
Clicking the Create button will show a prompt "Continue" but will break the website by going out and then back into WebXR session but this time with a black screen.

To Reproduce
Steps to reproduce the behavior:

  1. Go to hubs.mozilla.com on Oculus Browser
  2. Enter the room, exit webxr session, click "Enter VR" button
  3. See black screen

Expected behavior
Clicking "Enter VR" should start a WebXR session without pitch black darkness.

Hardware

  • Device: Oculus Quest 2
  • Browser: Oculus Browser.

Additional context
Seems to have started after the UI update.
Avatar Head rotation and movement still works fine if you look at the avatar through another browser.

Here is the log from Chrome debugging / OQBrowser:
image

Here is another log from Chrome/OQBrowser on my hubscloud
image

@camelgod camelgod added bug needs triage For bugs that have not yet been assigned a fix priority labels Apr 9, 2021
@camelgod
Copy link
Author

camelgod commented Apr 9, 2021

I was able to reproduce the same issue on hubs.mozilla.com using Firefox Reality. Seems like it is hitting the physics system?

Mozilla Nightly (81.0a1) Quest

image

After lots of workarounds and testing I got the VR loading but its all broken and I get:
WebGL warning: drawElementsInstanced: Multiview count mismatch: shader: 1, framebuffer: 2

@camelgod camelgod changed the title Enter VR button not working on Oculus Quest 1 and 2 VR not working on Oculus Quest 1 and 2 Apr 12, 2021
@bekojang
Copy link

Running into the same issue.

Screen Shot 2021-04-12 at 1 26 37 PM

@camelgod
Copy link
Author

camelgod commented Apr 14, 2021

Update: I managed to get it working seting webgl2: false in hub.html on my own HC fork.

@camelgod
Copy link
Author

camelgod commented Apr 15, 2021

So my hypothesis is that previously there was some kind of bug that made the client fall back to WebGL1. This is not the case anymore after the UI update, and it now loads WebGL2 successfully, but there is some kind of bug with Hubs + WebGL2 and Oculus Browser.

I still get the getPose error at random times:
Uncaught DOMException: Failed to execute 'getPose' on 'XRFrame': XRSpace and XRFrame sessions do not match.

@camelgod camelgod changed the title VR not working on Oculus Quest 1 and 2 VR + WebGL2 not working on Oculus Quest 1 and 2 Apr 15, 2021
@dvdsmthdvd
Copy link

dvdsmthdvd commented Apr 27, 2021

I'm still having this issue. Has anyone found a solution? Seems like an error like this that makes Oculus Browser unusable is a big one and needs fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs triage For bugs that have not yet been assigned a fix priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants