Search Issue Tracker
Won't Fix
Votes
1
Found in
2019.4.13f1
Issue ID
1294235
Regression
No
[XR] The A, B, X, and Y buttons for the HP Reverb G2 controllers aren't supported natively
Reproduction steps:
1. Open new Unity project
2. Attempt to use HP Reverb G2 controller's A, B, X, and Y buttons for input
Expected result: The A, B, X, and Y buttons are supported
Actual result: The A, B, X, and Y buttons are not supported
Reproducible with: 2019.4.13f1
Could not test with: 2018.4.30f1, 2019.4.16f1, 2020.1.16f1, 2020.2.0b14, 2021.1.0a8
Workaround:
You can add a Microsoft plugin and follow the setup steps to bypass the issue (https://docs.microsoft.com/en-us/windows/mixed-reality/develop/unity/unity-reverb-g2-controllers).
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
- Package signature validation unexpectedly return an invalid signature status if the validation check is done after the code signing certificate validaty range has passed
- 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
Resolution Note (2021.1.X):
This bug is within the Microsoft Mixed Reality code. We have reported your issue to MS.