Search Issue Tracker
Fixed in 2019.1.X
Votes
30
Found in
2018.2.1f1
Issue ID
1066427
Regression
Yes
Vive Tracker causes an error and does not report input
Steps to Reproduce:
- Connect a Vive tracker to SteamVR
- Open the attached project
- enter playmode
Minimum reproduction
- Connect a Vive tracker to SteamVR
- Launch the Unity editor
- Enable VR and add the OpenVR SDK
- Add a cube to the scene with a tracked pose driver that tracks a hand (doesn't have to match the tracker)
- enter playmode
Expected:
Vive Tracker is tracked and triggers some input when used in conjunction with an accessory.
Observed:
With a Vive Tracker connected, an error is triggered every frame:
"Attempting to set a device feature value type that is not supported by VRInputInstance. This will result in an incomplete state"
The Vive tracker will no longer trigger legacy input system buttons.
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
- Text overlap and is unreadable in Inspector > Terrain Paint Texture after creating new Terrain Layer
- Event "XRInputSubsystem.trackingOriginUpdated" triggers twice when recentering the view
- UITK TextField value is overwritten incorrectly by the converter result when Binding Mode is set to "To Source"
- Out of memory crash when selecting more than 80000 Assets simultaneously
- Test Runner fails to create a script in the active path when selecting a file as the active path
yngar
Aug 31, 2018 20:27
I am getting the same bug. I've found that I can only seem to get input on the first two controllers/trackers that were turned on. If I turn on two trackers I can get button input from them via the pogo pin interface but any controllers turned on after that will not return input. If I turn on the controllers first they will get input but any trackers turned on after that will not.