Meta Developers

Open your project in Unity.
Under Hierarchy, select and open the OVRCameraRig in the Inspector window.
In the Inspector, under Quest Features, ensure that Body, Face, and Eye Tracking Support are set to Supported, and Hand Tracking Support is set to Controllers And Hands.
In the Inspector, ensure the Movement features you use are toggled on under Permission Requests On Startup.
Go to Edit > Project Settings > Meta XR, select the standalone icon (left icon), and Fix All if any issues. For details, see Use Project Setup Tool.

Step 2. Follow troubleshooting guidelines

If the configuration steps above don’t resolve the problem, use the following guidelines to isolate the problem further.

Note: The following cases cover use of Link for app development with Movement SDK, in addition to general Movement SDK troubleshooting. If you’re facing issues using Movement SDK over Link, ensure you have configured these settings first.

Symptom	Resolution
Body tracking works with controllers on the Meta Quest headset, but not with hands when not using Link.	Enable hand tracking permissions on your headset under Settings > Movement Tracking > Hand Tracking. In the Unity Editor, ensure Hand Tracking and Controllers are enabled in your project’s configuration. Finally, ensure that the app requests Hand Tracking Support during startup.
(Link) Body Tracking works when running an app directly on the headset as an Android build, but fails to run over Link.	Ensure that you connect with a USB cable that supports data transfer, and open Meta Quest Link app on the PC. Then, under Device Settings, go to Link Cable > Connect Your Headset > Continue. Also, ensure you have Developer Runtime Features enabled on the Meta Quest Link app on the PC by navigating to Settings > Beta > Developer Runtime Features.
Body looks collapsed on the floor.	This means that Body tracking is not working. Outside of the app context, verify that controllers are being tracked, if you are using controllers. If you are using hand tracking, verify that hands are being tracked.
Character with body tracking rigged does not move or follow neither controllers nor hands.	Enable components like OVRBody. These components must be on enabled GameObjects. If you later disable an OVRBody component, body tracking will also be disabled.
Character with body tracking rigged stays in idle animation or doesn’t move at all on a character that uses animation rigging.	Verify that you are using the animation rigging workflow rather than the basic method. If you are not using animation rigging, ensure that the Animator check box on the Animator Controller in the character is not checked or that the character does not have an Animator Controller that is also animating the body joints.
(Link) When running the app on PC, it starts on PC, but doesn’t appear on the headset.	Check that Link is enabled on the headset. Disconnect USB cable, connect it back, and enable Link again.
Tracking technologies fail to start via Link or built APKs even with tracking features enabled, and their permissions checks toggled.	Make sure that the account running on the headset and the app on PC is the same, and is a developer account with an organization created. Refer to our overview page for setup details.

Step 3. Gather debug log messages

If the above steps don’t resolve the issue, the debug log messages might provide a clue to the problem. In such situations, try routing Debug.Log messages (including exceptions) to text displays visible in your app.

For details, see Unity’s documentation on Application.logMessageReceived.

Did you find this page helpful?