Develop

Use Wide Motion Mode

Updated: Oct 22, 2026
Wide Motion Mode (WMM) allows you to track hands and display plausible hand poses even when the hands are outside the headset’s field of view, improving social presence and wide motion tracking. This is achieved by running Inside Out Body Tracking (IOBT) under the hood and using the estimated hand position when hand tracking is lost.

Benefits of WMM

  • Improved social and self presence by providing plausible hand poses even when your hands are outside your FOV.
  • More reliable wide motion interactions (arm swings, backpacks, throws, and so on)
  • Reduced gesture and interaction failures due to tracking loss when the user turns their head.
  • Arm swing based locomotion, where users use their arms to move around the game, such as Echo VR.

Known limitations

  • While the system will always provide a hand pose, it will not be accurate when hand tracking is lost- the system uses body tracking data for approximate position and last hand pose as the pose itself.
  • You may also see a slight regression in position accuracy due to smoothing when transitioning from body tracking based hand pose to hand tracking based hand pose as hand tracking is reestablished.
  • WMM can be less robust in extremely low light. In case of low light conditions, the system will revert to standard hand tracking.

Compatibility

Hardware compatibility

  • Supported devices: Quest 3 and all future devices.

Software compatibility

  • Unity 6000.0.66f2 or newer
  • Meta XR Core SDK v62+

Feature compatibility

  • IOBT/ WMM will not run when passthrough and full body (FBS) are running along with FMM or Multimodal. To use FMM together with IOBT/ WMM in passthrough, turn off FBS.
  • When using Inside Out Body Tracking, the hands pose exposed via MSDK already includes WMM like fused hands. If you plan to use MSDK and consume hands from ISDK/ hands API, turn on WMM to reduce hand pose mismatch between MSDK and hands API.

Setup

This feature is included in the Unity Integration. To enable WMM, either use the editor or the provided C# scripts. A simple WMM sample scene called HandTrackingWideMotionMode can be found in the Core SDK samples. In the scene, you use a simple UI checkbox to turn the feature on and off. Projects that use the Unity XR Hands package follow Use WMM with Unity XR Hands.

Prerequisite

After importing the Meta XR Core SDK into the project, navigate to the Quest Features section of OVRManager and set Body Tracking Support to Required.
Body tracking set to required

Option 1: Editor

  1. In the Hierarchy, select OVRCameraRig. In the OVRManager, under Inspector, check the Wide Motion Mode Hand Poses Enabled box.
    Checked WMM hand poses box
  2. In Project Settings > Player > Android > Other Settings > Configuration, set the Scripting Backend to IL2CPP and the Target Architectures to ARM64.
    Setting scripting backend and target architectures

Option 2: C# Scripts

To turn on WMM programmatically, use this function on OVRPlugin:
void SetWideMotionModeHandPoses(boolean enabled);
To query if WMM is running, use this function on OVRPlugin:
bool IsWideMotionModeHandPosesEnabled();

Use WMM with Unity XR Hands

If your project uses Unity’s XR Hands package, the MetaHandTrackingDataSourceFeature OpenXR feature brings WMM to it. The editor lists this feature as Meta XR Hand Tracking Data Source. The feature ships in Meta XR Core SDK v209 or later (package com.meta.xr.sdk.core).
The feature is available when the project has both of these packages installed:
  • XR Hands (com.unity.xr.hands) 1.9.0-pre.1 or later
  • Unity OpenXR Plugin (com.unity.xr.openxr) 1.18.0-pre.1 or later
To enable the feature, turn on Meta XR Hand Tracking Data Source in the Meta XR feature group of the OpenXR settings. This feature is one of the default features in that group.
The editor reports an error, with an automatic fix, in these cases:
  • Unity’s Hand Tracking Subsystem feature is not enabled. The feature requires it.
  • Unity’s Hand Tracking Data Source feature or Hand Joints Motion Range feature is also enabled. These features conflict with Meta XR Hand Tracking Data Source, and the automatic fix disables them.
If your scene uses OVRManager, the setting from Option 1: Editor also turns WMM on or off in this feature. To control WMM from a script, use MetaHandTrackingDataSourceFeature:
using Meta.XR;
using UnityEngine.XR.Hands;

// Call from a MonoBehaviour method, such as Start()
if (MetaHandTrackingDataSourceFeature.TryGet(out var feature))
{
    feature.SetWideMotionModeHandPoses(true);
    // true when WMM infers the left hand pose
    bool leftInferred = feature.GetHandPoseSourceInferred(Handedness.Left);
}
TryGet returns true only when the feature exists and is enabled. IsWideMotionModeHandPosesEnabled() returns true when WMM is requested. GetHandPoseSourceInferred returns true when WMM infers the pose of the specified hand.
In an XR Hands project, detect an inferred pose with GetHandPoseSourceInferred on the feature. Detect WMM pose source covers the OVRHand and OVRPlugin APIs.
If WMM is requested but the XR_META_hand_tracking_wide_motion_mode2 OpenXR extension is not enabled, the feature logs an error and hand tracking requests no WMM source.

Detect WMM pose source

You can detect whether a specific hand pose was generated by WMM (body tracking inference) or by camera-based hand tracking. When hands move outside the camera frustum, WMM infers their positions from body tracking. This API lets you identify when that inference is happening.
The recommended approach is to read the PoseSourceInferred property on OVRHand. This property is updated automatically each frame:
  • true: the hand pose comes from WMM (body tracking inference)
  • false: the hand pose comes from camera-based hand tracking
// handLeft is an OVRHand component on the left hand anchor
if (handLeft.PoseSourceInferred)
{
    // Hand pose is inferred from WMM body tracking
    handLeftRenderer.material = inferredHandMaterial;
}
else
{
    // Hand pose is from camera-based hand tracking
    handLeftRenderer.material = normalHandMaterial;
}
WMM must be enabled before this property returns meaningful values. See Option 1: Editor or Option 2: C# Scripts above.
For advanced use cases, you can call the lower-level API directly:
OVRPlugin.Result result = OVRPlugin.GetHandPoseSourceInferred(
    -1, // frameIndex: matches OVRHand.Update() usage
    OVRPlugin.Hand.HandLeft,
    out bool poseInferred);
This method returns an OVRPlugin.Result rather than a bool.
Note: Both OVRHand.PoseSourceInferred and the lower-level OVRPlugin.GetHandPoseSourceInferred require OVRPlugin version 1.115.0 or later.
Note: This API is marked experimental and may change in future SDK versions.

Test WMM via adb

You can also evaluate WMM on your app without the API calls in code, through adb commands.

Before you begin

  1. In PowerShell, or the terminal, run adb devices to ensure adb is installed and the device is discoverable through adb.
You should see a response like this.
    ```
    List of devices attached
    230YC56D0S002V  device_ \
    ```

Steps

  1. To enable WMM, before starting the app, run these commands:
    1. adb shell setprop debug.oculus.forceEnablePerformanceFeatures BODY_TRACKING
    2. adb shell setprop debug.bodyapi.allowhandoverride 1
    3. adb shell setprop debug.bodyapi.handoverridetype 3
  2. To toggle WMM fusion logic before starting the app or while you’re in the app:
    1. Off:adb shell setprop debug.bodyapi.handoverridetype 0
    2. On:adb shell setprop debug.bodyapi.handoverridetype 3

Troubleshooting

  • How can I confirm WMM is running on my headset?
    In your headset, you should see improved tracking of hands outside of your headset’s field of view.
  • Can I evaluate the feature on my headset without changing my code?
    Yes, you can test WMM via adb commands to try the feature without changing your code.