Questions & Discussions

"This page isn't available at the moment.This may be because of a technical error that we're working to fix. Please try reloading this page."this is the error message that occurs while editing date of birth. please suggest a solution for this. 

Hi,I’m working with Unity + Meta XR SDK and using Meta Quest 3 via Meta Link (PC VR / OpenXR runtime).I would like to retrieve the battery percentage of the headset and controllers while running in PC VR mode (Link/Air Link).What I’ve tried:- SystemInfo.batteryLevel returns PC/laptop battery, not headset- OVRPlugin.batteryLevel marked as obsolete, and returns 0 when running via Link- OVRManager.batteryLevel same behavior as OVRPluginHowever, the Meta Quest Link desktop and mobile app itself are able to display headset and controller battery information, so the data clearly exists in the system.Is there any supported way in Meta XR SDK / OpenXR / Oculus PC SDK to access:- Headset battery percentage- Controller battery level…while running in PC VR mode (Link/Air Link)? Or is this data intentionally not exposed to third-party applications on the SDK side? Any clarification from Meta or experienced XR developers will be appreciated.Thanks!

Is it possible to toggle the panel's Stereo Mode during execution?I am running an Activity panel, which may sometimes display stereo content.

SERIOUSLY META UNTIL WHEN? Today it's my turn, quest 3 unused after update, HELPLet's go straight, I've already done everything conventional, the failure was after the update (one forcibly remarked) - the viewfinder restarts and remains in the logo, the startup music plays, even the cell phone detects the viewer, it doesn't go beyond that point.I already restarted several times.I already tried the factory reset, a useless reset since I overcame it - THANK YOU META, why do you have a factory reset if you don't respect it??.I already tried updating with official tools and ADB.I need someone to give me a full ota to reinstall the operating system And unfortunately since I live in Uruguay I do not have technical support and for tax reasons the repair would be like buy one new.help¡

In the documentation regarding building a shader binary cache per-platform (link) the documentation states:Using this feature, once one user starts the app and manually builds the SBC, all other users with the same device and software (Horizon OS, graphics driver, and app) will be able to avoid the shader generation process by downloading a copy of a pre-computed SBC.However, later on the same page, it states there is an automation in place to launch the apps and perform scripted prewarming logic if requested.The system automatically identifies and processes Oculus OS builds and app versions that require shader cache assets. It generates and uploads these assets to the store backend and automatically installs them during an app install or update.Does this feature support both of those setups? If I am not scripting any custom warmup logic, will shader binary caches still be shared between users with identical setups?IE, if I simply play the release candidate on the target OS version/har

Hello everyone,I’m experiencing a serious issue with a brand new Meta Quest 3 and I’m hoping someone here can help.The headset is brand new, straight out of the box. During the very first startup, it begins the mandatory system update, but gets stuck in an endless loop:“Applying update” → reboot → “Applying update” → reboot.I have already tried:- Factory reset (multiple times)- Power cycling- Different Wi-Fi networksNothing helps. The device never finishes the update and never reaches the normal system UI.I can enter the recovery menu and the base build/version shown there is:49660200226600510The web-based Meta update tool does not work and reports that the device is “not supported”.My questions:1. Is this a known issue with early Quest 3 firmware?2. Is it possible to manually flash the headset using ADB sideload?3. Does anyone have access to, or know how to obtain, the official FULL OTA update ZIP for Meta Quest 3?4. Has anyone successfully recovered a Quest 3 from this “Applying upda

We are building a custom engine on top of Android (using the SDK and Gradle, not Unity or Unreal) porting our products and targeting Meta Quest devices (Quest 3 specifically) for the 2D System panels / overlays (the floating windows in the Quest home environment):What we want:We need to capture *any form of controller input* (buttons, joystick, scroll) while the apps system UI panels are visible or focused. Key constraints:We are not trying to modify system UI, only observe or intercept inputEven partial input (e.g. scroll events, pointer movement, or indirect signals) would be sufficientWhat we’ve tried:Standard Android input APIs (onKeyDown, onGenericMotionEvent)Checking for MotionEvent sources from controllersPolling input devices directlyCombed through the SDK without luckIs there any supported way (SDK, API, or lower-level approach) to access or intercept controller input when system UI overlays are active on Meta Quest?Any guidance on how input routing works between apps and

Before the last Ray-Ban Display update, I was able to see the other person's video feed directly on the glasses during a video call, and I could also share my own camera. Now that the transcription feature has been introduced, the video feed no longer appears during calls. This really changes the experience — it's just not as impressive or immersive anymore. Has anyone else noticed this? Is there a way to get the video back while keeping the transcription, or is this a known limitation of the new update?

I've been developing a VR game for Quest Pro/Quest 3 for the past year using Unity 6 (6000.0.40f1) with Meta XR SDK (Core 74.0.1, All-in-One 74.0.2, Interaction SDK 74.0.2, Essentials 74.0.1).Current situation:Standalone Quest APK builds work functionallyPerformance is poor (~40-50 FPS, pixelated visuals)Unity Editor with Quest Link runs beautifully (80+ FPS, crisp visuals)What I need to know: Can I build a Windows platform executable with Meta XR SDK and run it as a PC VR app via Quest Link? Or is Meta XR SDK strictly for standalone Quest Android builds?What I've done:Optimizing the standalone build with my own code logic and texture compression, and logging disabled (My game has a server logging feature)Limited improvement due to an asset-heavy projectWhy I'm asking: Since Quest Link (Editor to Quest) performs so well, I'm wondering if I can build a Windows .exe that runs the same way - using my PC's GPU while the Quest acts as a display/input device.Constraints:I need Meta XR SDK sp

I am seeking urgent assistance from the developer community to identify the origin of a targeted exploit involving an unauthorized internal developer environment.The Issue:Forensic logs (December 2025) confirm my account is being accessed via a MessengerLiteForiOS framework—a project publicly discontinued years ago. This session is running on iOS 26.1 with Build String FBAV/537.1.0.47.110.The Evidence of Targeting:The sessions originated as early as February 2025, listing iOS 26.0 as the operating system. Since Apple did not release iOS 26 to the public until September 2025, this confirms the account was accessed through a future-dated, internal developer sandbox months before the software existed for consumers.Technical Markers:Egress Device ID: 0D01F55A-0303-4EB9-A533-85FA26A10850User Agent: LightSpeed [FBAN/MessengerLiteForiOS;FBAV/537.1.0.47.110;FBBV/846660078;FBDV/iPhone14,7]Forensic Hash: My local app containers (SHA-256: 1eec2c2032...) have been modified to include the Loom v3 t

Meta please make it happen!  Not being able to use WebGPU in WebXR is a big bottleneck for Gaussian Splatting on Quest.

Hi everyone,I’m currently planning the roadmap for my upcoming title, targeting a Q1 2027 release. I’m looking to start building my community and capturing wishlists now to ensure a strong launch, but I’ve just discovered the 180 day restriction for "Coming Soon" listings on the Horizon Store.Steam's philosophy is to get your store page up as early as possible, sometimes years in advance, to get as many wish lists as possible. This allows indie devs to funnel all social media and press traffic to a single source from day one.With the current Meta policy, I have to wait until late 2026 to even have a presence on the Store. Any hype generated now has nowhere to go on the platform, forcing me to use third-party tools (Discord/Email) which have much higher friction for users than a simple "Wishlist" button on their headset.My questions for the community and Meta team:Is the 180 days just a suggestion and really I could submit a page now?If not, what is the internal reasoning for this limit

Hi all!I'm somewhat new to VR development, especially in mixed reality. I am trying to use Meta's Real Hand building block, but I can't seem to get it to work. I have a very basic scene with some of the fundamental building blocks (camera rig, passthrough, passthrough camera access, interaction rig), along with the real hands building block and a single cube. When I build the project to my Quest (Meta Quest 3), and move my hands in front of the cube, I can only see the virtual hands - the occlusion does not work to show my real hands (i.e. it works the same as it did before I added the Real Hands building block). Why is this and how can I fix it?Unity Version: 6000.3.4f1Meta Quest Packages: Meta XR Core SDK (85.0.0), Meta MR Utility Kit (85.0.0), Meta XR Interaction SDK (85.0.0)Steps to Replicate:Create a new empty sceneAdd the following building blocks:Camera RigPassthroughPassthrough Camera AccessInteractions RigReal HandsAdd a cube at (0, 0, 3)Build the project and deploy to the Que

I am trying to create a Mixed Reality application in Unity where a virtual environment surrounds the user’s real room, so that the user feels like they are in a different environment while still being inside their real space.I experimented with the SpaceMap sample from the MR Utility Kit:https://github.com/oculus-samples/Unity-MRUtilityKitSample/tree/main/Assets/MRUKSamples/SpaceMapThis sample actually does almost exactly what I want.However, I am facing the following issue:Real-world objects, people, and even my own body appear behind the virtual environment objects, so they become invisible. In other words, the virtual environment fully occludes the real world.What I would like to achieve instead is:Real-world objects, people, and my body should appear in front of the virtual environment based on depth.However, the room surfaces (walls, ceiling, and floor) should not occlude the virtual environment.So effectively:Real dynamic objects should appear in front of the virtual world.Static

I have a minimally reproductible project but it cannot be uploaded here.Unity 6000.3.9 and Quest3 v2.1.1034, SDK v84We have a scene 0 that loads scene 1 in which the CameraRig lives.With that setup, after launching the APK I place some anchors, then holding the Meta button (Recenter) the anchors move away. After that first recenter everything works normally and any new anchor does stay in place.This doesn't not happen if scene 0 is not included and thus we launch directly to the CameraRig scene.Workarounds:- Removing scene 0 (but that's our bootstrapper we can't remove it, but this fix might work for you)- Adding a CameraRig (OVRManager) on scene 0 (so far it seems to work)If any developer from Meta is available, i do have a project that can reproduce he bug.Thanks in advance.

Hi Meta team and community,I’m Ron — a coach and on-ice referee with 15 years of experience in ice hockey. The game is incredibly fast-paced with action happening all around the rink, making split-second calls extremely tough even for seasoned officials.My Idea: use Ray-Ban Meta smart glasses (with the powerful camera and Meta AI) as a hands-free assistant for referees. The glasses could provide subtle audio alerts or light AR visual cues for:Offsides & icing detectionToo many men on the iceHand passes & high sticksMinor penalties (tripping, cross-checking, etc.)Goal confirmation + automatic scorer/assist identificationThis would keep refs’ eyes on the play at all times — no more looking away or missing peripheral action.Why this mattersDramatically improves accuracy, consistency, and safety in one of the fastest sports on earth.Reduces controversial calls and game-stopping reviews.Starts as a training/review tool (POV recordings + AI analysis) and evolves to live assistance.Th

Hi, I have a question regarding channel invitation limits.From what I understand:Each app can configure up to 5 channels for URL-based invites.Each channel can contain up to 200 users.If that’s correct, does that mean the maximum number of users we can invite to private channels is 1000 users total (5 × 200)?We’re planning to run tests before launch and may need to invite more than 1000 users.Is there any way to:Increase this limit?Add more channels?Invite more users before launch?Any clarification would be greatly appreciated.Thank you!

Just wondering if anyone else experienced this. Happens to coincide with the announcement of Framesync, so wondered if they might be related.     <meta-data android:name="com.oculus.enable_frame_sync" android:value="false" />Have added the above to my AndroidManifest for next update just in case. 

Hello, I am stuck in a verification loop when trying to create a new app for the WhatsApp Business API. My Goal: To create a "Business" type app to integrate with the WhatsApp Business Platform. The Problem: Every time I click "Create App" on the developers.facebook.com dashboard, I am redirected to the "Verify Your Account" page (see attached screenshot), even though my account is already fully verified. What I have already done: My account has 2-Factor Authentication (2FA) enabled.My phone number is fully verified in the main Meta Accounts Center.I have tried this in multiple browsers (Chrome, Firefox) and in InPrivate/Incognito mode.The verification for my credit card also fails.I was able to successfully create a developer organization ("Umiya Agro Digital") through the Meta Quest developer dashboard (developer.oculus.com), so my account is recognized as a developer account on that new system. However, the develo

Tried searching for topics relating to this but unable to find anything.Dearly hoping that there are plans afoot for a firmware release from Meta that facilitates these great glasses with the ability to film in landscape mode. I am worried that this has been a massive oversight, a what could have been potentially the most revolutionary piece kit, might end up falling short at the last hurdle. If this is the case I might just have to offload them and switch back to my other action camera. Come on Meta, please shed some light on what may or may not be on the way... at least a little hint please.

Hello everyone,My name is Mason. I’m a graduate student at Kennesaw State University and a Research Engineer working in XR environments through my Graduate Research Assistant role.I’m currently building a research prototype that connects a mobile companion application to a VR headset so that a VR user can view media stored on their phone inside a VR environment.The system uses a Unity-based mobile application to stream video frames to a Unity-based VR application using WebRTCEnvironmentSender Device: iPhone 15OS: iOS 26.3Engine: Unity 6000.3.8f1 (Unity 6.3)Graphics API: MetalReceiver Device: Meta Quest Pro headset (Unity application)Streaming Technology: Unity WebRTC packageArchitectureMobile Unity app acts as the WebRTC senderQuest Unity app acts as the WebRTC receiverConnection established over LANUDP used for discoveryTCP used for signalingVideo Source: Unity RenderTextureGoalThe goal of the system is to allow a VR user to browse and view media stored on their phone inside a VR envi

MQDH software has been mostly smooth on my windows PC but since upgrading it to v6.3.x I am constantly facing problem with MQDH freezes when scrolling, clicks are unresponsive and switching tabs are also slow. Another problem is every time I turn on my PC, there's this window's permission pop-up asking me to grant access to Quest Link, why does it ask me every single time I turn on my PC? It's super annoying.My PC:- Windows 11- 24 GB RAM- 1 TB Free Storage- AMD Ryzen 5 3400G processor- 2GB AMD Graphics card

On Unity 6, with the V85 of Meta SDK, I choose in "Hand Tracking Support" the "Hands only" mode so controllers aren't supposed to be available in build.However, controllers are still available in my app so I tried to use the "Controller Only" mode so it disable correctly the hand tracking in my app and it shows up a window to use controllers when I try to lauch my app.Why it's not making the same for hand tracking mode ?

Hey! I just updated my Meta Quest and noticed the new navigator has a cool 3D depth effect when you hover over the apps.I want to achieve similar effect for my app. Is there any documentation to achieve this in Unity?Thank you very much.

Hi everyone,I’m currently working with the Meta Interaction SDK in Unreal Engine (UE 5.6) and using hand tracking only (no controllers). I’m using the ISDK Hand Rig Component for both hands.What I’m trying to achieve is:I want to capture the user’s real hand pose at runtime, save that pose, and then reapply (replay) that exact pose later on command.So, basically my requirement is,Is there a built-in way in Meta Interaction SDK to record and replay hand poses ?What’s the best way to temporarily override hand tracking and apply a custom pose?Any guidance, suggestions, or pointers would be really helpful.help in any way you can. Thanks.