Some headsets drift under normal operation. Typically, this is alleviated through the use of a recenter hotkey (example: holding recenter button in daydream) or compositor menu action (example: recenter menu option in GearVR).
This is a suggestion to add configurable mappings from hotkeys, button-sequences, and maybe gestures(?) to dynamically run reset-yaw via a button press or sequence.
So in the above example, when the user presses the button mapped to "/path/to/button/interface", the server resets yaw on /me/head, effective for all clients (including analysis plugins). When the user presses "/path/to/button/interface/1" and "/path/to/button/interface/2" at the same time, then the server resets yaw for /me/hands/left for all clients (including analysis plugins).
Can you put a EXAMPLE with real project, I dont understand how works relative paths. I have a KinectV2 and my idea is when open the left Hand is reseted the YAW.
Some headsets drift under normal operation. Typically, this is alleviated through the use of a recenter hotkey (example: holding recenter button in daydream) or compositor menu action (example: recenter menu option in GearVR).
This is a suggestion to add configurable mappings from hotkeys, button-sequences, and maybe gestures(?) to dynamically run reset-yaw via a button press or sequence.
Potential configuration example:
So in the above example, when the user presses the button mapped to "/path/to/button/interface", the server resets yaw on /me/head, effective for all clients (including analysis plugins). When the user presses "/path/to/button/interface/1" and "/path/to/button/interface/2" at the same time, then the server resets yaw for /me/hands/left for all clients (including analysis plugins).