Search Issue Tracker
Fixed in 1.1.0-preview.3
Votes
0
Found in [Package]
1.1.0-preview.2
Issue ID
1295535
Regression
Yes
Input System not registering multiple inputs
Reproduction steps:
1. Open the user attached project "New Input System"
2. Open the scene "assets/test"
3. Enter Play mode
4. Use buttons A, S, K, L, and Space to print 't' in the console
5. Press any Two buttons in quick succession or simultaneously (example: A + Space)
Expected result: t Is printed to console with every keypress
Actual result: t Is printed to console once when keys are pressed in quick succession (or simultaneously)
Reproducible with: 1.1.0-preview.2 (2020.2.0f1)
Not reproducible with: 1.0.0, 1.0.1, 1.1.0-preview.1 (2020.1.17f1)
Could not test with: 2018.4, 2019.4, 2021.1 (Compiler errors)
Comments (1)
-
paulstraw
Feb 20, 2021 05:37
I was running into this issue with InputSystem 1.0.1 (a bit odd, as this issue lists 1.0.1 as not reproducible). Upgrading to 1.1.0-preview.3 did indeed fix it, but I'm now seeing the same issue in reverse. That is, pressing buttons in quick succession/simultaneously now sometimes results in one of the buttons _not firing at all_ instead of getting stuck on. I wasn't able to find an issue for this, and I'm not really sure what the process is for submitting an issue for a preview version. Hopefully someone can point me in the right direction :)
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
- Cubemap mipmaps display differently between Editor and Player when using custom mipmaps
- Graph Inspector has no padding at the top and the bottom
- Crash on memcpy when entering the Play Mode in a specific project
- SH Evaluation Mode has no performance difference when set to "Per Vertex" compared to "Per Pixel"
- Multiple Bug Reporters spawned when crashing from several threads at once
Resolution Note (fix version 1.1.0-preview.3):
Fixed in 1.1.0-preview.3 available in 2019.4 and up