Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configurable recenter hotkey/gesture/button-sequence #553

Open
JeroMiya opened this issue Jun 28, 2017 · 1 comment
Open

Configurable recenter hotkey/gesture/button-sequence #553

JeroMiya opened this issue Jun 28, 2017 · 1 comment

Comments

@JeroMiya
Copy link
Contributor

JeroMiya commented Jun 28, 2017

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:

{
  "resetYawHotkeys": {
    "/me/head": {
      "sourceButtonInterface": "/path/to/button/interface"
    },
    "/me/hands/left": {
      "sourceButtonInterfaces": [ "/path/to/button/interface/1", "/path/to/button/interface/2" ]
    }
  }
}

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).

@nevalonvr
Copy link

nevalonvr commented Dec 7, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants