Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.3.5f1
6000.4.0b4
6000.5.0a5
Issue ID
UUM-132371
Regression
No
String "RenderPipelineGlobalSettings" is not localized in the Inspector window help box
Steps to reproduce:
- Create a new Unity project
- Select "UniversalRenderPipelineGlobalSettings" asset displayed in the "Project" window
- Go to the "Inspector" window and observe the text in the displayed help box section
Actual results: String "RenderPipelineGlobalSettings" in the help box message is not localized
Expected results: It should be "Render Pipeline Global Settings". All the message should look like "Render Pipeline Global Settings should be edited from Project Settings > Graphics"
Reproducible with versions: 6000.3.5f1, 6000.4.0b4, 6000.5.0a5
Tested on (OS): macOS - Tahoe 26.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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.