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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 1.1.0-pre.5):
Fixed in package version 1.1.0-pre.5