Search Issue Tracker
Fixed in 0.2.1-preview
Votes
5
Found in [Package]
0.0.9-preview
Issue ID
1091938
Regression
No
[XR] The Vive Pro doesn't have any InputActions
Migrated from GitHub: https://github.com/Unity-Technologies/InputSystem/issues/207
Possible solutions:
- Have the Vive Pro trigger ViveHMD InputActions (which may or may not scale pending exposure of camera features?)
- Add the Vive Pro as a device in a component's public InputAction bindings list
jackpr-unity commented 29 days ago
Still present on 18.3.0b2 and InputSystem package 0.0.7-preview
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
ruoss_ls
Oct 26, 2018 14:33
With: Unity 2018.2.13f1 and 2017.3.0f3
OpenVR Input is working for:
Normal Vive Controller + Normal Vive Controller
Normal Vive Controller + Business Vive Controller
Not working for:
Business Vive Controller + Business Vive Controller
Business Vive Pro Controller + Business Vive Pro Controller