Search Issue Tracker
Fixed in 1.1.0-pre.5
Votes
0
Found in [Package]
1.0.0
Issue ID
1254705
Regression
No
The display names for keyboard keys in the input debugger do not match those defined in input system package
The display names for keyboard keys in the input debugger do not match those defined in input system package. One consequence is that the display names shown in the input debugger on windows are uppercase while they are lowercase on macos and linux. The discrepancy can be seen by opening InputSystem/Devices/Keyboard.cs in the input system package and observing the displayNames for most keys do not match the display names down in the input debugger.
Case 1210302 partially notes this issue but does not fix the use of keyboard layout names instead of display names.
repro:
1. open input debugger in windows editor
2. double click keyboard device
3. observe display name for a key reads 'A'
4. repeat 1-3 on mac or linux but observe the display name for a key reads 'a'
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
- Post Processing SMAA breaks when HDR mode R11G11B10 is selected and Color Space is changed
- The "UnityWebRequest.result" of the "UnityWebRequestTexture.GetTexture" method changes when accessing "UnityWebRequest.downloadHandler" texture
- Slider rounding does not allow setting certain valid numbers as Values when Low and High Values not set to default
- UI Builder Canvas has too big resizing zone on the outside of the canvas
- GetCurrentAnimatorClipInfoCount() and GetNextAnimatorClipInfoCount() return 0 when animator is in transition
Resolution Note (fix version 1.1.0-pre.5):
Fixed in package version 1.1.0-pre.5