Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.66f1
6000.3.6f1
6000.4.0b5
6000.5.0a6
Issue ID
UUM-133343
Regression
No
Environment Library Asset has incorrect icon on creation
How to reproduce:
1. Create a new HDRP Unity project
2. Go to Window -> Rendering -> Look Dev -> Environment -> Library -> New
3. Observe the icon of the Environment Library Asset before confirming the name
4. In the Project window, right-click -> Create -> Rendering -> Environment Library
5. Observe the icon of the Asset
Expected results: Both times the Scriptable Object icon appears
Actual results: The first time the default file icon appears and the second time there is no icon
Reproducible with: 6000.0.66f1, 6000.3.6f1, 6000.4.0b5, 6000.5.0a6
Reproducible on: 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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
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.