-
Notifications
You must be signed in to change notification settings - Fork 162
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
Support for additional 3D input devices #3
Comments
…tored and reorganized the project to support multiple input devices. Allowed the Leap-only scene to have the palm angled downward.
…tionality within the Leap-specific input module (#3).
The interface between Hovercast and the input devices is now much cleaner. All Leap-specific functionality is contained within its Leap input module. There is also a "test" input module which obtains its input data via Unity The device modules are located here: To wire up Leap Motion input, attach the |
Documentation about input modules: |
Adding support for OSVR should allow for a variety of 3D input devices: see #8 |
The v2.0 release currently includes Leap Motion (pre and post Orion) and Vive support. I plan to add support for more devices as I have access to them. This includes:
This list is missing many devices. If anyone has a specific device in mind, please comment here. |
Currently, only the Leap Motion input is supported. This implementation is hidden behind various input interfaces, however, which is the first step toward supporting multiple devices.
The desired input type should be an option that can change at runtime. If necessary, the menu can be completely re-initialized when this occurs -- it doesn't make sense to switch input devices while the menu is in use.
The input interfaces should also provide information related to the current device's capabilities. For example: the device may have only one position/rotation value for each hand, but it also has buttons that could be mapped to certain features.
Hovercast could include features or usage modes that emphasize the specific strengths and capabilities of each input device.
The text was updated successfully, but these errors were encountered: