Search Issue Tracker
Fixed in 1.1.0-preview.3
Votes
0
Found in [Package]
1.1.0-preview.2
Issue ID
1296688
Regression
No
[Input System] Inconsistent Input behavior with a key when using 2D Vector Composite with the Press Interaction
Reproduction steps:
1. Open the attached "Input Vector Test" project
2. Open Assets/Scenes/SampleScene
3. Enter Play Mode
4. Press the A key on the keyboard
5. Without releasing the A key, press down the D key
Expected result: The Action.performed only gets called when A gets pressed, when pressing D nothing happens (can be seen int the console window)
Actual result: The Action.performed only gets called when A gets pressed, when pressing D Action.performed gets printed (can be seen int the console window)
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)
Note:
- This only happens when pressing the keys of the same axis, Left and Right (A and D), Up and Down (W and S)
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 1.1.0-preview.3):
Fixed package version available in Unity 2019.4.0f1 and above