Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
1
Found in
6000.0.65f1
6000.3.4f1
6000.4.0b4
6000.5.0a5
Issue ID
UUM-131926
Regression
No
Holes and different colors appear on default Tree Materials after applying them to the Tree GameObject and undoing changes
Reproduction steps:
1. Create a new 3D (Built-in Render Pipeline) template project
2. Create a Tree GameObject (GameObject > 3D Object > Tree)
3. Select newly created GameObject and press “Add Leaf Group” button in the Inspector
4. Assign Bark Material to the Branch and Leaf Material to the Leaf and Apply changes
5. Add Tree Renderer to the LOD Group and observe the Preview window
6. Undo changes several times and observe the Tree GameObject in the Scene view and Material icon in the Project window
Actual result: Holes appear on the Tree and Material icons
Expected result: Changes are reverted
Reproducible with: 6000.0.65f1, 6000.3.4f1, 6000.4.0b4
Couldn’t reproduce with: 6000.5.0a4 (No 3D (Built-in Render Pipeline) template)
Reproduced on: macOS Tahoe 26.2 (M4), Ubuntu 24.04
Note: Several different colours appear on the Tree and Material icons if Material colors are changed to non-default ones
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
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
- Mixers do not have "Rename" in the right-click context menu when a Mixer is right-clicked in the Audio Mixer window
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.