Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.4f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131869
Regression
No
Tree Prefab Asset icon does not display leaves
Reproduction steps:
1. Create a new project
2. Create a Tree GameObject (GameObject > 3D Object > Tree)
3. Select newly created GameObject and press “Add Leaf Group” button
4. Make sure Prefab reloads and observe Prefab Asset icon
Actual result: Leaf is not displayed in the icon
Expected result: Leaf is displayed in the icon
Reproducible with: 6000.0.65f1, 6000.3.4f1, 6000.4.0b3, 6000.5.0a4
Reproduced on: macOS Tahoe 26.2 (M4), Ubuntu 24.04
Note: Issue is not reproducible with Branches
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
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
- White flickering artifacts are present on dynamic objects when doing rotation/movement and using APV
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.