Search Issue Tracker
By Design
By Design in 6000.6.X
Votes
0
Found in
6000.0.69f1
6000.3.11f1
6000.4.0b10
6000.5.0a8
6000.6.0a1
Issue ID
UUM-136329
Regression
No
Material's icon doesn't fit the "Material preview not available" text when the Material doesn't have a preview
How to reproduce:
1. Open the attached project "BugMaterial"
2. In the Project window, expand the "New VFX" Asset
3. In the expanded Asset, select any Material
4. Observe the Inspector's header icon
Expected results: The icon is missing
Actual results: Partially visible text is used instead of icon
Reproducible with: 6000.0.69f1, 6000.3.11f1, 6000.4.0b10, 6000.5.0a8
Reproducible on: Ubuntu 24, macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
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
- Attribute on Toolbar Overlay does not resolve when importing .unitypackage
- Remote repository size is not shown for GitHub repositories when expanding project details
- "Repository name" field and "slug preview" don't have correct validation and become inconsistent when unsupported characters are entered
- Package Manager throws ScriptableSingleton related errors after a package was installed while there were pending package manifest changes
- Default Branch name does not change when changing the Default Branch name for a project that was disconnected from a repository
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.6.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.