Search Issue Tracker
Feature Request
Feature Request in 6000.4.X
Votes
0
Found in
2022.3.66f1
6000.0.60f1
6000.2.8f1
6000.3.0b5
6000.4.0a2
Issue ID
UUM-121699
Regression
No
Terrain Layers don't use icons when viewed in the Project Browser
Steps to reproduce:
- Open any Project
- In a Scene's Hierarchy create a Terrain Game Object and select it
- In the Inspector click the option to "Paint Terrain"
- In the Terrain Layers section click the button "Edit Terrain Layers..." and select "Create"
- Select any Texture
- Search for that Layer in the Project Browser and observe it both in a List View and with Preview
Actual results: In both View Modes an unassigned Icon for an unidentified Asset is used
Expected results: Layer Gear Icon or any other Icon is used as it's an Asset Generated with Unity
Reproducible with versions: 2022.3.66f1, 6000.0.60f1, 6000.2.8f1, 6000.3.0b5, 6000.4.0a2
Tested on (OS): Windows 11
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for taking the time to report this bug and sharing your observations with us. After reviewing the details of the report, we’ve determined that this issue is not a software defect but rather an opportunity to enhance the clarity and usability of the UI.
As such, we’ve transitioned this report into a feature request to explore UI improvements that address the concerns raised. Our team will assess this feature request as part of our ongoing roadmap planning and prioritize it alongside other initiatives based on its impact and feasibility.
Resolution Note (6000.4.X):
Thank you for taking the time to report this bug and sharing your observations with us. After reviewing the details of the report, we’ve determined that this issue is not a software defect but rather an opportunity to enhance the clarity and usability of the UI.
As such, we’ve transitioned this report into a feature request to explore UI improvements that address the concerns raised. Our team will assess this feature request as part of our ongoing roadmap planning and prioritize it alongside other initiatives based on its impact and feasibility.