-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add ability to move the world with both hands #2
Comments
Teleportation is an interesting idea. Thanks |
I used incorrect terminology at first. I briefly forgot that you don't have teleportation, but that you move the world instead. So ignore that, world-moving is fine. |
@brianpeiris Hey Brian, thanks for the feedback! On Vive, since the wand controllers are the same for both hands, we designed it such that left-handed players can just swap which controller goes in which hand. This is more of an issue for Rift where the left and right controller cannot be interchanged. But you're right that the other hand's trigger is unused and could be also used for something like moving the world. I will definitely consider adding it. My only concern may be the confusion over having multiple world moving icons or lines coming out of each controller may make it harder to see which controller is pointing at what. The only way to find out what is right is to do some user testing to see how it goes. :) I will keep you updated and would love more feedback from you once we implement more changes. |
If you do implement this, personally I would like to have one hand for moving the world about and another hand for navigating and selecting the code (preferably configurable). While attempting to navigate through some code earlier today I kept accidentally dragging the world when trying to select classes as my pointer would move just a bit as pulled the trigger. (HTC Vive) |
Summary
The trigger on the left hand seems to be unused. I'd like to be able to move the world with it.
Platform (Vive, Rift, Windows MR, GearVR): Vive
The text was updated successfully, but these errors were encountered: