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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note:
Tagged as Won't Fix, because the underlying issue is a lack of data coming from SteamVR/OpenVR