Search Issue Tracker
By Design
Votes
0
Found in
2017.3.1p1
Issue ID
1012406
Regression
No
LOD Group component contains references to Renderers of a different LOD Group after pasting LOD Group component values
How to reproduce:
1. Open the attached "1012406_repro.zip" project
2. Select "LodGroup_1" GameObject from the Hierarchy
3. In the Inspector, observe that LOD 0 has "Object" (which is a child of "LodGroup_1") added as a renderer
4. Select "LodGroup_2" GameObject from the Hierarchy
5. In the Inspector, observe that LOD 0 has "Object" (which is a child of "LodGroup_2") added as a renderer
6. Copy LOD component of the "LodGroup_1" and "Paste Component Values" to "LodGroup_2"
Expected result: LOD 0 renderers of "LodGroup_2" still contain a reference to the child "Object" of the "LodGroup_2".
Actual result: LOD 0 renderers of "LodGroup_2" now contain a reference to the child "Object" of the "LodGroup_1". Thus, one "Object" has more than one LODGroup.
Reproducible with - 2017.4.0f1, 2017.4.13f1, 2018.2.12f1, 2018.3.0b6, 2019.1.0a5
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:
The properties were copied and we don't support relative references