Search Issue Tracker
Won't Fix
Votes
0
Found in
Issue ID
1060266
Regression
No
[2018.2][GearVR] Oculus HMD device exists, and incorrectly drives button 1 based on the remote's back button
Steps to Reproduce
1) Run the single scene in the attached reproduction project
Expected:
Input from the back button is only routed to button 6 if the remote is set to left hand or button 7 if the remote is set to right hand. When the back button is pressed, this causes the corresponding Unity button (6 or 7) to be active for a single frame.
There is no "HMD" device joystick
Observed:
Input.GetJoystickNames() reveals an Oculus HMD device. When the back button is pressed on the remote, this device drives button 1. As long as the back button is pressed, Unity button 1 registers as pressed.
Why is matters:
This could drive unwanted input.
Observed in 2018.2.0f2
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (2018.2.X):
XR Management has evaluated this issue and determined that it does not meet our current bug severity threshold. If you would like your issue to be reviewed again, please re-submit your bug.