Search Issue Tracker
Won't Fix
Won't Fix in 1.16.X
Votes
0
Found in [Package]
1.14.2
1.16.0
Issue ID
ISXB-1771
Regression
No
Supported device usage appear as code strings instead of readable text in Input System Settings
Steps to reproduce:
- Create a project
- Go to "Edit" -> "Project Settings"
- Select "Settings" displayed under the "Input System Package"
- Click "Create settings asset"
- Click "+" in the "Supported Devices" section
- Select "Keyboard -> Usages" from the list
- Observe the listed options
Actual results: "Primary2DMotion", "PrimaryAction", "PrimaryTigger", "ScrollHorizontal", and others are displayed as code strings
Expected results: It should be: "Primary 2D Motion", "Primary Action", "Primary Tigger", "Scroll Horizontal"
Reproducible with versions: 1.16.0 (6000.0.63f1), 1.14.2 (6000.2.13f1), 1.16.0 (6000.3.0f1), 1.15.0 (6000.4.0a5), 1.16.0 (6000.5.0a2)
Tested on (OS): macOS - Tahoe 26.1
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.16.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.