Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.44f1
6000.1.0b13
6000.2.0a8
Issue ID
UUM-101911
Regression
No
UI Actions are presented as code strings not as human language options
*Steps to reproduce:*
# Create a project
# Go to Edit -> Project Settings
# Go to the "Input System Package"
# Select the "UI" option under the "Action Maps"
# Observe the "Actions" list
*Actual results:* "RightClick", "MiddleClick", "ScrollWheel", "TrackedDevicePosition", and "TrackedDeviceOrientation" miss spaces between the words. A screenshot is added below in the "Attachments" section.
*Expected results:* It should be: "Right Click", "Middle Click", "Scroll Wheel", "Tracked Device Position", and "Tracked Device Orientation". Items in the UI should be presented in human language. This section should be consistent with all other engine sections.
*Reproducible with versions:* 6000.0.44f1, 6000.1.0b13, 6000.2.0a8
*Not reproducible with versions:* -
*Can’t test with versions:* 2022.3.59f1 Input section is not listed in the "Project Settings" list.
*Tested on (OS):* M1 Max - Sequoia 15.3.2
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
- Unity Package Manager Events Not Triggered When Changing Registry
- "DateTime.Now" in the UK timezone does not adjust when the British Summer Time is active
- "Unsupported source texture format (7) in ComputeNextMipLevel" error is shown and the texture atlas is corrupted when the texture format "RGB Compressed ETC2 4bits" is selected
- The label that uses data binding is no longer updated at runtime when `INotifyBindablePropertyChanged` reloads updates of the VisualTreeAsset in UIDocument
- HDRP Graphics "High Quality Line Rendering" is missing a documentation link
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.