VR body tracking: read SlimeVR directly over OSC / VMC (works with Virtual Desktop's VDXR and any runtime) #1582

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

Full-body tracking (#1565) reads trackers only through OpenXR's XR_HTCX_vive_tracker_interaction, which in practice means SteamVR. SlimeVR's trackers exist only inside SteamVR (through its SteamVR driver). So a Quest user on Virtual Desktop's own runtime (VDXR), which many prefer for its lower latency, or on any other non-SteamVR runtime, gets no body tracking.

Proposal

Read SlimeVR directly from the SlimeVR server over the network outputs it already has, independent of the OpenXR runtime:

  • VRChat OSC trackers (/tracking/trackers/N/position|rotation, UDP), and/or
  • VMC protocol (OSC, /VMC/Ext/Tra/Pos trackers and/or /VMC/Ext/Bone/Pos bones).

Pick the one that gives per-role tracker poses most reliably, and document the SlimeVR settings the user must turn on.

Requirements

  • A body source alongside the OpenXR tracker source. Its poses feed the same calibration, IK and body layer (LLVRBody), with roles mapped from SlimeVR's tracker ids or bone names.
  • Space alignment: SlimeVR's space is not the OpenXR play space. Align them using the HMD pose (the head tracker or bone that SlimeVR outputs, plus the T-pose calibration solving yaw and offset), so the feet land under the user.
  • Settings: SlipstreamVRBodySource (Auto / OpenXR trackers / SlimeVR OSC) and the UDP port (default to the SlimeVR / VRChat convention). Listen on localhost only and validate every packet; nothing is sent.
  • Nothing runs unless VR is on and the source is selected (Auto: OpenXR trackers when the runtime lists them, else SlimeVR when packets arrive).
  • The wrist "Body" button appears when either source has trackers.
  • Log lines: source chosen, packets/s, roles seen, alignment result.

Part of #1565.

Full-body tracking (#1565) reads trackers only through OpenXR's `XR_HTCX_vive_tracker_interaction`, which in practice means SteamVR. SlimeVR's trackers exist only inside SteamVR (through its SteamVR driver). So a Quest user on **Virtual Desktop's own runtime (VDXR)**, which many prefer for its lower latency, or on any other non-SteamVR runtime, gets no body tracking. ## Proposal Read SlimeVR directly from the SlimeVR server over the network outputs it already has, independent of the OpenXR runtime: - **VRChat OSC trackers** (`/tracking/trackers/N/position|rotation`, UDP), and/or - **VMC protocol** (OSC, `/VMC/Ext/Tra/Pos` trackers and/or `/VMC/Ext/Bone/Pos` bones). Pick the one that gives per-role tracker poses most reliably, and document the SlimeVR settings the user must turn on. ## Requirements - A body source alongside the OpenXR tracker source. Its poses feed the same calibration, IK and body layer (LLVRBody), with roles mapped from SlimeVR's tracker ids or bone names. - **Space alignment:** SlimeVR's space is not the OpenXR play space. Align them using the HMD pose (the head tracker or bone that SlimeVR outputs, plus the T-pose calibration solving yaw and offset), so the feet land under the user. - **Settings:** `SlipstreamVRBodySource` (Auto / OpenXR trackers / SlimeVR OSC) and the UDP port (default to the SlimeVR / VRChat convention). Listen on localhost only and validate every packet; nothing is sent. - Nothing runs unless VR is on and the source is selected (Auto: OpenXR trackers when the runtime lists them, else SlimeVR when packets arrive). - The wrist "Body" button appears when either source has trackers. - Log lines: source chosen, packets/s, roles seen, alignment result. 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#1582
No description provided.