OpenXR module
The OpenXR module receives head pose, hand tracking and stereo H264 video from an OpenXR-based VR application, pushed continuously over a local named pipe by a separate component: the HEAT OpenXR API layer. This module does no video decoding - it passes each H264 access unit through unmodified, for whatever consumes the session downstream to decode.
What you need
The HEAT OpenXR API layer (a separate install, from
CaptureApp-OpenXR) must be installed and
registered with the OpenXR loader before this module receives anything. It plugs into the
Khronos OpenXR API-layer mechanism ;
with SteamVR, confirm it under Settings → OpenXR → Manage OpenXR Layers. See
Interface Control Document for the pipe contract between the two.
Hidden module setting
The named pipe name is a hidden module setting, HeatOpenXRDataPipe, defaulting to
heat_openxr_data_pipe. It is not exposed in HEAT Capture’s settings UI. The API layer must use
the same name. Deploy matching module and layer versions; neither side negotiates a protocol
version. See Interface Control Document Section 8.
The module also exposes the generic settings every module has - Enabled, Interval,
OverrideNodeId/NodeId, Timeout - see
Manage capture modules.
Pages
- Data produced: what is published, and the video encoding parameters.
- Troubleshooting: symptoms, causes and fixes.
- Interface Control Document: ICD-CMOPENXR-001, the named-pipe contract with the HEAT OpenXR API layer.