Meta Quest Unity Real Hands Building Block not showing real hands
Hi all! I'm somewhat new to VR development, especially in mixed reality. I am trying to use Meta's Real Hand building block, but I can't seem to get it to work. I have a very basic scene with some of the fundamental building blocks (camera rig, passthrough, passthrough camera access, interaction rig), along with the real hands building block and a single cube. When I build the project to my Quest (Meta Quest 3), and move my hands in front of the cube, I can only see the virtual hands - the occlusion does not work to show my real hands (i.e. it works the same as it did before I added the Real Hands building block). Why is this and how can I fix it? Unity Version: 6000.3.4f1 Meta Quest Packages: Meta XR Core SDK (85.0.0), Meta MR Utility Kit (85.0.0), Meta XR Interaction SDK (85.0.0) Steps to Replicate: Create a new empty scene Add the following building blocks: Camera Rig Passthrough Passthrough Camera Access Interactions Rig Real Hands Add a cube at (0, 0, 3) Build the project and deploy to the Quest Wave your hands in front of the cube - only virtual hands are visible, not real hands
Make GameObjects translucent to the Passthru?
For debugging and for a few specific bits (I want to make a Leia hologram in my scene), I'd love to have the gameobjects be translucent (alpha fine) to the passthru images. If I "just set alpha," the gameobjects are transparent to themselves... but they still block all of the passthru... So... is there a way to make a hologram in your living room that works?Is there a flag for World Locked vs Free?
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)
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.Passthrough randomly disables during runtime
UE 5.5.4. Meta XR plugin v78. I have an apk that I sideload onto several headsets. The app works fine while connected to my laptop for development. Never an issue. The packaged apk works fine on the headsets during testing. Seems solid. But then I'll launch the app and hand out 10+ headsets to the customers, and they walk around for a while, eventually some of the headsets lose passthrough. The app is still running and tracking. You can see the virtual objects, but they are on the field of black. You can't see and of the surroundings. Double-tapping the side of the headset simply pauses the app and takes me to the menu. I can't get passthrough working again once this happens. I added blueprint code that every 10 seconds checks if the passthrough object is null and, if so, initialize another passthrough, but that didn't help. I've fired up 10 headsets let them run and walked around the room holding several of them, grabbing them all over the headsets (in case the customers are pressing some button), but I can't get the passthrough to stop working. Hence why I don't have a log file to attach. I'm at a loss what could be happening and how to recreate the issue. Any help or suggestions would be appreciated.Why does an MRUK Room sometimes get loaded at an angle?
I'm working on an AR app in Unity which makes used of the global mesh of the room I'm currently in. It seems that on rare occasions the whole room gets created/loaded at an angle. Not a rotation around the up-axis, but an actual tilt. I can easily detect that this happens, but from there on out I seem to be stuck. From what I can tell there is no API to go "hey, please attempt to reload the rooms again". I guess I could reload the scene, triggering a reload of the MRUK prefab, and see if that fixes things, but that's not ideal. So I guess my question is twofold. Is this a known bug/issue? How can I, when I detect this happens, cause a specific room to get "reloaded"? Unity Version: 6000.0.56f1 Current Meta Packages: 81.0.1 (Although the behaviour dates from well before that)
Stylized passthrough: How can i retexture walls?
Meta Horizons documentation on Scenes gives this image as an example of a Basic stylized passthrough. This looks to me like a screenshot of a stylized hall way. How can such an effect be accomplished in Kotlin without using Unity or Unreal? Can this effect also be achieved on Quest 2 or only on Quest 3(s)? The article mentions that Assisted scene capture (available on Quest 3(s) only) shouldn't be used to create such an effect.
