Search Issue Tracker
Won't Fix
Won't Fix in 1.12.X
Votes
0
Found in [Package]
1.12.0
Issue ID
OXPB-10
Regression
No
[Oculus][InputSystem] Trigger and Grip Inputs don't go back to 0 when released.
We are also tracking this in Favro with Meta: [https://favro.com/organization/c564ede4ed3337f7b17986b6/7d68353be445fc2630fc1f1c?card=Uni-324032]
When using the Input System, trigger and grip values start at 0, but once pressed will fluctuate on very small values for up to a minute before finally settling back to 0.
This breaks some of the default Action behaviour, since the control is never truly released.
Steps to Reproduce:
1. Open Sample Project
2. Open Sample Scene in Assets folder
3. Open Input Debugger Window (Windows -> Analysis -> Input Debugger)
4. Hit Play
5. Select a device in the Input Debugger (Devices -> OculusTouchController[Left/Right])
6. Scroll down the chart until you see both Grip and Trigger rows.
7. Observe resting value
8. Press Grip and Trigger and release them
9. Observe current values
Expected: Released grip and trigger values return to 0
Result: Released grip and trigger fluctuate values rapidly on very small values.
Note: This can be fixed either in the native SDK, or can be fixed within the Input System Layouts.
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
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.12.X):
There are no fixes planned for this Bug