Search Issue Tracker
Fixed in 1.1.0-preview.3
Votes
0
Found in [Package]
1.1.0-preview.2
Issue ID
1289749
Regression
No
[Input System] "Press" interaction triggers only the first time when both Gamepad and Xbox Controller bindings are attached
Reproduction steps:
1. Open the attached "Demonstration" project
2. Open Assets/Scenes/SampleScene
3. Enter Play Mode
4. Press the South Button on your Controller (A on the Xbox One Controller) multiple times
Expected result: "Triggered" message gets printed multiple times in the Console window
Actual result: "Triggered" message gets printed only once in the Console window
Tested with: Xbox One Controller
Reproduces on: 1.0.1 (2019.4.15f1), 1.1.0-preview.1 (2020.1.15f1), 1.1.0-preview.2 (2020.2.0b13, 2021.1.0a7)
Can't test: 2018.4 (can't successfully import project)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.1.0-preview.3):
Fixed as of 1.1.0-preview.3 by resolver no longer adding the same control multiple times. "<Gamepad>/buttonSouth" and "<XInputController>/buttonSouth" both resolve to the same control. Before, the resolver added the control twice since there were two bindings for it. This in turn engaged "conflict resolution" even though is no conflict here as it's just one control.
Now, the control only gets added once no matter how often it is referenced from the same action.
Package available in Unity 2019.4.0f1 and versions above