Search Issue Tracker
Duplicate
Votes
0
Found in
2019.4
2020.3
2021.1
2021.1.13f1
2021.2
2022.1
Issue ID
1348746
Regression
No
"Shift" key causes causes other keys to retain their pressed state when released
How to reproduce:
1. Create a new project
2. Open the Package Manager, and install and enable the new Input System
3. Open the "Input Debugger" windows by going to the menu bar: Window > Analysis > Input Debugger
4. In the window expand the "Devices" section and double-click on the keyboard
5. Observe the "a" key's value in the "Keyboard" window while performing the following step
6. Hold down "a" then "Shift", release "a" and then "Shift"
Expected result: The "a" key's value returns to 0
Actual result: The "a" key's value stays 1
Reproducible with: 2019.4.28f1, 2020.3.14f1, 2021.1.13f1, 2021.2.0b3, 2022.1.0a1
Could not test with: 2018.4.35f1 (no "Input System" package listed in the Package Manager)
Notes:
1. Reproducible on Ubuntu 18.04
2. Not reproducible on Windows 7
3. Pressing the key again sets its value back to 0
4. Reproducible only on the new Input System
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
This is a duplicate of issue #1344266