HP Reverb G2 Controller Profile
Enables the OpenXR interaction profile for the HP Reverb G2 Controller and exposes the <ReverbG2Controller> device layout within the Unity Input System.
For more information about the HP Reverb G2 interaction profile, refer to the OpenXR Specification.
Available controls
The following table outlines the mapping between the OpenXR paths and Unity's implementation:
| OpenXR Path | Unity Control Name | Type |
|---|---|---|
/input/x/click |
primaryButton (Left Hand Only) | Boolean |
/input/y/click |
secondaryButton (Left Hand Only) | Boolean |
/input/a/click |
primaryButton (Right Hand Only) | Boolean |
/input/b/click |
secondaryButton (Right Hand Only) | Boolean |
/input/menu/click |
menu | Boolean |
/input/squeeze/value |
grip | Float |
/input/squeeze/value |
gripPressed | Boolean (float cast to Boolean) |
/input/trigger/value |
trigger | Float |
/input/trigger/value |
triggerPressed | Boolean (float cast to Boolean) |
/input/thumbstick |
thumbstick | Vector2 |
/input/thumbstick/click |
thumbstickClicked | Boolean |
/input/grip/pose |
devicePose | Pose |
/input/aim/pose |
pointer | Pose |
/output/haptic |
haptic | Vibrate |
| Unity Layout Only | isTracked | Flag Data |
| Unity Layout Only | trackingState | Flag Data |
| Unity Layout Only | devicePosition | Vector3 |
| Unity Layout Only | deviceRotation | Quaternion |
Note
Some Unity controls don't correspond to an OpenXR path. Unity expresses Pose data as individual elements, whereas OpenXR expresses poses as a group of data. These additional controls contain Unity Layout Only in the OpenXR Path column. You can use this additional Pose data for more fine-grained controls. To learn more, refer to Pose data.