Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.3.8f1
6000.4.0b8
6000.5.0a6
Issue ID
UUM-133921
Regression
No
UI Document icon is pixelated in Editor Hierarchy
Reproduction steps:
1. Create a new project and make sure new Hierarchy window is enabled
2. Enable Hierarchy Integration in Project Settings (Edit > Project Settings… > UI Toolkit)
3. GameObject > UI Toolkit > UI Document
4. Observe “<none>.uxml” VisualTreeAsset GameObject icon in Editor Hierarchy
Actual result: Icon is pixelated
Expected result: Icon is sharp and not pixelated
Reproducible with: 6000.3.8f1, 6000.4.0b8, 6000.5.0a6
Couldn’t reproduce with: 6000.0.67f1 (No Enable Hierarchy Integration option)
Reproduced on: macOS Sequoia 26.2 (M4)
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
- ScrollView clips content when under an ancestor that has a filter set
- "Retrieving array element that was out of bounds" error thrown when attempting to remove a column from a Multi-Column List View
- Multi-Column List View horizontal scroll resets to left most position when scrolling vertically
- Floating License is lost for concurrent jobs
- Warning "Failed to insert item" is logged when Assigning Project to Organization's Project in the Project Settings
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 (6000.5.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.