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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
There are no fixes planned for this Bug