Questions & Discussions

Hi I am trying to make a VR app in Unity (6.3.9f1 + meta sdk version 203) for Meta Quest devices and wanted to test it in the simulator (latest) since Unity's play mode doesn't support interactions. I checked the console logs of the simulators and I can see these errors:```[arvr.simulation.openxr.vulkan_helpers]: Failed to allocate memory: -13[arvr.simulation.openxr.compositor_readback]: Error creating swapchain image```I also reported a bug from the simulator but not sure where to track the bug report. Anybody else having a similar issue?

I'm developing a VR game in a Unity project created through Meta Quest Developer Hub (MQDH).When using Meta Horizon Link for play testing, a vignette effect seems to be applied automatically, even though vignette is disabled in my application settings.Is there any way to completely disable the vignette while testing with Meta Horizon Link? Unity Version:  6000.2.8f1Meta XR SDK Version:  201.0.0Meta Horizon Link Version:  85.0.0.306.552Device:  Quest 3, Quest 2

When using the OVR Metrics tool on Quest 3 the levels show as 7 and 8 for any app, neither of them exists. When using the Meta Quest Developer Hub, the levels always show as -1.... Has anyone else encountered this?

Recieved an update on horizon editor, then was unable to open the app. I tried restarting my desktop computer as well as re-installing the software, still keep getting this fatal error code: il2cpp _ reported on horizon several times via the headset, no answer - HELP! 

Hi everyone,I am currently developing a Proof of Concept (PoC) in Unity for Meta Quest 3 where I need to use both hands and both controllers simultaneously and completely independently.I have successfully configured the project to render both the hands and the controllers at the same time, correctly positioned in space. However, I am running into a specific visual/tracking issue:When I move my physical hand away from a controller, the virtual controller momentarily tries to follow/snap to the hand's position before lagging behind and eventually snapping back to its actual, real-world physical position.My Question: Is this intended multimodal fusion behavior (algorithmic blending) or a known tracking bug?My Goal: I need the tracking positions of the hands and the controllers to be completely independent of each other at all times, without this "rubber-banding" or tethering effect when they separate.Environment Setup:SDK Version: Unity Meta All-In-One SDK 203.0.0Engine: UnityFeature Enab

I've seen the MRUK toolkit, and it looks like a decent bit of kit... but...How do I get Q3+Unity to give me a ray... on my controller... to activate stock UGUI elements?Eg, I bought https://assetstore.unity.com/packages/tools/gui/evo-ui-modern-ui-framework-310303And can see it... but... I can't interact with it on a Q3 app.  This ought to be simple, but... it's just not clicking with me...  does anyone have an example of using rays to interact with plain-jane UGUIs (not bigredbuttons) or a tutorial on what I need to do to these widgets to make them ray-interactable?  The canvas already had a Graphic Raycaster on it... but...?

Hello,I'm working on a project (PCVR) that continually reads coordinates from Quest Pro controllers (integrated cameras), all works fine in my side.My issue is that the controller automatically turns off (auto-sleep) after few minute if no movements detected, so, reading the controller's coordinates breaks.How to disable controller's auto-sleep?Thank you.

Hi everyone,I am trying to build a Unity application for research that plays haptic feedback through HapticSource.Play(). Despite haptic files being longer than 15 seconds, the controllers keeps going to sleep when not physically moved every 10-15 seconds, and disabling the haptic feedback too as a result.I have seen other posts marked as resolved by Meta, mentioning that this is a battery-saving feature, this feature is definitely a constraint for me instead... Please let me know if anyone has found a way to disable this. I'd greatly appreciate any help.Thank you very much!Tim

Meta XR Standalone Simulator V83.2 crash immediately on running the game in unityI am using Unity 6.3 LTS , Meta All-In-One SDK v83, using URP and Ghraphics API D3D11full log from simulator app:[com.meta.xrsim.grpcconnectionfeeder]: Handling connection request with URI: [ :: 1]:56959 [com.meta.xrsim.openxrplatform]: Starting logging for device: [: :1]:56959 [com.meta.xrsim. openxrplatform]: Successfully started logging for device: [ :: 1]:56959 [meta.xrsim. logger_factory]: Started message streaming for device: [ :: 1]:56959 [arvr. simulation.xrsim]: XrSynch received changed state no session, asked to terminate: yes [com.meta.xrsim.openxrplatform]: Device 12281027643599708862 notified about disconnected state. (XrInstance destroyed) Scheduled terminaiton. [arvr. simulation.xrsim]: XrSynch received changed state no session, asked to terminate: yes [com.meta.xrsim.openxrplatform]: Device 12281027643599708862 notified about disconnected state. (XrInstance destroyed) Scheduled termina

I cannot submit my app for App Review. App ID: 1544866123670159 (Acelera Comentários).Clicking "Submit for review" returns: "the following question labels are not valid: fblogin-web-1".All visible App Review sections are complete and green. I'm requesting advanced access forinstagram_manage_messages and instagram_basic, plus public_profile renewal for Facebook Loginfor Business. OAuth redirect URI (https://comentarios.aceleraatacado.com/) is configured and validated.A DevTools query confirms there is NO element with this label anywhere in the page DOM(document.querySelectorAll returns an empty NodeList), so it is a backend/draft schema ghost,not a missing visible field. The Bug Report tool also fails with "An error occurred while creating the bug report".Please reset the submission draft schema for App ID 1544866123670159 so I can submit. Thank you. 

Hi everyone,I hope you are well. Although the Developer Dashboard shows that both my individual developer account and my developer organization are Verified, the Developer Mode switch is not visible in either the Meta Quest mobile app (Android) or in Settings ▶ System ▶ Developer on my Quest 3 headset. Also I do not share the account I am the primary account holder I Have Already Created a new developer organization in the dashboard and uploaded the required documents.The dashboard now shows:Account Verification:  VerifiedOrganization Verification:  Verified Enabled two-factor authentication (TOTP + backup SMS).Updated the Meta Quest mobile app to the latest version.Confirmed that Bluetooth and Location Services are ON and that the headset appears as Connected in the mobile app’s Devices tab. EnvironmentHeadset: Quest 3Android SymptomsMobile app: No “Developer Mode” option appears under Devices ▶ [My Quest 3] ▶ Headset Se

Meta App Review final submission for our app is blocked by a hidden/internal validation label. All visible App Review sections are complete/green, but final Submit returns: Some sections are incompletequestion labels are invalid: fblogin-web-1 App: Hermes BotApp ID: 2389952421516474Business ID: 1114463873276065Submission ID: 2407995389712177 Expected behavior:- The submission should submit successfully because every visible required section is complete, or- The UI should render the missing question/field that maps to fblogin-web-1 so it can be completed. Actual behavior:- The final submit confirmation modal accepts the acknowledgement checkbox.- After clicking the modal Submit button, the page returns the fblogin-web-1 validation error.- No visible App Review section, Website platform testing instructions, Facebook Login for Business settings field, Facebook Login for Business configuration field, or Instagram setup field is visibly marked incomplete. Troublesh

ive had a facebook and tried in many different avenues to logging into meta developer but i keep getting this error message  You can't make this change at the momentThis is because we noticed you are using a device you don't usually use and we need to keep your account safe. I need help for my account to get cleared.

I'm building a minimal Quest 3 mixed-reality app (passthrough with a transparent background) using the Meta XR All-in-One SDK with OVRCameraRig and OVRPassthroughLayer, on a Mac (Apple Silicon). I can't get a working Android build on any Unity version I try:On Unity 6000.4.11f1 (tested with All-in-One SDK 203.0.0 and 201.0.0), the Gradle build fails with: Namespace 'com.oculus.Integration' is used in multiple modules and/or libraries: :InteractionSdk:, :SDKTelemetry:, :OVRPlugin:. The conflict is inside the compiled .aar files, so I can't fix it from my own manifest.On Unity 6000.5.0f1 (6.5) with All-in-One SDK 203.0.0, compilation fails before building with CS0619 errors inside the SDK's own scripts: 'Object.GetInstanceID() is obsolete, use GetEntityId' (com.meta.xr.sdk.interaction PoseDetection scripts) and 'EntityId implicit operator int is obsolete' (com.meta.xr.sdk.core MCPBridge/Tools/Reflection.cs). This looks like Unity 6.5's EntityId breaking change isn't yet supported by the

I updated the Quest Link software this morning and since then handtracking in the Unity Editor doesn't work anymore. Also running the project takes a minute until it starts in the headset - before it only took 1-2 seconds.Last straw I can investigate is this version mismatch. How do I update the headset Link version? At this point I'd like to say to Meta that the developer experience is EMBARASSINGLY BAD and I recommend literally anyone who reaches out to me to not use Quest. Any help would be appreciated. 

First... not sure where these should be.  If there's a bugtracker, I'll gladly use it because I haven't found a way around this one yet (save for keeping the controllers alive).When using CameraKit to scan QR codes https://communityforums.atmeta.com/discussions/Questions_Discussions/bug-report-mruk-83-0-4---85-0-0-cameraaccess-getcamerapose-bad/1371408/It's all fine and dandy with the above patch... until you put the controllers down.Then, it seems to go off in a random, not flat direction that is not stable...Unfortunately I haven't gotten actual MR screenshots to work, but here are logs.HH = HandHeld.  This the last frame before I pick up a controller.CC = ControllerControlled.  This is the first frame after I pick up a controllerCS = CameraStable.  IIRC 10 frames later when it's nice and flat.I try to hold my head and the QR code still for these tests... you get a smidge in the UV space and a smidge in the camera pose... but the WC (world coords) are very ve

Hello,I am building a scene with a CAD car inside a wind tunnel. I would like to trigger a video showing a CFD airflow simulation when pressing a button. Is video playback supported in Horizon Desktop Editor, or is there another recommended workflow?

Hi, when I turn on Developer Settings through Meta Quest Link and try to load into a scene on Unity, my headset stays stuck on the loading screen (i.e. Unity loading on Link).When I try stop the Unity scene using the stop button (square) at the top, it hangs and I have to force quit Unity.I believe this might be because I updated Link recently? This was not an issue before I updated the app. Even when I open other Unity projects, I also get the same issue where it doesn't load on the headset and hangs when I press the stop button.I am on Meta Horizon Link version 205.0.0.103.543 and Unity version 6000.4.0f1 on a Windows 11 PC, using a Meta Quest Pro.See below for 'Developer runtime features' setting. 

Hi everyone,I am working on a VR project that requires true simultaneous and independent tracking for both hands and controllers. However, I have run into a native snapping issue that I cannot seem to bypass.Project Environment:Device is Quest 3. Running via Link in VR Preview, not deployed as APK yet. Engine version is Unreal Engine 5.7.4. Plugins enabled are Meta XR and Meta XR Interaction SDK. Native OpenXR is disabled.Current Setup and Behavior:I followed the official documentation for Multimodal input. In my VRPawn, I use ISDK_HandRigComponent and ISDK_ControllerRigComponent. On BeginPlay, I call Set Simultaneous Hands And Controllers Enabled with the true checkbox.This successfully prevents the hand tracking from completely shutting down when controllers wake up. However, a major issue occurs when they get close to each other.If I hold the right controller with my left hand, the hand tracking for both hands remains completely fine. But the moment the headset detects that my right

Hello,We are trying to migrate our games from Facebook Canvas to Instant Games, as required before the Canvas shutdown in September.For the last several months, we have been trying to publish two games through the Instant Games Quality Review process, but we have been unable to get meaningful feedback when our submissions are rejected. The review responses do not provide enough information for us to understand what needs to be fixed.The bigger issue is that the support process itself appears to be broken.1) The "Ask a Question" button available in the Instant Games Review section on https://developers.facebook.com/ also does not work. When clicked, it loads indefinitely and never allows us to submit a question to the review team.2) The support page at https://developers.facebook.com/support/ does not work for us. When we try to submit a support request related to Instant Games, the page never finishes loading and the case is never created.We have also tried other channels, including re

I lost the ability of body tracking a few hours ago,I was doing some updates in my project so I thought I might broke something inside Unitythen I tested a previous build which had a working body track but the tracking didn't work alsoIs it a bug in Meta Horizon Link?Meta Quest 3 Version 2.3.1034Meta Horizon Link Version 201.0.0.73.547 

Got a PTC update for Link today, v205.0.0.103.543. Now, Unity freezes when I try to enter Play mode in VR via Air Link. I'm on v201 of the Meta XR packages (because that's the latest version that supports Unity 2022.3). I get a bunch of warnings in the Unity console upon trying to initialize the VR session, and then it stops responding, and I have to kill the editor via the task manager to get out. I can still enter Play mode without Link running (if I just want to watch something in the editor), and I can still use VR mode with Virtual Desktop, so I'm pretty sure it's a Link issue. I could exit the PTC, but that would only be a temporary fix. Anyone else having a similar issue? I assume it might be fine with Unity 6, but I'm not keen to try updating my whole project. I guess Meta might force my hand if they're not supporting Unity 2022.3 with their SDK releases going forward. Edit: I managed to copy a few of the warnings before the editor froze: [OVRPlugin] [XRCMD][failure] [XR_ERROR_

Updating to XR Core version 203.0.0 when using Unity 6000.5.0f1 on macOS, the package has / compile errors on import, because casting an `EntityId` to `int` is obsolete. Error:com.meta.xr.sdk.core/Scripts/MCPBridge/Tools/Reflection.cs(461,28): error CS0619: 'EntityId.implicit operator int(EntityId)' is obsolete: 'EntityId will not be representable by an int in the future. This casting operator will be removed in a future version.'The internal representation of EntityId seems to be an `ulong`, so switching to that might be an option.Two further points:The MCPBridge tool seems to be entirely optional, I would appreciate it if the asmdef for it was not enabled by default, but could instead be enabled in an editor window / menu instead, for those who want it.This is the second time in a row where I'm forced to fiddle with your packages after upgrading, because you cannot seem to be testing your packages for the platforms & Unity versions you claim to be supporting. PLEASE improve your

My personal Facebook account was temporarily restricted due to a login anomaly on June 15 and successfully restored on June 16. However, my Meta for Developers access is still blocked with the error "You cannot access this service." Furthermore, when I click "Submit a support request," the page goes completely blank (white screen). Since my personal account is fully active now, this seems to be a sync issue or frontend bug. Please help refresh my developer status.

## Issue summaryOn Quest 2 (Horizon OS, build `UP1A.231005.007.A1`, Android 14), native app crashes are not surfaced correctly through the `ApplicationExitInfo` API. A full tombstone is written to disk by `debuggerd`, but the framework fails to associate it with the process exit, so `ApplicationExitInfo` reports the wrong reason and no trace. This breaks any crash-reporting SDK that relies on `ApplicationExitInfo.REASON_CRASH_NATIVE` + `getTraceInputStream()` (e.g. the Sentry Android SDK, and AOSP's own documented native-crash flow).## Observed behavior`debuggerd` handles the crash and writes a valid tombstone to `/data/tombstones/`:```F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 26718 (GameThread), pid 26590F DEBUG : Diagnostic-Collection-Type: Tombstone ProtoF DEBUG : pid: 26590, tid: 26718, name: GameThread >>> [redacted package name] <````NativeTombstoneManager` then rejects the tombstone because of non-standard filenames:```W NativeTo