Questions & Discussions

ماذا عن تفعيل الارباح في اليمن 

For a few days, whenever I connect link to Unity editor, when I press Play, it shows this error:Failed to initialize Insight Passthrough. Please ensure that all prerequisites for running Passthrough over Link are met: https://developer.oculus.com/documentation/unity/unity-passthrough-gs/#prerequisites-1. Passthrough will be unavailable. Error Failure_NotInitialized.UnityEngine.Debug:LogError (object)OVRManager:InitializeInsightPassthrough () (at ./Library/PackageCache/com.meta.xr.sdk.core@e6e7a2c46b82/Scripts/OVRManager.cs:3667)OVRManager:InitOVRManager () (at ./Library/PackageCache/com.meta.xr.sdk.core@e6e7a2c46b82/Scripts/OVRManager.cs:2390)OVRManager:Awake () (at ./Library/PackageCache/com.meta.xr.sdk.core@e6e7a2c46b82/Scripts/OVRManager.cs:2524) It just happened, I don't use passthrough, in OVR manager everything is disabled. If I disconnect the LINK cable, the error disappears.The problem is that whenever I press Play, Unity starts in pause mode. If it's harmless, I can disab

I am enjoying using the Meta XR building blocks to bootstrap VR projects on the quest 3.  It's pretty easy to get things up in running.   However I hit a total wall with trying to interact with any world space UI designed with the UI toolkit (not the more common ui canvas or the old school immediate mode gui).Do any of you know of any tutorials or strategies on getting it to work with a project set up with Meta XR system? A little more background:I've found one example project of interacting with the UI toolkit in VR but that is not compatible with the Meta XR tools.  ("package manager->XR Interaction toolkit->World Space UI") so it doesn't work.I know UI Toolkit isn't very popular but i think it's literally the answer to everything wrong with UI Canvas and IMGUI because of the possibilities unlocked when you use it as a target for react  UI design.

Hey i am from India can anyone tell how to go inside meta horizon centre world. Also not able to live events in tv app. It shows not applicable in your country 

I am running into an issue with trying to edit some worlds I am working on in VR. I get an error message and I am being sent back to my island home saying unable to travel to this world. I can access and edit the world on Desktop Editor but I can not get into the world in edit mode on VR. Wondering if anyone else is having this issue and if there are any solutions to fix or prevent this issue. Thanks!MadamMischief

Hello,We are encountering a significant issue with system keyboard on Meta Quest builds using Unity 6.The ProblemForced Entry Point: Unity 6 now defaults to the GameActivity application entry point. When we attempt to use the older Activity entry point (required for the previous keyboard system), the application crashes on startup, forcing us to use GameActivity.Missing Input Box: The GameActivity entry point uses the GameActivity Jetpack library, which has removed the on-screen input box that traditionally appears above the system keyboard.For mobile apps, this is a clean design, but in Meta Quest VR, this causes a major UX problem.The UX Issue on Meta QuestSince the Quest system keyboard is visually separate and detached from the in-game UI, users lose all visual confirmation of what they are typing. The visible input box on the system keyboard is necessary in VR to show the user the text they are actively entering.The ConstraintMigrating our entire project to a custom virtual keyboa

For some reason today's analytics report for revenue is off by about 85%.For example, instead of showing $100 earned it's showing $5. Is anyone else seeing this?

Hi, This is definitely a pretty basic question relating to  the Meta Interaction SDK for Unity. I've managed to get a HandGrabUseInteractable linked to a HandGrabinteractable via a SecondaryInteractionFilter. However, I also have a DistanceHandGrabInteractable on that object, linked to its own HandGrabUseInteractable linked to the same delegate as the first. When I grab the object without distance grab, my script calls BeginUse, EndUse, and ComputeUseStrength properly. When I grab with distance, it does not, as far as I can tell - I am working on Mac and the simulator was not working with this scenario at all, so I have to port the APK to my quest each time I want to test. That takes away a bit of my debugging capabilities.I thought perhaps this was an issue with having multiple HandGrabUseInteractables, but when I removed the duplicate and made the object only have DistanceHandGrabInteractable and one HandGrabUseInteractable, it still did not work. I also wondered if perhaps

I am building a hand-control-based VR app for users with impaired mobility.  I have two challenges related to the pinch-and-hold gesture for recentering.For some users the gesture is exceedingly hard or impossible to perform (false negative).For others, the gesture is sometimes triggered accidentally (false positive).I understand Meta's desire to keep this gesture universal across all third-party apps.  Unfortunately, it is not universally viable to all users.  I need a solution to this problem or my app will never ship.I am prepared to roll my own recentering system that manipulates the in-game view in response to a hardware "easy button" press.  However, to implement this solution I still need to know when an actual pinch-and-hold gesture is performed, so that I can properly recalibrate my own system.  Unfortunately I have not found any functioning API or telemetry that might hint that this has happened.  I have tried several OpenXR and Meta Core APIs bu

We are a non-profit organization for a 50+ community.  Our volunteers are requesting specific clothing so they can be identified as hosts and/or trainers at events.  I am an MHCP member and the President of the organization. Is it possible for me to create a members only world and only add those specific folks to that world and then create a quest so that when they enter the world they do 1 task such as just enter the world and they "win" their designated shirt?  They saw this happen recently in another world so are requesting IF I can make this possible for them. These would be logo'd shirts specific to our 500+ member community.  And most importantly only to a small number of our volunteer folks. They will not be sold in any clothing shop or in a public world. 

Hello,we are currently depveloping an AR app that relies on spatial anchors. We intend to deploy it via MHMS in the future.For the development we are using Unity and are currently testing the deployment. We tried it a few months ago and there were some crucial errors regarding spatial anchors. The problem is, when the app is deployed via MHMS the spatial anchor feature doesn't seem to work. Coming back to it now, the errors still persist.When saving a spatial anchor, the system always returns a platform error and the anchor cannot be loaded or saved.This ONLY occurs when deploying over MHMS. Deploying from Unity directly or sideloading the app always works perfectly fine. It also is not Unity or OpenXR version dependent as there have been multiple updates of both since we tried it first. When the headset is managed via MHMS, no option works.Is there any way to handle this problem or any fix for this in sight?Thanks!  

Hey all,Working with Meta support, but it's taking a bit of time to get back to us. Meanwhile, I was curious if anybody else might have run into this issue. We've been approved on our Coming Soon page, but we're unable to launch it. You can see specifically what I mean here:Notice that "Publish coming soon" is greyed out, and it's asking us to email mailto:submissions@oculus.com. We've of course emailed this as well, but haven't heard response in weeks. Meta Support has been checking into this, but the hope here is that somebody else may have had the same issue and reasoning. Really appreciate it :)Once we do get this solved, however it's done, I'll respond here in case somebody else finds themselves with the same issue.~Justin

Hello, I'm a VR game developer on the MetaQuest Store and I have a European bank account in euros. Currently, Meta's payments to developers are in dollars and are automatically triggered once the amount reaches $100. The problem is that for dollar payments, European banks take a hefty commission (between €15 and €30 minimum per transfer). We lose a lot of money this way. Would it be possible to implement euro payments or at least allow us to choose the minimum payment amount? (to reduce the bank commission) Thank you

I'm trying to register for a Meta for Developers account to build an app, but I'm stuck at the verification step. On my first attempt, I was able to get past the SMS verification, but then I received an error message saying my device wasn't recognized. Since that happened, I haven't been able to complete registration at all because now I no longer receive the SMS verification code.I've tried multiple times over several days, waited well beyond the 30-second delivery window, and confirmed my phone can receive texts from other services. My number is a regular carrier number, not VoIP, and isn't linked to any other Meta developer account. It seems like something on Meta's end may have flagged my number or account after that initial "device not recognized" error. Has anyone else run into this issue or found a workaround? I've also submitted a support request through Facebook but haven't heard back yet. Any help would be appreciated.

I want to know if there is any way to install a custom network certificate on a quest headset. Please help me try to see if there is a way. If not is there a way to view HTTPS requests for a headset.

Hello,I am trying to update my apps from Meta Spatial SDK from v0.9.2 to v0.10.0 and when deploying and running it on the Quest 3 headset, the application will crash and exit as soon as VrActivity runs onCreate. I am observing the following error on logcat:Abort message: 'JNI DETECTED ERROR IN APPLICATION: JNI NewGlobalRef called with pending exception java.lang.ClassNotFoundException: Didn't find class "com.facebook.soloader.MergedSoMapping$Invoke_JNI_OnLoad" on path: DexPathList[[zip file "/data/app/REDACTED_MY_APP/base.apk"],nativeLibraryDirectories=[/data/app/REDACTED_MY_APP/lib/arm64, /data/app/REDACTED_MY_APP/base.apk!/lib/arm64-v8a, /apex/com.meta.xr/priv-app/VrDriver/VrDriver.apk!/lib/arm64-v8a, /system/lib64, /system_ext/lib64]]The changes I did are minimal (version update on libs.versions.toml and XML component definitions and removing deprecated APIs). I tested also compiling several of the updated examples from the Meta-Spatial-SDK-Samples (such as  MrukSampl

I'm working on a project with Meta SDK and mixed reality in Unity  I'm trying to find a way to stabilize the scene, when I shake my head or move side side, it seems to reload often or shake back-and-forth. How do I fix this? I was told to use MRUK.  Is it already installed in the package of the complete SDK?  

I am trying to become a dev, and keep receiving this error message, "Sorry, a temporary error has occurred. Please try again in a little while." I have all my info connected to my account already and this issue persist multiple days in a row. I can't report a bug unless I'm a developer please help I need an access token and I've just been struggling. I've literally never had an issue getting a key when it comes to anywhere else...I have:* Confirmed phone number is fully verified in Accounts Center / Meta Pay.* Confirmed credit card is linked in Meta Pay.* Tried clearing cache/cookies and different browsers. 

Hello, We are a game development team with titles currently live on Meta Quest. In previous firmware updates, we’ve experienced unexpected regressions that affected gameplay and required urgent hotfixes after release. To reduce risk on our production builds, we’d like to proactively test upcoming firmware versions. Is there any official way for developers to get early or beta access to new Quest 3 firmware before it rolls out publicly? We are mainly looking for a beta or preview firmware channel, a developer opt-in program, or any documentation or best practices to anticipate breaking changes. Having early access would help us validate compatibility, identify blockers, and protect the user experience before updates reach the wider audience.

Hello everyone,I am writing because I am experiencing a persistent issue with my Facebook Page monetization. My W-8 tax form has been stuck in the Pending status since April 4th, 2024.Despite having completed all the required steps and submitted the documentation correctly, the status has never updated. This is causing a significant financial loss as my payouts have been frozen for several months.I have contacted standard Support multiple times, but I only receive automated responses that do not resolve the technical deadlock.Details of the issue: Issue: W-8 Form stuck in Pending.Date of last update: April 4, 2024.Impact: All monetization payouts are currently suspended.Could a moderator or someone from the Meta team please look into this or escalate my case to the internal financial department? I need a manual review of my tax documentation to unlock my account.Thank you for your help.

I develop AR applications designed to run on both the Quest3 as well as Android/iOS devices in Unity.  It would appear as though a couple of the aar/so files in the meta voice SDK and Haptics SDK are not 16kb aligned and cause issues when trying to deploy to the google play store (using the all-in-one package updated to latest at the time of this post, v81).  Since both targets (Quest3 and Android) share build settings, it complicates deploying an APK that has these meta libraries in it.The files with issues are:mailto:com.meta.xr.sdk.voice@1613052ece81\Lib\Telemetry\Plugins\SDKTelemetry.aarmailto:com.meta.xr.sdk.voice@1613052ece81\Lib\Wit.ai\Lib\third-party\UnityOpus\Plugins\UnityOpus\Plugins\Androidunityopus.aarmailto:com.meta.xr.sdk.haptics@cd1f215a823c\Plugins\libs\Android\ARM64\libhaptics_sdk.so I did notice in the changelogs for v81 that several libraries were updated for 16kb alignment, it seems as though a few may have been missed.  One big thing to note is

https://drive.google.com/file/d/1E7m4Eh7-UDsS7_y8cipJ4Zs0d-CEUpD_/view?usp=sharing  

Quest Link has slowly eroded in quality over time (performance). Now, it's completely broken. At first, I had issues with using Link to test from the Unity Editor. In play mode, after a bit of play time, it would turn into a slideshow and/or crash. Over time, play mode would be a slideshow pretty much immediately after launching. Not even a little play/testing time.Recently, it devolved to the point where I could no longer get Link to function properly and enter play mode from Unity Editor.As of today, Quest Link will no longer work at all. Attempting to launch it, I either get a black screen and frozen head tracking or a complete slideshow and then freezing/crashing. This is independent of Unity and trying to use Link from the editor. Link simply does not work anymore.I've uninstalled and reinstalled the latest version of Quest Link. I've installed the latest version of the MQDH. I'm using Unity 6.3 for development.Please advise; I can no longer use Quest Link for developmen

I have the MRUK world locking seemingly everything by default...But not quite.  Evidently Zombies aren't world locked and nether is my DebugMenu...But my "Main Menu" is world-locked and I'd like it to reposition itself in front of me.How can you tell MRUK "free this" and how do I know what is "in front of me, near eye level" so when I spawn an orb... it's "findable?"  (Hunting the real world for virtual items is... odd)

I m using for years Meta sdk, lately wth openxr backend in Unity.There are some main issues which I found after doing dozens of VR projects with hand tracking and other feature.I don t know how other people are using building blocks, but BUILDING BLOCKS SHOULD NOT OVERRIDE SETTINGS, at all. I spend weeks on a project, with hands, features like poke etc, then I just want to drag a building block for the audio for example, and suddenly, things are changed in the ovr camera rig and things suddenly don t work. If for example I have in my hierarchy locomotor deactivated, it should not activate it automatically. And also other settings.If it s a building block designed to do a thing, should only do that thing.Also, after all these years with hand tracking and grabbing, it cannot still be so rudimentary to have so many components for one thing: grabbing an object. It shouldn t need grabbable, hand grab interactable, grab interactable to just grab an object. Then, from one update to another, y