Questions & Discussions

Hey everyone, We're QuantumArcadia, a small studio based in India. We recentlypublished Arcade Mania on the Quest Store — a collection ofskill-based mini-games built for VR, arcade-style. We're still learning what resonates with the Quest community, so Iwanted to share it here and get honest feedback — what works, whatdoesn't, anything that feels off in the first 5 minutes. You can check it out on the Quest Store here:https://www.meta.com/en-gb/experiences/arcade-mania/1181756821683806/ Happy to answer questions about how we built it, tech stack, orlessons learned so far. Would really appreciate any thoughts!

Hello, I am working on a vulkan app. I tried taking capture on an oculus quest pro using the latest v68.16 version. I am using raw vulkan code and I think the issue is on the libVkLayer_GLES_RenderDoc.so side. I am using vulkan memory allocator for all my allocations:tried multiple scenarios, this is one example of callstack: Essentially what happens, is either vkBindBufferMemory or vkBindBufferMemory2 is intercepted by the renderdoc validation layer. The validation layer tried to inspect my buffer pointer for replayability I suppose. It ends up calling CreateAddressRange which is a nullptr.   I think everything boils down to VK_KHR_buffer_device_address, it does not appear to be supported by either my quest pro or quest3. But even if not supported, it looks like renderdoc is using some of its feature such as vkGetBufferDeviceAddress or vkGetBufferOpaqueCaptureAddress and fails to do so. Is there any way of avoiding renderdoc to use this extension?   I ran a similar app on Qu

Hi guys, i am a student pilot and like to take pictures while in flight with my meta 2 glasses. I also like to identify towns from above but my glasses cannot accomplosh that without internet connection. I was wandering...if the GPS of my Phone is on and I have download the offline maps for Google maps, why should not be possibile.for my glasses interpolate gps/maps data to give the location and tell what i am looking?!?Any idea would be appretiated 

I’m looking for help regarding an issue with Meta XR Simulator on Windows 11.I’ve installed Meta XR Simulator (v83), but it continuously shows an error saying “Windows App Runtime 1.5 or higher is required”, even though Windows App Runtime versions 1.1 through 1.8 are already installed and working on my system. Meta XR Simulator seems unable to detect the expected 1.5 package structure or registry/runtime signals.If anyone has encountered this issue or found a workaround (other than downgrading to v82), I’d really appreciate your insights. Thanks in advance.

I’ve added the first version of the multiplayer mode.At the moment, I don’t have access to multiple Meta Quest headsets to fully test real headset-to-headset gameplay. I’ve tested the online flow using a bot, and it appears to work correctly, but I’d really appreciate feedback from users who can try it between multiple headsets.If you test multiplayer, please let me know whether matchmaking, synchronization, player movement, and race results work correctly. https://www.meta.com/es-es/experiences/ufo-snowboard/1178822797740806/?require_login=true

We isolated a reproducible browser/driver-level hang on Meta Quest Browser and want to share it with other WebXR developers (also filed via the developer Feedback Center). Symptom: entering an immersive WebXR session permanently hangs (rAF stops within ~2 seconds, no webglcontextlost event, no GPU process recovery; the headset OS stays responsive) when a WebGL2 page combines ALL THREE of:antialias: true on the WebGL2 context (MSAA)2. A per-frame shadow map pass (rendering into a depth texture every frame, e.g. three.js shadowMap)3. The Spark 3D Gaussian Splatting renderer (sparkjs.dev), which performs out-of-band GPU work between frames and fence-based async readbacks (fenceSync + getBufferSubData) for splat sortingRemoving any ONE of the three avoids the hang. Baking the shadow map once (three.js: shadowMap.autoUpdate = false) instead of rendering it every frame also avoids it - that is the workaround we shipped. Environment: Quest 3, Meta Quest Browser (latest as of July 20

Ever since I updated to v78, my devices go to sleep in 1 minute.  I'm on v79 now and this persists.  I have the "power" settings so that it is supposed to sleep in 4 hours, but they seem to have no effect.  I also have my presence sensor disabled (as well as having tape over it).This is driving me crazy because if I set my headset down, I have 60 seconds to debug before it turns off and suspends my title, then when I pick it up, I have to choose a profile again before I can continue.  Meta: how do I disable this?I used to be able to keep my devices awake and running my app for HOURS, through many iterations of debugging.  I try to drive my app through automation as much as possible, and when I am debugging multiplayer, I would be in the habit of running the app on both headsets via ADB and driving most of the interactions through APIs so I don't have to juggle headsets.  This is now impossible because in 60 seconds, the device goes to sleep.  I'm

Hi everyone, I'm working on an MR project in Unreal Engine 5.7 using Meta Quest 3 with a PCVR offline setup (Quest Link via USB). I want to place virtual objects at fixed real-world positions, so I'm trying to use MRUK's LoadSceneFromDeviceAsync() along with UMRUKAnchorActorSpawner. However, LoadSceneFromDeviceAsync() is returning false and I'm unable to load the scene.Things I have already checked:1. Requested com.oculus.permission.USE_SCENE and com.oculus.permission.USE_ANCHOR_API2. Completed Space Setup on Quest 33. Spatial anchors & scene support enabled in project settings.4. Share spatial over Link is enabled in Meta Horizon link.Has anyone successfully used MRUK Scene API with Quest Link/PCVR? Is there any additional setting required for LoadSceneFromDeviceAsync() to work?Any help would be appreciated. Thanks!

Hi, could someone at Meta look into how subscriptions are surfaced to users? I know there's a grey "Choose subscription" button, and from inside my app I can open the Meta Quest store page, but I still regularly get messages from players saying they can't find how to subscribe or don't know how to subscribe. My Meta Quest app is Slice Art Engine.

Meta Horizon denied all purchasesPending identity verification, which was submitted by me June 24 through PayPal a dollar deposit then refunded ….on July 18 I submitted my drivers license and still no resolution. I’ve contacted through chat discussion many times and have no resolution replied with the same response. Will get back to you by email . Not understanding why the situation this is taking so long. Can somebody please help that's all I want to do is subscribe to the $7.99 Meta Horizon..They have all the documentation that is needed, why is it taking so long for the specialty team to review my situation? It’s been six weeks.😖  

I recently updated my Quest 3 to version v83, and since then, the app that handles QR code recognition has stopped working correctly. I tried reinstalling the app and a few other basic troubleshooting steps, but it still fails to recognize any QR codes. Is anyone else experiencing the same issue with v83? If someone has found a solution or workaround, I would really appreciate hearing how you resolved it.

(Meta Quest Pro)Could you guys please make it optional to update controllers and not just the headset?Because I don't always have time to put them to charge and thus it's very frustrating when i finally have time to be in VR again and Quest wants to forcefully update controllers but can't because there isn't "enough charge" and then having to wait forever to get the required charge on the controllers.Wouldn't also be a problem if something in the update broke something in the firmware again causing syncing issues.

Hello, I am reporting a regression introduced by the July 8, 2026 software updateon Meta Quest 3S (OS v2.5, build 3594280027800610). Summary:A WebXR streaming web application (NVIDIA CloudXR.js web client, WebGL-based)that had worked reliably for several weeks now fails immediately whenconnecting, with the error: failed to create CloudXR session: Error: Failed to initialize WebCL render The failure occurs during the client's local render-context initialization,before any network session is attempted (confirmed: the streaming serverreceives no connection attempt). Evidence that this is a headset-side regression:- The same URLs work correctly in desktop Chrome on the same network,so the server stack is healthy.- The app worked on this same headset until the July 8 update.- Tried on the headset: private tab, full reboot, clearing browser data —same failure. Wolvic on the same headset also fails, which may point toan OS-level graphics/WebXR runtime change rather th

Hello everyone,I am trying to create an application for a museum with the purpose of giving visitors a more interactive experience. However, I have found no way to prevent users from accidentally accessing the menu through the pinch feature, and then exiting the application. Using Shared Mode has prevented this, but it restarts the application whenever the user attempts to leave, causing data such as anchor points for objects in the room to be lost.Is it possible to require a code in order to access the menu or to leave an application?Thank you for time.

Hi all,I'm running a Unity app on Quest 3 that uses Shared Spatial Anchors. This setup worked reliably for a long time, but with a newly created shared anchor and a OS update later I'm now seeing inconsistent behavior: some headsets localize the anchor correctly, while others fail to localize it at all. I tryvar loadResult = await OVRSpatialAnchor.LoadUnboundSharedAnchorsAsync(groupUuid, unboundAnchors);  and I get a -1006 as error message) Sometimes I have to wait for minutes then it suddenly works sometimes not at all.Things I've already checked:Enhanced Spatial Services is enabled on all devices (Settings > Privacy & Safety > Device Permissions)Scene permission is requested/granted in OVRManagerWi-Fi/network connectivity looks fine on all headsetsUsers walked around the room in passthrough before attempting localizationHas anyone else run into shared anchors suddenly becoming unreliable across a fleet of headsets, with no changes on the app side?Meta XR SDK versi

J’ai un problème avec mon compte meta ils me disent que j’ai 12 ans alors que j’ai eux mon casque le 14 juillet pour mes 13 ans il demande de mettre une carte d’identité je l’ai mise et sa me redemande de la mettre j’essaye et la page reste blanche ya rien ce n’est pas ma connexion parce que je suis bien connecter etc… expliquer moi pourquoi sa me fait ça parce que sinon je vais perdre mon compte merci d’avance :)

Hello,I am having a login issue with Meta Horizon Link that I have been unable to solve.When I click "Sign in" in Meta Horizon Link, the browser opens the Meta authentication page, but the login process always fails with:ERR_TOO_MANY_REDIRECTS"auth.meta.com redirected you too many times"I can log in normally to my Meta account through the browser (meta.com / auth.meta.com), so the account credentials and web login are working correctly.I have already tried:Reinstalling Meta Horizon Link.Reinstalling Windows (fresh installation).Clearing browser cookies and cache.Testing with Chrome and Microsoft Edge.Checking Meta/Oculus services.Generating logs with OculusLogGatherer.The most important test:I created a new Meta account with another email address and tested it on the same PC, with the same Meta Horizon Link installation.Results:✅ New Meta account → Works correctly.❌ My main account → Always fails with ERR_TOO_MANY_REDIRECTS.This indicates that the issue is related specifically to my Me

Hi Meta team,I'm building a WebXR mixed reality application on Quest 3 that uses computer vision to annotate real-world objects in AR — think floating info panels anchored to products on a store shelf, triggered by voice commands. The app uses Three.js + React-three/xr and connects to backend AI services for object detection and enrichment.The missing piece is camera-access. When I request it:```navigator.xr.requestSession('immersive-ar', {requiredFeatures: ['camera-access']});``` The session is rejected with:`Feature 'camera-access' is not supported for mode: immersive-ar`This is on Quest 3 running Horizon OS v85, Quest Browser latest. Why this matters for WebXR:The Passthrough Camera API is already available on native platforms (Unity, Unreal, Android) since v76. Bringing it to WebXR would unlock a category of browser-based MR apps that currently require a full native build pipeline — real-time object detection, visual search, accessibility overlays, educational AR, and mor

Unable to Receive SMS OTP for Meta Developer Verification Hello Meta Support, I am unable to complete Meta Developer verification because I never receive the SMS OTP. I have tried more than 10 different Facebook accounts, multiple phone numbers, different browsers, devices, and internet connections. The verification code never arrives. Country: Pakistan I cannot create a Meta Developer App because the verification SMS is never delivered. Please investigate this issue and let me know how I can complete the verification. Thank you.

I would like to request that Live Captions be made available in Spanish on the Meta AI glasses.I have a parent who is hard of hearing, and the Live Captions feature would make a tremendous difference in our ability to communicate. Right now, we are using the Live Translation feature as a workaround, but it isn’t designed for conversations where both people are speaking Spanish.We’ve experienced several issues with translation, including inaccuracies, delays, and  portions of the conversation being omitted. What we really need is real-time Spanish speech-to-text captions, just like the existing Live Captions feature for English.Adding Spanish Live Captions would greatly improve accessibility for millions of Spanish speakers and people with hearing loss. It would also help families like mine communicate more naturally without relying on translation.Thank you for considering this feature request. I hope it’s something the team can prioritize in a future update. 

Hello Meta Developer Community,My name is Burhan İyibicer, and I am a researcher at the Department of Restorative Dentistry, Faculty of Dentistry, KSU, Türkiye.I am currently developing a novel augmented reality-guided workflow for direct composite restorations as part of an academic research project.The objective of our study is to investigate whether Meta Quest 3 can assist clinicians by displaying a patient’s pre-treatment tooth anatomy during restorative procedures, helping them reproduce the original tooth morphology with greater accuracy.The first phase of the project will be conducted using phantom dental models as a proof-of-concept study. The anatomical accuracy of the restorations will then be evaluated using 3D deviation analysis by comparing the pre-treatment and post-restoration scans.We believe that Meta Quest 3 has significant potential for this application because of its mixed reality capabilities and developer ecosystem.We are currently looking for the most appropriate

I build high-fidelity mixed-reality installations where a Quest 3 is tethered to a workstation over Quest Link and all rendering happens on the PC (Unity HDRP, ray-traced). Tethering lets the visuals far exceed what the standalone SoC can do — which is the whole point for gallery/production work.The blocker is that every MR capability is standalone-only, so a PC-tethered app is effectively blind to the room:Passthrough Camera Access API (Android Camera2) is on-device only — "the Android Camera API is not supported over Link." So no real-world light estimation, color sampling, or CV when tethered.Passthrough compositing requires a transparent, SDR background, documented as supported only for URP and Built-In — not HDRP (HDR breaks compositing). And raw passthrough isn't exposed to PC apps over Link in the first place.Net result: a PC-rendered app cannot see the room or composite over passthrough. High-fidelity tethered MR is impossible —

AccessibilityIs there any way with Meta glasses to allow  longer  pauses during dictation without the dictation feature assuming you have stopped speaking and knocking itself off. For users with cognitive difficulties such as remembering and recalling words, the current time allowed to Pause is so Social short that the feature is rendered pretty useless for users like me. I am sure that extended pauses would be a godsend to many users.

Hello, I am reporting a regression introduced by the July 8, 2026 software updateon Meta Quest 3S (OS v2.5, build 3594280027800610). Summary:A WebXR streaming web application (NVIDIA CloudXR.js web client, WebGL-based)that had worked reliably for several weeks now fails immediately whenconnecting, with the error: failed to create CloudXR session: Error: Failed to initialize WebCL render The failure occurs during the client's local render-context initialization,before any network session is attempted (confirmed: the streaming serverreceives no connection attempt). Evidence that this is a headset-side regression:- The same URLs work correctly in desktop Chrome on the same network,so the server stack is healthy.- The app worked on this same headset until the July 8 update.- Tried on the headset: private tab, full reboot, clearing browser data —same failure. Wolvic on the same headset also fails, which may point toan OS-level graphics/WebXR runtime change rather th

My Meta Quest 3S (SN: 340YC10G8N0PVR) has suffered a total hardware failure. The device is stuck on a permanent Black Screen, and the controllers have entered an Infinite Rumble loop that does not stop.   I have already performed the 'Last Resort' Factory Reset, but the hardware remains unresponsive. The Tracking Service has failed entirely, and even the Gaze Dot has disappeared from the display. I have also attempted to boot from both Slot A and Slot B, but the 'Blind Setup' wall persists due to the physical failure of the tracking cameras.   Since a full system wipe (Factory Reset) did not resolve the issue, this is clearly a hardware-level defect. I am requesting an immediate warranty replacement to Meta so I can restore my data and return to the Metaverse.