TrackedDeviceRaycaster Does Not Work with WebVR
When I run my WebVR app in the editor with my VR headset connected, TrackedDeviceRaycaster works and the UI responds to being pointed at by the controllers. When I run the WebVR build and switch to VR, the UI does not respond to being pointed at by the controllers. I did some digging around and this is what I am observing. When running in the editor, the eventData passed to TrackedDeviceRaycaster.Raycast has pointerType = UIPointerType.Tracked, which causes the method to call PerformRaycast. When running as a WebVR build, pointerType = MouseOrPen, which causes PerformRaycast NOT to be called. Furthermore, I believe InputSystemUIInputModule.GetPointerStateIndexFor sets the pointer type. It seems the bug is in there.
WebVR getVRDisplays() error
Hello! I have a problem with WebVR API, when I call a getVRDisplays() Oculus Browser returns error: Uncaught (in promise) DOMException Code: navigator.getVRDisplays().then(displays => { if (displays.length) { VRManager.display = displays[0]; console.log("VR api found " + VRManager.display.displayName); } }); but in Firefox Reality it works great, appearse only in Oculus Browser. Maybe someone know where is a problem may be, thanks for help!
Positional tracking in Oculus Browser WebVR worse than native
Hi there, Thanks for all the great work on the Oculus Browser! I believe I'm seeing significantly worse positional tracking in the WebVR browser compared to native apps. To reproduce: Visit http://moonrider.xyz using the Oculus Browser on Quest Click to enter VR (glasses icon in bottom right corner) Bend knees and move whole torso from left to right (i.e. left/right DoF, not yaw) Notice the edges of things like the 'Start' button and the grey star you are standing on (look down) move in a choppy way To compare: Open Beat Saber demo and start tutorial Move to the corner of the black square you are standing on (with the white edge) and look down Repeat same left/right movement Notice the white edges of the square do not move in a choppy way So it appears the WebVR browser has a lower frequency of positional tracking than the native apps. Is this something that can be fixed?
[WebVR] [Oculus Go] Headset and Controller have different display ids
Hello, we have developed a 360° showcase web app and implemented the web vr interface. We have already tested the website in Firefox with the Vive and Rift and on Android with the Google Daydream. When we tested the app with Oculus Go we noticed that the vr api works as indented but the controller was missing. I debugged the browser app and found this: The display id of the Oculus Go and the display id of the controller were different. When the controller is in the same 3d space as the vr headset the two display ids should match. This is not the case when using the Oculus Browser. So our web app ignores the controller. See also: https://developer.mozilla.org/en-US/docs/Web/API/Gamepad/displayId Here is an example: https://webvr.info/samples/XX-vr-controllers.html This app ignores the display id so the controller is visible. Open this link in the Oculus Go. Connect your Oculus Go to your computer, enable developer mode and install ADB. Open Chrome on your Desktop and enter chrome://inspect. Inspect the XX - VR Controllers tab. List all your vr displays with "navigator.getVRDisplays().then((r) => console.log(r))". List all your gamepads with "navigator.getGamepads()". You should see that the display ids differ. For now we'll ignore the display id if the display name is "Oculus Go". But is this behaviour indented or is this a bug? The ids match in the Android Chrome browser.Oculus Home overrides WebVR
I haven't been able to nail down a root cause and reliable path to reproduce but when trying to start a WebVR experience in Firefox the view in my Oculus Rift will fade to black like its going to go into the experience but then fades back to Oculus Home. This seems to happen randomly, but once its starts it wont stop until I close Firefox and Oculus Home and restart everything. This makes development and demoing really really annoying. I have seen on the slack channels that other developers are having the same issue. Can anything be done to fix this? Windows 10 with Firefox
