QRCodeTrackingSupported returns false in build but works in Editor
I’m working with the Meta MRUK QR Code Detection sample. The QR code detection scene works perfectly in the Editor, but when I build the project for Quest 3, the property QRCodeTrackingSupported is not have a green tick: Due to this, the QR Code is not getting detected. This functionality works perfectly fine in the Editor and is detecting the QR codes properly as well. Here’s my setup: Unity 6000.1.4f1 OpenXR 1.15.0 Meta XR SDK v79 Meta Horizon OS v 79 (Quest 3) Has anyone seen QRCodeTrackingSupported return false only in build? Any guidance on the correct setup or SDK version needed for QR code detection on Quest 3 would be really appreciated. Thanks!
Link does not have passthrough enabled?!?
Hi guys, I'm getting this error... "Link installed on the machine does not have passthrough enabled which is used in the project. Please enable it in Settings > Beta > Passthrough over Meta Quest Link." It's happening because this code in OVRProjectSetupDeviceTasks is failing... private static bool IsPassthroughEnabledOnLink() { return GetLinkWindowsRegistryValue("PassthroughOverLink"); } I'm a little embarrassed to say this, but... I don't have a Beta section in my Settings. Where do I find look for this? -Chilton
HorizonOS v81 update broke Passthrough in startup Splash Screens
Hi folks, This is for a project in a C++ UE 5.5.3-0+oculus-5.5.3-release-1.109.0-v77.0 engine from official Oculus Branch. A recent update to Horizon OS, likely v81, seems to have changed the way Splash screens are handled to now send the user to a black void with particles and wisps flying by. This has created a big problem for our MR application in that now NO Passthrough is visible during splash, which is causing us to fail VRC (Functional.14). This was not an issue before this OS update. These are the settings and image (PNG with transparency) we are using: Even forcing bAutoEnabled to True in DefaultEngine.ini does not help: Setting to Black also gives the same result, which is the black void with a very low resolution proxy of the PNG we have: For reference, this was the behavior before the v81 update: We also scouted other MR apps and it seems they face similar situations (?) Any help is appreciated as we'd rather not request any waivers during our QA process. Thank you! -Sebastian
ERROR_CLOUD_MESH_UPLOAD_FAILED(-400039)
Unity colocation build with MRUK, getting this error in Logcat and "host can't share the room with group xx-xx.." on immersive debugger... User ID and User profile active in dashboard, device has spatial permission enabled, project uploaded to alpha channel, my own user invited as tester, Keystore signed, tried with 4 different WIFI, no LLM has a clue... was working before upload alpha, What else should I check?
Trying to get Scene working
Hello all, I'm starting an AR Unreal 5.6.1 app with the Meta Quest 3. I'm trying to figure out how to scan my (real) environment and do raycasting against the room mesh. The Scene docs page points me over to the MRUK page. The MRUK page says to call LoadSceneFromDeviceAsync. When I do that my App crashes, and I pulled the .log file off my Android/<project> folder on my device and it had no callstack. So I started reverse engineering the setup done in the "Core" level in MRUtilityKitSample. The thing is, I can't get scene scans to work in the Sample on the Quest 3 either. On the Quest 2, it forced me to manually draw walls and furniture but then I was able to use the raycast modes, identify the main wall, etc. On the Quest 3, it takes me to the room auto-scanner but then when I return to the MRUKSample app the Room Details widget says there are 0 rooms loaded and none of the core demo modes seem to do anything. I noticed that Core.umap -> SetupRoom is using a deprecated node, LoadGlobalMeshFromDevice. So I tried replacing it with GenerateProceduralSceneMesh, but that function fails if you don't add a global anchor first. So before I continue to try to mess with this I want to ask if anyone has gone through and gotten scene capture working on v81. MetaXR plugin is v81.0 / the OculusXR.uplugin file has Version Name "1.113.0" Headset says software is up to date, is also v81.0 from Nov 20, 2025 This is what I see after I run "launch scene capture" and return.
Accessibility Feature Request: Conversation Focus Mode for Ray-Ban Meta Display Glasses
Hi everyone! I’m a Ray-Ban Meta display glasses user who is hard of hearing and wears hearing aids daily. I’d love to see a conversation focus mode added that prioritizes voices directly in front of the wearer and reduces background noise. In busy environments, this would make a big difference for hearing-aid users and others who rely on clearer speech in real time. If this type of accessibility feature is ever developed, I would absolutely love the ability to have it added to my glasses and would be happy to provide feedback or participate in any beta or user-testing opportunities. I’ve also submitted this through support channels, but wanted to share here in case the team is gathering feedback.
MRUK QR Tracking suddenly not working
I am making a quest3/3s app that uses QR codes for alignment, I was able to get the system working but suddenly this week I am now getting an 'MRUK Shared: queryCompleteEvent->result returned error code: -2', and QR tracking has stopped completely. The headset has stopped asking for me to confirm the environment setup before launching. I was able to confirm its broken on an old push and fresh project. I have spent most of a day trying to troubleshoot, but my best guess is something on the headset changed, and I have done all the troubleshooting steps on the headset and unity project as possible. Any ideas here would be extremely helpful. Ideally all i need is tracking, in fact, id love to remove the scene setup step, since the app is boundaryless and only uses the scene for QR code tracking support MRUK/Meta XR core/Meta Interaction/SDK Essentials all V85.0.0 Quest3 OS V2.1
Space sharing with EnableWorldLock = true drifts the controller pose
I am using the meta MRUK sdk to share the scene space between an host and a gust user with the EnableWorldLock = true. After the scene is shared, the guest's right/left controller pose is slightly misaligned. I tried to convert from local space to unity or room space but it did not work to realign the pose. Did anyone have the same issue? Thanks for any help
