Search Issue Tracker

Fix In Review for 1.4.X

Votes

0

Found in [Package]

1.2

Issue ID

1393330

Regression

No

[Input System] Reading a gamepad trigger as a button produces inaccurate press/release states

Package: Input System

-

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

  1. Response avatar

    Resolution Note (fix version 1.4):

    Release behavior tweaked by https://github.com/Unity-Technologies/InputSystem/pull/1490.

    Repro project was not correct in so far as `started` being considered as "button press". However, `performed` marks a button press. `started` only means the button (trigger in this case) has moved begun to have a non-zero value.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.