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.0a5
Issue ID
UUM-131884
Regression
No
Tree GameObject appears grey when rotated in the Preview window
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. Increase the Frequency and add LOD Group Component
5. Add Tree Renderer to the LOD Group and observe the Preview window
6. Turn the Tree around in the Preview window and observe
Actual result: Tree GameObject appears grey when rotated
Expected result: Tree GameObject displays correct colours
Reproducible with: 6000.0.65f1, 6000.3.4f1, 6000.4.0b3
Couldn’t reproduce with: 6000.5.0a4 (No 3D (Built-in Render Pipeline) template)
Reproduced on: macOS Tahoe 26.2 (M4), Ubuntu 24.04
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
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
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.