Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.27f1
Issue ID
UUM-40324
Regression
Yes
LODGroup throws MissingReferenceException error when using DestroyImmediate
Reproduction steps:
1. Open the attached “Test Project” project
2. Open the “Scenes/SampleScene” Scene
3. Select the “GameObject” GO in the Hierarchy window
4. Open the Context Menu of “Group LOD Manager (Script)” Component
5. Press “Add LOD Group”
6. Repeat step 4
7. Press “Remove LOD Group”
Expected result: LOD Group is removed without any errors
Actual result: A lot of errors are printed out in the Console
Reproducible with: 2021.2.0a17, 2021.2.19f1, 2021.3.27f1, 2022.1.0a14
Not reproducible with: 2020.3.48f1, 2021.2.0a16, 2022.1.24f1, 2022.3.2f1, 2023.1.0f1, 2023.2.0a19
Fixed in: 2022.1.0a15
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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, as it is a non-blocking issue that seems to be resolved with later updates, 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.