QR code recognition is not working properly on the new version of Meta Quest.
I recently updated my Quest 3 to version v83, and since then, the app that handles QR code recognition has stopped working correctly. I tried reinstalling the app and a few other basic troubleshooting steps, but it still fails to recognize any QR codes. Is anyone else experiencing the same issue with v83? If someone has found a solution or workaround, I would really appreciate hearing how you resolved it.
OVROverlayCanvas with Passthrough Broken
I was playing around with an app I made and decided to turn it into an XR app with passthrough capabilities and ran into issues. Passthrough: this works as it should I can see the video feed. UI: I had OVROverlayCanvas enabled on the main menu. This is where things get wonky. With the OVROverlayCanvas component set to underlay as the default and no passthrough enabled everything works on the device (editor is another story as it only shows in the left eye and will not show in the right eye no matter what I try, even with a simple canvas. When I turn on passthrough the UI shows but only in my peripheral vision, but if I look directly at it I cannot see the UI anymore it just disappears. Switching to Overlay instead of Underlay it is always visible, but I cannot figure out how to get the hand ray cursor to appear over the top of the imposter UI. Does anyone know how to get either of these to work?
Getting Analog Values from Joysticks in Spatial SDK Native Android App
Hi, I am trying to create an app that can track the joystick push values as continuous values rather than discrete pushed/not pushed. I am using the Spatial SDK and it seems to only expose getters such as ButtonThumbLL which return an Int representing whether they were pressed or not. I saw a similar post about 4 months ago that was left unanswered: Interface of getting Controller joystick travel range | Meta Community Forums - 1336257. I am curious if anyone knows and idiomatic way of getting the continuous values of how far the joysticks are pushed. Thank you.
Unreal 5.6.1 Interaction Examples SDK
I'm just getting started. I'm interested in looking at the Unreal version of the Interaction Samples SDK - especially for Unreal 5.6 or 5.7. I got the plug-in(s) working for 5.6, I can't get the Samples working for 5.6. I'd greatly appreciate help from anyone who has the Samples working? Also is there a timeline for 5.7 integration? Here is what I've done: https://github.com/oculus-samples/Unreal-InteractionSDK-Sample I added the: Meta XR Plugin Meta XR Interaction SDK plugin The OcculusInteractionSamples plugin doesn't seem to want to run with UE5.6.1. I've tried a rebuild - Then, I tried Generating VS project files and recompiled. But that didn't work. Thanks for any help!Meta XR Simulator Standalone Help
I'm an educator teaching Unity & XR development using Quest 3 and Meta Building Blocks. But I have been really struggling because of the difference in learning materials online (from Unity's end, and from content creators online from even just 3 months ago, let alone 1 year). The most current / pressing issue in my class is the lack of updated documentation and examples using the new standalone version of the Meta XR Simulator. Half the documents in the official Meta XR Simulator Overview documentation are from 2024 and use the old interface (which had WAY more features and customization options). I have a bunch of students relying on mouse and keyboard controls trying to test behaviors like the locomotion building block, but they don't work. Current issues I would love suggestions or hints on how to solve (from just importing Building Blocks into a Unity Core 3D scene, nothing customized yet): I have duplicate controller models and ghosting (only in the simulator, visible when moving) I have weird graphical glitches sometimes that look like snow or fuzz (only in the Unity game view & simulator when running the simulator) I cannot get rays or aiming reticles to come from the controllers no matter where they or my mouse are pointing (but they work in the headset). Even with point and click on. Do the movement inputs (default WASD and Arrow Keys) simulate the left and right joystick? Or do they override/bypass those inputs? Some teleport control options involve aiming and pressing up on the joystick, and I'm not sure how to test that in the simulator Is there some way to add simulation input options that actually trigger the controller's inputs like the Unity package version used to? I would also appreciate any general advice or resources on new/recent best practices, customization options, and debugging tips using the building blocks and interaction SDK.
