Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.4
2019.3.13f1
2020.2
Issue ID
1251159
Regression
No
Assigning a preset to a LODGroup removes reference to the selected Renderer
How to reproduce:
1. Open the project from the attached file "1251159.zip"
2. Open the SampleScene and select the "Test" GameObject
3. In the Inspector select LOD 0 and open the Select Preset window
4. Select any of the two presets
5. Inspect the Renderers section
Expected result: Renderer is assigned to LOD 0
Actual result: There are no Renderers assigned to LOD 0
Reproducible with: 2018.4.25f1, 2019.4.4f1, 2020.1.0b16, 2020.2.0a18
Note: when a preset is selected, re-opening the preset selection window does not show it as selected.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
Fixed in 2021.1.0a1