Oculus Browser - set start page?
I have a fleet of headsets through Oculus for Business. We deploy Oculus Browser on it for our WebXR project. Is it possible to change the start page in the browser, so that our site comes up automatically? If so, is it possible to do through Workplace? Currently, we set a bookmark to the site when we provision the headsets, but this has to be done manually on each headset, and the users have to remember to look in the bookmark list.
Is WebXR dom-overlay support hidden behind a feature flag?
Hi, I'm trying to use the WebXR `dom-overlay` feature. I've tried some online demos and turning on these Chrome flags: "WebXR Experiments" "Experimental Platform features" But no joy. Is this simply not supported? Is there any plan to support it? Thanks Wayne
window.requestAnimationFrame not working in newest 33.3 Meta browser in WebXR mode
I used window.requestAnimationFrame inside a WebXR app, which previously work fine in the Meta Browser, but it seems automatically update to 33.3 on June 3rd, and now this function only works when I press the Meta button to pop up the browser but not work at all when I hide the browser and enter the XR mode. Any helps? Maybe I need to change the function? But I don't see an alternative to count frames accurately. Basically I want to have a timeManager that supervise the timing of different assets in the app.
Feature 'light-estimation' is not permitted by permissions policy
I'm making a test page to see what features devices use. I'm getting this permissions policy errors for 'light-estimation' and 'secondary-views'. Is there something I need to enable to make these work? The permission policy error even comes up in the three js light-estimation example feature: https://threejs.org/examples/#webxr_ar_lighting I'm using a meta quest 3 with version v68 OSMeta Quest Browser & BabylonJS = Slow FPS
I'm trying learn about WebXR and I'm finding that my library of choice isn't playing well in the Meta Browswer, locking at about 30 FPS. Now, I see 60 FPS on the desktop with Chrome and I know that's because Chrome is locked in a vsync. I can pass Chrome some parameters to unlock the FPS limiting. At that point, I'm seeing around 500 fps. Chrome works great with Link, but I'm looking to work with the native Meta Browser inside the Quest. I've found other engines, such as the Wonderland Engine, demonstrates 72 FPS in the Quest with their app Escape Artists (https://esc.art). A-Frame applications show up in the browser at 90 FPS. So my question is, is there some sort of parameter or command the WebGL lib should be passing to the browser to speed it up? Or, is this likely to be some sort of bug in BabylonJS that is locking it to 30 FPS and the browser doesn't have any sort of artificial rate limiting?
Quest 3 Controllers not registering with A-Frame in WebXR
This feels like a question that must have an obvious answer, as I have found no one else who seems to have this problem, but as I was attempting to work on an A-Frame project I was really confused why I couldn't get my controllers to give me movement in Immersive. After beating my head against the wall for a while I decided to go look at working examples and see what I was doing wrong. In every A-Frame project I went to, the controllers did not work. Even in Stemkoski's Quest Controller Data example. There was nothing. I tried my Quest 2. Works just fine. I factory reset my Quest 3. Nothing. I tried non-A-Frame WebXR experiences - they all worked fine. For some reason when I take my Quest 3 into Immersive on an A-Frame project it just doesn't seem to register the controllers. I feel like there must be a setting or other strange condition I'm missing, but I'm at a loss. Any ideas?
Meta Quest Browser Bug - 3D Scene Jitter - Developer - THREE.js
We are reporting a bug and seeking help. It is most likely a bug of Meta Quest Browser or related infrastructures. we are developers making 3D VR browser based Apps. We open our 3D Scenes (rendered by THREE.js) in Meta Quest Brower. The issue is, we notice that the scene would jitter even for the simplest example link from THREE.js official website. To reproduce, just open the following link in Meta Quest Browser and use controllers to drag the scene to rotate. https://threejs.org/examples/#webgl_animation_keyframes Jitter will likely to show up (not every time but pretty frequent). We believe this is more likely to be a bug of quest/browser other than the web page because the web page is simple and good in every other desktop/mobile browsers. One hint is, the jitter seem only happen (or much more frequent) when Passthrough mode is turned off. If you can not reproduce please refer to this video - it's captured by phone directly into the quest lens.: https://www.youtube.com/watch?v=hEha6OoYvyA This issue currently impacts our app badly - if anyone knows anything please let us know. Appreciate so much!!
