Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
1.1.0-preview.3
Issue ID
1333234
Regression
No
Keyboard.current.anyKey.wasPressedThisFrame value is incorrect on keyboard click when clicking different keys rapidly
Reproduction steps:
1. Open user's project "InputBug.zip"
2. Enter Play Mode
3. Click on Game View to get a focus on it
4. Click different keys of the keyboard slowly
5. Notice how Console prints out a message where both values are True
6. Click different keys of the keyboard rapidly
Expected result: Keyboard.current.anyKey.wasPressedThisFrame registers clicks correctly both when different keys are clicked slowly and rapidly
Actual result: Sometimes Keyboard.current.anyKey.wasPressedThisFrame value is False, while Input.anyKeyDown is True when different keys are clicked rapidly
Reproducible with: 1.0.2 (2019.4.26f1, 2020.3.8f1, 2021.1.6f1, 2021.2.0a16), 1.1.0-preview.3 (2021.1.6f1, 2021.2.0a16)
Couldn't test with: 2018.4 (Input System is not available)
More consistent bad behavior is observed when:
- You hold one key and click other
- Using package version 1.1.0-preview.3
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note:
Postponing until further notice due to higher priority needs. We hope to revisit this at a later time.