Search Issue Tracker
Duplicate
Votes
0
Found in
2018.2.0a6
2018.2.0b3
Issue ID
1035076
Regression
Yes
Incorrect processing of input keys when navigating the scene view with directional keys + Shift
To reproduce:
1. Open any project
2. Try navigating the scene using the shift+ two non-opposite directional keys (try going diagonal)
Expected: directional keys' input is not ignored
Actual: after the Shift is began to be held down, new directional keys' events are ignored
Reproduced in: 2018.2.0a6, 2018.2.0b3
Not reproduced in: 2017.2.3f1, 2017.4.3f1, 2018.1.0f2, 2018.2.0a5
Note1: directional keys used: W,A,S,D
Note2: odd behavior examples:
pressing Shift and then directional buttons result in viewport camera not moving
pressing two directional keys and then shift works, but changing input to new directions while shift still on hold will be ignored
press directional button, then shift. Camera's moving, however, releasing directional keys and pressing them again will be ignored (while Shift still being held down)
Conclusion: After Shift is being pressed down and held, no new directional input will be recognised
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
This is a duplicate of issue #1018932