Search Issue Tracker
Won't Fix
Votes
4
Found in
2021.3.47f1
2022.3.54f1
6000.0.31f1
6000.1.0a7
6000.3.0a1
6000.5.0a1
Issue ID
UUM-90946
Regression
No
LODs lower than QualitySettings.maximumLodLevel do not get stripped when building project for the first time
Reproduction steps:
1. Open the attached “Test_MaximumLodLevel.zip” project
2. In the top menu click “BuildMethods” > “Run TestBuild”
3. Observe the Player and the text in the top left corner
Expected result: “LOD 2 : renderers=1” is the only that is present and has value '1'
Actual result: “LOD 0 : renderers=1”, “LOD 1 : renderers=1” and “LOD 2 : renderers=1” text is visible, meaning all renderers are present
Reproducible with: 2021.3.47f1, 2022.3.54f1, 6000.0.31f1, 6000.1.0a7
Reproducible on: Windows 10 (User reported), Windows 11
Not reproducible on: no other environment tested
Notes:
- The issue reproduces only the first time building the project and building it after that shows the expected result
- The user has a workaround where clicking “BuildMethods” > “Run TestBuildWithWorkaround” first builds a “dummy” build and then the “actual” build after that
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thanks again for reporting this issue. We’ve had quite a bit of internal discussion since it was filed, and rather than addressing the bug directly, we’ve decided to pursue a broader change to how usage information and stripping work in Unity.
This goes beyond a simple fix to ensure a more stable platform moving forwards, so we’re closing the issue for now - but your report was genuinely helpful in shaping the direction, sincerely appreciate it!