Search Issue Tracker
Won't Fix
Votes
0
Found in
5.3.4f1
Issue ID
792568
Regression
No
Dragging materials onto specific LOD objects fails when the LOD group object is a prefab
Reproduction steps:
1. Open User's project
2. Open "Main" scene
3. Position the editor camera so both objects are in view, showing the sphere or cube (LOD1 or LOD0).
4. Select LOD2 of the object 'TestObjectWithLOD_NotPrefab_Works' in the hierarchy.
5. Drag TestMaterial from the project window onto the selected object in the 3D view.
6. Select LOD2 of the object 'TestObjectWithLOD_Prefab_Broken' in the hierarchy.
7. Drag TestMaterial from the project window onto the selected object in the 3D view.
Note: Prefab object - the cube or sphere (depends on how close the camera was) (LOD0 or LOD1) material was changed.
Non-prefab object - the capsule (LOD2) material was changed.
Expected: LOD2 renderer of both objects to have TestMaterial applied, and the other LOD levels to be unaffected
Actual: Non-prefab object is set up correctly. The prefab instance changes to whichever LOD level would currently be shown if a specific LOD object wasn't selected, and that object's material is set instead.
Note: It is only set correctly if the camera is far enough away that the capsule would be shown.
Note: The wireframe of selected object is shown, but the solid form of the incorrect LOD level is overlayed.
Reproducible: 5.2.4f1, 5.3.0f4, 5.3.2f1, 5.3.4f1, 5.3.4p5, 5.4.0b16, 2018.3.0a8
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note (2018.3.X):
This particular case has been investigated thoroughly and we have decided, in the interest of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.