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
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
Resolution Note:
Tagged as Won't Fix, because the underlying issue is a lack of data coming from SteamVR/OpenVR