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
1
Found in
4.2.1f4
Issue ID
566002
Regression
No
Pressing Left Shift + Keypad causes keypad to remain in the pressed state
To reproduce:
1. Create a project and add the Test.cs script to it
2. Run the game
3. Press Keypad 8 - console says keypad on
4. While holding the keypad 8, press left shift. Release the keypad 8 and then release shift. Notice how the console is still flooding with Keypad on
Note: seems to happen specifically with left shift + keypad.
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
quill18
Nov 20, 2013 18:10
Note that other modifier keys (Alt, Ctrl) seem to work fine. Only shift seems to be the problem.
quill18
Nov 20, 2013 18:09
In the old system, I reported Case 522013, which is probably related. In my example I was using both Shift keys to control the flippers in a pinball game. On the Mac this worked fine. On Windows, this sequence would cause the keys to start stuck in the "pressed" state:
"Hold the LEFT SHIFT key. Now also hold the RIGHT SHIFT key. Now release the RIGHT SHIFT key. You'll notice that both boxes are stuck in the air until the LEFT SHIFT key is released. The same problem happens if you invert the LEFT/RIGHT order."
This was marked as Resolved/Postponed with this comment from Silviu:
"The bug has been reproduced and our developers have put them on our roadmap for a partial system rewrite. We can't say when this will be ready for release, so we have resolved this bug as postponed."
I reported the bug in Feb 2013 and it was "resolved" in June, though I can confirm that it's still a problem.