Search Issue Tracker
Won't Fix
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
- FBX Resamples Curves incorrectly when importing FBX files
- ProBuilder GameObject Faces disappear when increasing the Sides Count value
- FileUtil.CopyFileOrDirectory throws IOException when destination parent folder does not exist
- The Editor is stuttering when G-Sync is enabled and set to "Enable for windowed and full screen mode"
- USS files are not marked as dirty when an element is added to the Hierarchy
Resolution Note:
There are no fixes planned for this Bug