VR body tracking: Quest headset body tracking through OpenXR (XR_FB_body_tracking / XR_META_body_tracking_full_body), incl. Virtual Desktop VDXR #1583

Open
opened 2026-11-17 10:46:08 +00:00 by sky_line · 0 comments
Owner

Full-body tracking (#1565) supports only discrete trackers through XR_HTCX_vive_tracker_interaction. Quest headsets track the body themselves: upper body from the headset and hands, and Quest 3 legs by inside-out body tracking (IOBT) or generated legs. Meta's runtime, and Virtual Desktop's VDXR, expose this to OpenXR apps. Supporting it gives Quest users body tracking with no trackers at all, on the low-latency runtime they already use.

Proposal

A body-tracking source over the OpenXR body-tracking extensions, whichever the runtime offers:

  • XR_FB_body_tracking (70-joint upper body);
  • XR_META_body_tracking_full_body (legs) with XR_META_body_tracking_fidelity (high-fidelity IOBT where supported);
  • optionally XR_BD_body_tracking (Pico) and XR_HTC_body_tracking if the mapping is cheap.

Requirements

  • Enabled as optional extensions (dropped if the instance refuses them), with a body tracker created only while VR is on and the source is selected.
  • Map the runtime's skeleton joints onto LLVRBody's roles and solver: hips, chest, knees, feet, and optionally the spine and neck directly. Use the existing calibration path, where the eye height and scale mapping onto the avatar still apply.
  • Low-confidence or generated legs must not jitter; respect the joints' validity flags, and fade like a lost tracker.
  • Settings: SlipstreamVRBodySource gains "Headset body tracking". In Auto, prefer real trackers, then headset body tracking. Fidelity: Low / High.
  • Log lines: the runtime's body-tracking extensions, the joint set, fidelity, valid joint counts.
  • The "Body" button appears when this source is active.

Part of #1565.

Full-body tracking (#1565) supports only discrete trackers through `XR_HTCX_vive_tracker_interaction`. Quest headsets track the body themselves: upper body from the headset and hands, and Quest 3 legs by inside-out body tracking (IOBT) or generated legs. Meta's runtime, and **Virtual Desktop's VDXR**, expose this to OpenXR apps. Supporting it gives Quest users body tracking with no trackers at all, on the low-latency runtime they already use. ## Proposal A body-tracking source over the OpenXR body-tracking extensions, whichever the runtime offers: - `XR_FB_body_tracking` (70-joint upper body); - `XR_META_body_tracking_full_body` (legs) with `XR_META_body_tracking_fidelity` (high-fidelity IOBT where supported); - optionally `XR_BD_body_tracking` (Pico) and `XR_HTC_body_tracking` if the mapping is cheap. ## Requirements - Enabled as optional extensions (dropped if the instance refuses them), with a body tracker created only while VR is on and the source is selected. - Map the runtime's skeleton joints onto LLVRBody's roles and solver: hips, chest, knees, feet, and optionally the spine and neck directly. Use the existing calibration path, where the eye height and scale mapping onto the avatar still apply. - Low-confidence or generated legs must not jitter; respect the joints' validity flags, and fade like a lost tracker. - **Settings:** `SlipstreamVRBodySource` gains "Headset body tracking". In Auto, prefer real trackers, then headset body tracking. Fidelity: Low / High. - Log lines: the runtime's body-tracking extensions, the joint set, fidelity, valid joint counts. - The "Body" button appears when this source is active. Part of #1565.
sky_line added this to the Slipstream project 2026-11-17 10:46:08 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sky_line/Slipstream#1583
No description provided.