Search Issue Tracker
Feature Request
Votes
2
Found in
2021.3.40f1
2022.3.38f1
6000.0.11f1
6000.1.0a7
6000.2.0a1
7000.0.0a1
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
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note:
Thank you for reporting a bug to Unity.
We will be logging this as a Feature Request for the future.