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?Meta SDK Mixed Reality - shaky scene
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?
Meta building blocks should not override settings
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, you just want to move the grabbed object in a way, but scripts don t work, new ways appear, like grab free transformer, which doesn t cover all the use cases. The structure of the camera rig is way too complicated, so many hand objects like hand anchors, hand visuals and other objects for interactions, left and right. Also, Oculus hands are still by default activated in editor, openxr hands are deactivated. Over time, things should become easier to use, not harder. Thank you.
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.
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.Game-Design for post-stroke patients, need help hacking the interactions SDK
Hi everyone, I'm currently working on a Unity game designed for post stroke patients with hemiplegia undergoing motor rehabilitation. I want to use Hand Tracking to make the players grab different objects. Problem is : the impaired hand often has very reduced finger mobility, so grabbing motion is out of the question. So I would like to know how to : 1- Trigger fake hand motions to simulate grabbing on one hand with a simple event (also ignore actual hand motion except for position) 2- Even better : simulating a grab from a different object that i could control independently for animations etc... (Also i need this because eventually the game will have to work with a motorized rehabilitation glove that will be tracked via Passthrough because default hand tracking doesn't track him at all) I'm currently using the basic interaction building block and sample scenes prefabs for the objects (Chess piece prefab : Touch Hand Interactable + Grabbable components) If you have any leads on how to approach this problem, I'll be very grateful ! Joseph, student gamedev
