Forward a gamepad paired to the headset to the server. Useful when the controller is in range of the headset but not the server, such as a DualSense paired to a Quest over Bluetooth.
The headset reads the gamepad through the OpenXR microsoft/xbox_controller profile and forwards it on the existing input rails: gamepad device ids in the inputs packet, plus a gamepad entry in the interaction profile array that signals connection and disconnection from the tracking thread.
The server exposes a native OpenXR gamepad at /user/gamepad, connected while the headset reports a gamepad interaction profile. This needs no permission and is always available.
Rumble is sent back to the headset and applied through OpenXR haptics.
* Don't override hands from other drivers on interaction profile change
* Rename *_hand to *_controller
* Fix derived pose and tracking control desync with hand interaction
* Reset pose history on switch from hand interaction, code cleanup
Will merge contents from
@CMAKE_INSTALL_PREFIX@/share/wivrn/config.json
/etc/wivrn/config.json
~/.config/wivrn.config.json (XDG_CONFIG_DIR in fact)
If -f option is provided, just parse that file, don't merge anything
Client can describe a pose to be derived from an other one, for instance
AIM can be derived from GRIP by applying an offset and rotation.
This reduces the amount of data that needs to be polled and transmitted
over the network.
- xrt_tracking_offset field 'offset' was renamed to 'initial_offset'
- STAGE is now supported by default, 'stage_supported' is for drivers
that require active polling for the STAGE pose.
- new space offset API included
Add the timestamp where data was requested, use this to compute how far
in the future the application is requesting samples.
With this information, client requests 2 tracking samples: one at the
current time and one in the future.
Server now keeps track of actual samples + one predicted sample, and is
most of the time in the interpolation use case.