Search Issue Tracker
Won't Fix
Won't Fix in 1.4.X
Votes
0
Found in [Package]
1.2.0
1.3.0
Issue ID
ISXB-160
Regression
No
[Input System] Reading a gamepad trigger as a button produces inaccurate press/release states
Reproduction steps:
1. Open project "InputSystem_TriggerIssue.zip"
2. Open the Scene "SampleScene"
3. Enter Play Mode
4. Press the right trigger button on the gamepad then let go
5. Observe the Console window
Expected result: 2 Callbacks are called in the Console window (Pressed and Released)
Actual result: More than 2 Callback are called in the Console window
Reproducible with: 1.2.0 (2019.4.34f1), 1.3.0 (2020.3.25f1, 2021.2.7f1, 2022.1.0b2, 2022.2.0a1)
Note:
- Tested on a PS5 controller
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
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.4.X):
This is an intentional behavioral change from this commit: https://github.com/Unity-Technologies/InputSystem/commit/753bc6b2a76a65512a49d724763df9b1cac6a9d0
The change is documented there in "CHANGELOG.md"