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
- Crash on GameObject::QueryComponentByType when opening a project
- "Object reference not set to an instance of an object" is thrown when destroying a GameObject with a Camera Component
- [Android] The error message "OPENGL NATIVE PLUG-IN ERROR: GL_OUT_OF_MEMORY:" is thrown when the video is playing
- [IL2CPP] Build fails with the error "[1mcannot convert 'Nullable_1_tEA06D91799914C5C8830F83CE2A8395868C14F02' to 'int32_t' (aka 'int') without a conversion operator" when IL2CPP is used as the Scripting Backend
- Rigidbody interpolation is performed after the next frame's FixedUpdate() when using Rigidbody2D
This is a duplicate of issue #1344266