Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.44f1
2021.3.17f1
2022.1.24f1
2022.2.4f1
2023.1.0b1
Issue ID
UUM-25082
Regression
No
[LOD] Prefab Instance overrides not showing a blue line indicator near LOD Group component when LOD Group Renderers are overridden
How to reproduce:
- Open the attached project "DebugLODGroup2020.zip"
- Open Assets/Scenes/SampleScene.unity
- Select "Prefab_Overrided" in the Hierarchy window
Expected results: LOD Group component has a blue line indicator
Actual results: LOD Group component does not have a blue line indicator
Reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.1.24f1, 2022.2.4f1, 2023.1.0b1
Reproducible on: Windows 10
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 FindNearestVertex when objectsToSearch array contains a null transform
- Context menu item checkmark updates only after reopening twice when using Menu.SetChecked on component context menu items
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
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 (2023.1.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.