Search Issue Tracker
Fixed in 5.5.0f3
Votes
3
Found in
5.5.0p1
Issue ID
869197
Regression
No
[VR Input] Oculus Touch and OpenVR documentation wrong or button mappings are wrong
The Documentation reports that the Left Controller Menu button on Vive corresponded to Button.Three (X) on the touch controller. However, when setting up the button mappings and testing the Oculus touch controllers while using the OpenVR SDK we found that Button.Four (Y) correspondes to the Left Controller Menue Button, not Button.Three (X)
This is the same for the right controller as well (Button.Two (B) Corresponds to the Right Controller Menu Button, not Button.One, as reported in the docs.
2. How we can reproduce it using the example you attached
1) Download attached project
2) Set OpenVR as the primary SDK
3) Setup Oculus Rift
4) Enter Playmode
5) Press the Y button
6) Observe that the text field "X (Left Menu Button):" reports the button is pressed/held. This is the bug.
Expected:
The Y button does nothing when using OpenVR. Instead, upon pressing the X button the text field "X (Left Menu Button):" reports that the button is being pressed\held.
Either that or change the docs or talk to valve about this.
Related documentation: https://docs.unity3d.com/Manual/OpenVRControllers.html
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment