It would be beneficial to support some of the third-party body tracking options available on standalone HMDs, such as the PICO Motion Trackers, so that full functionality for each headset can be experienced while using Steam VRLink.
This would bring the Steam VRLink client closer to parity with some third party options such as Virtual Desktop, ALVR, and WiVRn across several platforms.
As an addition, Meta headsets post Quest 2 need XR_META_body_tracking_fidelity with its status set to High for upper body tracking via the cameras, which has poor documentation outside of a single header file
It would be beneficial to support some of the third-party body tracking options available on standalone HMDs, such as the PICO Motion Trackers, so that full functionality for each headset can be experienced while using Steam VRLink.
Example khronos specs:
https://registry.khronos.org/OpenXR/specs/1.1/html/xrspec.html#XR_BD_body_tracking
https://registry.khronos.org/OpenXR/specs/1.1/html/xrspec.html#XR_FB_body_tracking
https://registry.khronos.org/OpenXR/specs/1.1/html/xrspec.html#XR_HTC_body_tracking
https://registry.khronos.org/OpenXR/specs/1.1/html/xrspec.html#XR_META_body_tracking_full_body
A non-khronos spec example (likely private in some way):
https://pico.crx.moe/docs/pico-openxr/body-tracking-pico/
This would bring the Steam VRLink client closer to parity with some third party options such as Virtual Desktop, ALVR, and WiVRn across several platforms.