Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Votes
1
Found in
2021.3.40f1
2022.3.38f1
6000.0.11f1
Issue ID
UUM-76438
Regression
No
Models which have a LOD below the MaximumLOD level are not omitted in a build when the GameObjects are Instantiated after loading the scene
Reproduction steps:
1. Open the attached “MaxLODbug” project
2. In the “Build Profiles” window (File > Build Profiles), make sure only one scene is selected (can be “(AssetReference)”, “(DirectReference)” or ”(Resources)”)
3. Make sure “Development Build” and “Autoconnect Profiler” settings are enabled
4. Press “Build And Run”
5. Capture a memory snapshot using the Memory Profiler
6. Open the captured snapshot, select the “Unity Objects” tab
7. Observe the “Mesh” line in the memory allocation table
Expected result: The “ash_02_LOD0” mesh is not loaded
Actual result: The “ash_02_LOD0” mesh is loaded
Reproducible with: 2021.3.40f1, 2023.3.38f1, 6000.0.11f1
Reproducible on: Windows 11, macOS 14
Not reproducible on: No other environment tested
Notes:
- Models which have a LOD below the MaximumLOD level are only omitted when GameObjects are placed inside the scene before making the build
- Reproducible with Addressable Asset reference, direct reference and Resources reference
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Select Preset "None" icon changes after switching tabs
- [Android] Crash when using xxHash3 and targeting the ARMv7 Architecture with IL2CPP Scripting Backend
- GameObject reference in a Script Component becomes missing when unpacking a variant of another Prefab variant
- Project Settings vertical separator position is not synchronized with the mouse position when dragging it horizontally
- Crash on PhysicsDebugDraw::SelectFiltering::Update when entering play mode with Physics Debug window docked and unfocused
Add comment