Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.8f1
Issue ID
1148315
Regression
No
Analog input for OpenVR controllers doesn't go through for non-HTC manufactured devices
Tagged as Won't Fix because the underlying issue is a lack of data coming from SteamVR/OpenVR.
This issue was found by a customer who changed just the manufacturer string on a Vive controller.
Steps to Reproduce:
- Open the attached project, "BugRepro_UnityInput.zip"
- Get the firmware-modifed controller from Jackpr
- Open SampleScene.unity and enter playmode
Expected:
Observe the public fields on the GameObject UnityInput. All buttons and axes should report normally.
Observed:
The analog values for the trigger and trackpad do not report normally.
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
Resolution Note:
Tagged as Won't Fix, because the underlying issue is a lack of data coming from SteamVR/OpenVR