Symptom	Resolution
Body tracking works with controllers when running on the Meta Quest headset, but not with hands	Ensure you have enabled hand tracking permissions on your headset, under Settings > Movement Tracking > Hand Tracking. Also, in the Unreal Editor, ensure that Hand Tracking and Controllers are enabled in your project’s configuration.
Meta Horizon Link: Body tracking, face tracking, or eye tracking works when running an app directly on the headset as an Android build, but fails to run over Link.	1. Ensure connection with a USB cable that supports data transfer: Open Oculus App on the PC. 2. Under Device Settings, go to Link Cable and choose Connect Your Headset > Continue. 3. Ensure you have Developer Runtime Features enabled on the Oculus App on the PC by navigating to Settings > Developer > Developer Runtime Features. 4. Ensure that Eye Tracking over Meta Horizon Link and Natural Facial Expressions over Horizon Link are enabled.
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.	Animation Node: Ensure you have requested the body tracking service to start tracking during the start of your application (like pawn Begin Play). Actor Component: The Body Tracking component should automatically start the body tracking service on startup. Check that you have enabled body-tracking in the MetaXR plugin settings. Check that you are requesting the relevant permissions for body tracking
Meta Horizon Link: When running the app on PC, it starts on PC, but doesn’t appear on the headset.	Check that Meta Horizon 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 a team created. Refer to our overview page for setup details.
Character has working body tracking but hovers up in the air or is down below ground.	Ensure you are correctly setting the Tracking Origin to Floor Level during your pawn’s begin play.
App crashes on startup	1. Ensure you have applied all recommended settings from the MetaXR project setup tool, 2. Ensure you are requesting the required permissions at the start of your application 3. Ensure you are only requesting permissions that your device supports
Unreal encounters compile issues when opening the Unreal Movement Samples project	Make sure you have the latest version of the sample. Delete all temp-folders in the project root as well as under the plugin directory: Binaries, DerivedDataCache,Intermediate,Saved. You should now be prompted to rebuild the project when you open it next

Debugging retargeting

Currently the visulaizations described in this section are only visible when using PCVR.

It is often useful to visualize the skeleton received from the tracking services (Oculus Body Tracking Skeleton) compared to the skeleton after you have completed the bone mapping and retargeting (retargeted skeleton). There are two fields added to the OculusXR Body Tracking node to support debug visualization. The Debug Pose Mode limits the debug to the rest pose.

The Debug Draw Mode provides four options:

None. Do not draw the debug skeleton.

Rest Poses. Draw only the rest poses.

Rest Pose with Mapping Draw the rest pose and the adjustments made between the rest pose of the skeleton and the tracking skeleton.

Frame Pose. Draw the current frame pose as show by the body tracking skeleton.

Frame Pose with Mapping. Draw the frame pose from the body tracking skeleton as modified by the adjustments to match the character.

Common errors like mapping the wrong bones should be immediately obvious and distinguisable from tracking errors. For instance, if you see a bone in the tracking skeleton behaving correctly, but the bone in the retargeted skeleton not moving, then you can guess there was probably a naming mismatch in the bone mapping. In the following image, you can see the Oculus Body Tracking skeleton in red, and the final retargeted output in blue.

The retargeted algorithm depends on calculating offsets between the rest poses. As such there is another visualization provided for these skeletons with the following colors:

Yellow: The Oculus XR Body Tracking rest pose / T-pose (tracking skeleton)

Green: Your skeletal mesh’ rest pose(retargeted)

This can help you understand which bones may need manual corrections.

Did you find this page helpful?