Quest Browser location bug preventing IWSDK testing
I tried to start an Immersive Web project following the guide. But I got stuck at the step where you put on your headset and point your Quest browser to the IP address of your project in order to actually enter VR. As you can see in this photo, there is a strange error "Browser needs access to your location to share your location with this site" The CONTINUE button does nothing when I press it. I tried granting location access several different ways, none of which work. Obviously my location should not matter, and should certainly not be preventing me from developing an app. Somebody needs to fix this.
Browser WebXR apps not recognizing correct size of space
Hey! I've been trying and testing some WebXR apps for the past few days and they have been working fine with my space setup (the scan of my room). But since this morning, it's pretty messed up. The scale of the WebXR environment is not working properly in the different apps I've been trying (my own and others). It seems like it is doing a weird scaling of everything (the UI 3D panels, the objects, the planes and surfaces, etc). I thought it could be the browser and WebXR itself, but the quest device feels weird as a whole. The main menu in passthrough mode tracks a bit of my head movement, which was not happening previously. Also, I cannot focus very well on passthrough mode and looking to my surrounding makes me feel dizzy. There seems to be an offset between the real world and representations in MR (you can see that happening with my hands in the second video). This was not happening yesterday and the days before. Here is a recording of what's happening both in the browser and in the normal menu and passthrough interaction. https://horizon.meta.com/shares/Y5SSCJhQQbs1PwveM5rrfkIQVKXgfg https://horizon.meta.com/shares/iTQZ6bNkM5zH3hdRjK3KWwJFbL0WfJ I tried factory resetting and it didn't help. Rescanning of the space, didn't help.
webXR on Meta Quest scan QR code?
Meta Quest with webXR and passthrough I have a webXR project with passthrough and this is working perfect on the Meta Quest 3s with the meta browser! Scan a QR code? But now I want to scan a QR code (printed on paper, laying on the table in the real world) in order to place digital content on top of this QR code. My browser is on the latest version 40.2. I was reading that webXR did not yet have access to the camera API. Is there some progress on this? When can we have access to the camera? Other solution for QR scanning? Or is there an other solution? I do not need the full camera access but only detect the QR code? We made QR scanning with meta quest working in Unity while access to the camera API is available in Unity. But as said we are really looking in this simple QR scanning solution for webXR? As addition to this. We work with three.js. I really hope that QR scanning will be available. This could make AR tours with QR scanning much more easy. And this scanning of a QR should only be done for example 2 times a second. Just to place the content on top of a QR in near-real-time. I really hope to hearOculus 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 OS
