Questions & Discussions

Hi, we're an organization investigating whether using Meta's Colocation / Shared Spatial Anchors SDK will be feasible for large-scale VR/MR projects.I have found limited information in the documentation regarding this topic, mostly mentioning 'two or more' players are supported. We are building a prototype app that is planned to need to scale up to approximately 200 people in quite a large space.We'd like to know if there are any strict hardware limits to:A) the amount of headsets that can share spatial anchor data with one another (in our case, it's fine if one headset shares the spatial anchors and the others 'listen' to these anchors. e.g. how many concurrent users can accurately receive spatial anchors from a single headset?B) the maximum amount of physical space that the headsets' pointcloud can accurately track. e.g. an area of 200m2

Hello,We are evaluating the feasibility of using Meta's Colocation / Shared Spatial Anchors SDK for a large-scale VR/MR project and would appreciate some clarification regarding its scalability.While reviewing the available documentation, we found limited information about supported participant counts, with most examples referring only to "two or more" users.Our current prototype is intended to scale to approximately 200 concurrent users operating within a relatively large shared physical environment. To assess whether Shared Spatial Anchors are suitable for this use case, we would like to better understand any practical or hard limitations of the system.Specifically, we are interested in the following:A. Concurrent headset support* Are there any documented or recommended limits on the number of headsets that can share the same spatial anchor data?* In our scenario, a single headset (or a small number of headsets) could act as the source of the spatial anchors, while all other headsets

I’m trying to register as a developer to create an app. At the verification step I get “device you don’t usually use”. Someone please help!

Hello,I am a graduate student currently planning a research study that combines EEG recording with virtual reality, and I am considering using either the Meta Quest 3 or 3S headset. Because EEG analyses require precise synchronization between stimulus presentation and neural recordings, I am trying to better understand the timing characteristics of these devices.I was wondering whether there is a delay between:A visual stimulus being rendered or presented by a program running on a computer, andThe stimulus actually appearing on the display inside the Quest headset.If such a delay exists, I would greatly appreciate any information regarding:The typical end-to-end display latency (measurable delay) for Quest 3/3S.Whether the latency differs between wired and wireless PC connections.The expected variability (jitter) in presentation timing.Any technical documentation, specifications, or user experiences related to display latency and timing accuracy that may be useful for research applicat

Hi there,I'm testing a build of my Unity project on the Quest 3 (installed through the MQDH), and after a few minutes, the HMD just went dark (while the headset is on my head and with me actively testing my app) with what I believe is the "sleep mode" sound effect (the "shooooo" sound like you are moving away). If I press the Meta button on my right controller, the screen lights back up, and I can resume.I tested running the Horizon World to rule out the proximity sensor's problem, and I stayed in a world for 30 minutes without the screen going dark.I believe it might be some specific settings in my Unity project. Is it possible to log what's making my HMD go to sleep (that's what I'm assuming when the screen goes dark) and monitor it through ADB?

I'm building a multiplayer app in Unreal Engine targeting Meta Quest 3 and utilizing shared spatial anchors. I'm trying to request shared spatial anchors by calling GetSharedAnchorsAsync(). I provide a GroupUUID and the anchors UUIDs that I previously saved in the cloud and shared via ShareAnchorsAsync().However I'm getting the error: RequestSharedAnchors: Failed with result code 11.The error code is tied to the error: Failure_ErrorLimitReached.  Here is my setup: -The Quest is logged into the same developer account, which owns the organization which owns the app- The headset is in developer mode- Enhanced Spatial Services are enabled- anchor_persistence_cloud_anchor_service_enabled: true confirmed in logcat- Data Use Checkup (DUC) completed – User ID and User Profile access approved- The organization is verified- Build uploaded to a release channel- The release channel has a test user assigned – the same admin developer account, also used for organization verificat

Hey buddy, I encountered the following error when using Meta XR SDK v78 in Unity and don't know how to fix it. I also encountered this issue with v77: the project was running normally just a moment ago, but after restarting the project, this error pops up. I can fix it by deleting the Library folder in the project directory, but I want to know if there are any other simpler solutions. Does anyone know how to do this?ArgumentException: An item with the same key has already been added. Key: Assembly-CSharp System.Collections.Generic.Dictionary`2[TKey,TValue].TryInsert (TKey key, TValue value, System.Collections.Generic.InsertionBehavior behavior) (at <356d430fdcb04bbf8dc54776e1d3627f>:0) System.Collections.Generic.Dictionary`2[TKey,TValue].Add (TKey key, TValue value) (at <356d430fdcb04bbf8dc54776e1d3627f>:0) Meta.Conduit.Editor.AssemblyWalker..ctor (System.Collections.Generic.IList`1[T] assemblies, System.Collections.Generic.IEnumerable`1[T] compilationAssemblies) (at ./Libr

I always want to search for a specific thing they talked about in a specific profile.. that’d be freakin amazing 

I dont think i am the only one but all the worlds i have created missing items, no textures, cant upload assets . Most worlds i have visited that are not mine same issue

Hello Guys,My app is a mixed reality app and in my app boundary is not required but it looks like with new OS update boundary is a required. I am using Unreal Engine 5.6(Meta fork) .Is it possible for you to provide the steps for:1) boundary permissions2) passthrough enable3) scene api permissions.4) Hand tracking Please advise. It would be nice if you can provide a sample project. I am using Meta XR v85 plugin.Best regards,Saurabh Saxena

Hey everyone, I was looking into some specifics regarding savesystems with quest and have a question, perhaps someone can clear things up for me.So I understand Meta has moved away from a cloud storage API to use Androids automatic cloud backup system. I wanted to test that out with a Unity app I made.From what can see there are mutliple steps that need to be setup for sure:- In the App created on the meta developer dashboard, cloud storage must be activated- The User (in this case myself) must have cloud backup enabled on the headset itselfThose 2 seem quite certain. Now there's one third thing that I'm trying to find out: OculusProjectConfig.asset and it's "disableBackup" flag. This will set the resulting Manifests allowBackup flag from what I gather, but not 100% sure even on thisI had written a large paragraph trying to explain what got me confused, but I'll ratehr just ask outright: Is it a necessity to also make sure that the allowBackup flag in the final AndroidManifest is set t

All about great things we are working on

Hello, were here made it perfect and great.

Hi there,I just got an email notification indicating my payout account was restricted and disabled due to "unusual activity", but I received no clarification on what this activity was, or how to resolve this issue.What's the best way to resolve this, and who should I reach out to for clarification?The corresponding "Learn More" button in the Meta Horizon portal links to an identity verification help page, but AFAICT my identity is already fully verified.In both my personal and business account overview there are no account issues flagged.I really don't know how to proceed here and appreciate support from someone at Meta on this.

After updating Meta Horizon Link to v85 on Windows, Unreal Engine 5.5 VR Preview crashes consistently when using DX12. Environment:- UE 5.5.x- DX12- Lumen + Nanite- Quest headset via Link- MetaXR plugin enabled- RTX  4090 laptop GPU Crash:Assertion failed:!EnumHasAnyFlags(TextureDesc.Flags, ETextureCreateFlags::RenderTargetable | ETextureCreateFlags::ResolveTargetable) File:D3D12Texture.cpp Line 299 Behavior:- Normal viewport works- VR Preview crashes after 1-2 seconds- Old projects that previously worked now also crash- Disabling MetaXR plugin stops the crash- Using SteamVR as OpenXR runtime works- Crash only happens when headset is connected through Meta Link runtime This started immediately after updating Meta Horizon Link to v85.

I am currently working on a VR project using Unreal Engine 5.7.4 and am running into a version mismatch error between the Meta Interaction SDK and the Meta XR Plugin.The Issue:Upon launching the editor, I receive the following warning:“Meta Interaction SDK version '1.201.0' (v201) requires MetaXR Version '1.233.0' (v201) but found '1.201.0' (v169). Mismatched versions may result in unexpected behavior.”Current Setup:Engine Version: Unreal Engine 5.7.4 (Epic Games Launcher)Meta Interaction SDK: Version 1.201.0Meta XR Plugin: Version 1.201.0 (reported as v169 by the engine/plugin)Despite both plugins showing as Version 1.201.0 in the Unreal Engine Plugins window, the Interaction SDK specifically requests Version 1.233.0 of the Meta XR plugin to maintain compatibility. Troubleshooting Steps Taken:Verified that both plugins are enabled in the Installed > Virtual Reality section.Updated DefaultBuildSettings to BuildSettingsVersion.V6 and IncludeOrderVersion to EngineIncludeOrde

HiWe have a project that needs to target Meta Quest 3 as well as Web(GL) in Unity 6.3. We are aware that the Meta SDK doesn't support the WebGL target and don't intend to use it there, but apparently some of its editor-only code generates compiler errors when the target becomes active, blocking any iteration:Library/PackageCache/com.meta.xr.sdk.core@fc2d39f84dd4/Scripts/Editor/OVRManagerEditor.cs(392,220): error CS0103: The name 'manager' does not exist in the current context Looking at this file, around line 86 it says:#if UNITY_EDITOR_WIN || UNITY_STANDALONE_WIN || UNITY_EDITOR_OSX || UNITY_STANDALONE_OSX || UNITY_ANDROID OVRManager manager = (OVRManager)target; // ...In other words, this is missing the UNITY_WEBGL compiler directive to have this compile in, or rather should probably be present on any platform to avoid errors. The other option is to move manager one line up.I'm currently investigating if there is a workaround, since the normal

instagram_basic required API call counter stuck at 0 — cannot submit App Review App ID: 1987336468887502 I have been unable to advance my App Review submission because theinstagram_basic permission shows "0 of 1 required API call(s)" despitemaking multiple successful API calls over 48+ hours. Calls made (all returned valid data):- GET /me/accounts?fields=id,name,instagram_business_account ✓- GET /{page-id}?fields=instagram_business_account ✓- GET /17841437050927736?fields=biography,id,name,profile_picture_url,username,website ✓- GET /17841437050927736/media ✓ Token verified via Token Debugger:- Type: User token- instagram_basic confirmed in scopes- App ID: 1987336468887502 Other permissions (pages_show_list: 66 calls, instagram_manage_messages:52 calls) are counting normally. Only instagram_basic is stuck at 0. Bug report channel shows "no longer available" for this product.App Review channel says it cannot look into individual cases. Has anyone resol

I'm trying to add a custom rig from blender to unity and set it up for full body tracking but when I just follow the steps from the Meta movement tutorial, my mesh keeps getting deformed like in the picture.I can't find any info on any specific settings or bone rotation or whatever that I would need to follow when doing this. Does anyone know what the issue can be? 

I'm using Unity with Meta XR Tools for Meta Quest hand tracking, and I'm trying to create a hand-tracking based UI.What I want to do:When a finger pinch is detected, I want to highlight the corresponding fingertip.I want to place a small Sphere on each fingertip and make it glow using Emission.The Sphere should follow the fingertip movement.What I'm struggling with:I don't know where the Sphere should be placed in Unity.I'm using OVRHand and OVRSkeleton, but I don't know how to correctly get the fingertip Transform.I'm not sure whether the Sphere should be placed under the HandPrefab hierarchy or attached using OVRSkeleton bones.The behavior I want:For example, when thumb and index finger pinch, the Sphere on the index fingertip glows.The Sphere should continuously follow the hand/finger movement.In a Unity + Meta XR SDK environment, what is the standard or recommended way to implement this?

Hello,I am seeing thousand of logs like this one in `Android Logcat` window in runtime:2026-05-05 12:37:37.045 28704 28939 Info InputDevice_Hand HANDTRACKING ADMIRE hand 1: hpm=1 -> shared=0 2026-05-05 12:37:37.045 28704 28939 Info [CT] HandPoseSampler: Filter reset 2026-05-05 12:38:22.126 28704 28939 Info InputDevice_Hand HANDTRACKING ADMIRE hand 1: hpm=1 -> shared=0 2026-05-05 12:38:22.126 28704 28939 Info [CT] HandPoseSampler: Filter resetThis appear when using hands and even when using controllers.`Tag Control` can exclude them but then it doesn't show other logs unless I manually add all tags in the list and then deselect these two logs.currently I am using Regex Filter to hide them.

Hardware/software:- Quest 3, Horizon OS v203 (PTC, displayed as "v2.3")- Spatial Persistence Service: Version 84, Build Apr 19 2026- Meta Quest Link PC app: v201 (MQDH reports persistent version   mismatch)- Unity 6000.3.14f1- Meta XR SDKs tried: v201.0.0 (Asset Store latest) and v85.0.0   (resolves to OVRPlugin 1.117 / SDK 1.1.53)- OpenXR Plugin 1.17.0, Meta Quest Support enabled (Android tab)- Settings > Apps > Spatial data: ONSymptom:Every MRUK scene query in a standalone APK build returns:  E/Unity: MRUK Shared: queryCompleteEvent->result returned error     code: -2  E/OVRPlugin: [XREVENT][XR_ERROR_RUNTIME_FAILURE]     XR_TYPE_EVENT_DATA_SPACE_DISCOVERY_COMPLETE_METASave operations also fail with XR_ERROR_RUNTIME_FAILURE on XR_TYPE_EVENT_DATA_SPACE_SAVE_COMPLETE_FB.

After registering for NGL with my Instagram account, I suddenly got a verification prompt from Instagram asking for an SMS code. The weird part is that this appeared while I was already logged in — I wasn’t trying to log in, it just popped up as a security check.I entered my phone number, but I haven’t received anything for 4 days now — no SMS, no WhatsApp code.What I’ve tried so far:- Requested the code multiple times (with waiting in between)- Restarted my phone- Reinstalled the Instagram app- Waited over 50 hours since the last request- Tried logging in from a browser (same issue, asks for SMS code immediately)Additional info:- I have a Hungarian phone number (Yettel)- The shortcode is NOT blocked on my device- I have Authenticator (2FA) set up- I have NOT tried another phone number- My account is around 8–9 years oldAt this point I’m completely stuck because I can’t receive the code at all.Has anyone experienced this? Is there any workaround or way to regain access?Any help would b

I have a few apps I'd been working on which are on my developer account which are all based off of the same project - due to this I've managed to use the same app key across a few projects (silly, I know).Would this potentially be causing a problem I have with achievements / leaderboards?  One of the apps works fine, however another app doesn't seem to register any achievements or leaderboards. If so, is it easy to change the app key over?  Unfortunately the one I'm having issues with is the one that I'm actually looking to release! For reference I'm using a slightly modified 4.27 Oculus UE Build.

Hello Team, We were previously using this WhatsApp number (91 9445599821) with Interakt (WhatsApp API provider).Interakt has confirmed that the number has been released/deactivated from their system. However, we are still unable to activate the number on normal WhatsApp.Current issue:OTP is not receivedUnable to register the numberWhatsApp activation failsWe already tried:Uninstalling and reinstalling WhatsAppRestarting the phoneTrying SMS OTP and Call OTPKindly check and completely release/reset this number from the WhatsApp Business API (WABA) system.WhatsApp Number: +91 9445599821Please help us resolve this issue at the earliest.