Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.30f1
2022.3.10f1
2023.1.14f1
2023.2.0b10
2023.3.0a6
Issue ID
UUM-49118
Regression
No
ForceLOD() does not work when de-selecting the GameObject after instantiation
How to reproduce:
1. Open the user-attached “LODBug.zip” project
2. Open the “SampleScene”
3. Add the “LODObjectSpawner” Prefab into the Scene
4. De-select or select any other GameObject in the Scene
5. Observe the Scene window
Expected result: The Sphere shaped GameObject is visible
Actual result: A Cube shaped GameObject is visible, or the GameObject disappears
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a6
Reproduced on: macOS Ventura 13.5 (Intel), Windows 11 (User Reported)
Not reproduced on: macOS Ventura 13.4 (Intel)
Notes:
- Full spec for the reproduced OS: macOS Ventura 13.4 2,4 GHz 8-Core Intel Core i9 AMD Radeon Pro 5500M 8GB
- Full spec for the non-reproduced OS: macOS Ventura 13.4 (Intel) 3,4 GHz Quad-Core Intel Core i5 Radeon Pro 570 4GB
- The issue appears to not reproduce being close to the affected GameObject
- ForceLOD(1/2) appears to give similar results
- The issue might stem from the execution of “GetComponent<LODGroup>().ForceLOD(0);”
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
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
- Crash on mono_array_length when building a project
- "StackOverflowException" error when changing spline curve type from "Bezier" to "Auto" in the "Element Inspector"
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.
In this case, it seems ForceLOD works properly in Game mode, lowering the impact of the issue by a significant margin.
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.