VR body tracking: read SlimeVR directly over OSC / VMC (works with Virtual Desktop's VDXR and any runtime) #1582
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#1582
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
/tracking/trackers/N/position|rotation, UDP), and/or/VMC/Ext/Tra/Postrackers and/or/VMC/Ext/Bone/Posbones).Pick the one that gives per-role tracker poses most reliably, and document the SlimeVR settings the user must turn on.
Requirements
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.Part of #1565.