Open NathanaelA opened 1 year ago
XRLayers are not supported by Gecko. Hopefully we could support them with the future chromium backend
@svillar - Thanks for confirming my tests... Is there a estimated time line for the Chromium backend, because yes, Chromium does support it [The Oculus browser is Chromium based]....
@svillar - Thanks for confirming my tests... Is there a estimated time line for the Chromium backend, because yes, Chromium does support it [The Oculus browser is Chromium based]....
At some point during Q4 I think
Is your feature request related to a problem? Please describe. The wolvic browser is missing some of the functionality of the WebXR spec, in this case: https://developer.mozilla.org/en-US/docs/Web/API/XRWebGLBinding shows that Firefox does not yet support this ability. Since Wolvic uses GeckoView, I assume Wolvic then has the same lack of good WebXR support as Firefox does. i.e. that the "Layers" functionality is not available.
Trying to use it reports this:
Web Content: [JavaScript Error: "NotSupportedError: A required feature for the XRSession is not available."]
Describe the solution you'd like I need access to the XRControllers as a Gamepad, taking full control of them, eliminating the default "mouse" emulation behavior they default to.
The primary issue is that what I am doing is I have a 2D canvas that is refreshed every frame [see site like at bottom]. The current solution that I use on the default Oculus browser to try and eliminate as much CPU/GPU drain is to:
immersive-vr
mode, this gives me gamepad access I need.Describe alternatives you've considered There is no good alternative, because an
immersive-vr
session is currently the only way to get access to the gamepad data on the XR controllers which I need, and QuadLayer is the only way to be CPU/GPU friendly and look reasonably nice.Additional context This is the solution that I created, which works on the Oculus Browser, because of needing the XRController gamepad issue. This is for my site https://vr.gamers.center -- I decided to test the Wolvic browser because it is used by several other VR devices to see if I could make it compatible and at this point I don't have a good solution to supporting my site on anything but the Oculus browser due to this missing WebXR support.