Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
3
Found in
2019.4
Issue ID
1280104
Regression
Yes
[Linux] Keypad number keys reporting incorrectly
Accidental regression due to recent changes.
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 mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
alfish
Oct 05, 2020 18:04
Similar bug in Input System package: https://forum.unity.com/threads/how-can-i-enable-active-polling-to-workaround-this-gamepad-drift-bug.978897/#post-6358926
The keys are mapped all wrong in the Editor Player (runtime works). It doesn't seem to be a keyboard layout problem, as it also happens in US layout. Kubuntu 20.04, Unity 2020.1.4f1.