Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
2
Found in
6000.0.45f1
6000.1.14f1
6000.2.0b13
6000.3.0a3
6000.4.0a1
Issue ID
UUM-113050
Regression
No
Material properties are lost when setting a parent that hasn't been loaded yet
Reproduction steps:
1. Open the attached “IN-108816” project
2. Select “test/matC” Material in the Project window
3. Select “Flatten Material Variant” option from the Inspector window’s context menu
4. Repeat steps 2-3 with “test/matD” material
5. Restart the Editor
6. Drag “test/matB” Material onto “test/matC” Material
7. Drag “test/matB” Material onto “test/matD” Material
OR
1. Open the attached “IN-108816” project
2. Flatten the materials and unload unused assets (Tools > Test Material Bug part1)
3. Assign “matB” Material as parent of “matC” Material (Tools > Test Material Bug part2)
4. Assign “matB” Material as parent of “matD” Material (Tools > Test Material Bug part3)
Expected result: Both “matC” and “matD” materials keep their properties
Actual result: “matC” material properties are reset while “matD” material properties are preserved
Reproducible with: 6000.0.54f1, 6000.1.14f1, 6000.2.0b13, 6000.3.0a3
Reproducible on: Ubuntu 25.04, Windows 11
Not reproducible on: No other environment tested
Comments (1)
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
- Gradient Editor window bottom-right gradient marker color is incorrect
- MaskField tooltips should only display Value when bound
- Reordering Enum Values in VFX Graph Uint Property expands the “Value” field
- Visual Effect Graph sample titles display in non-human-readable format
- UxmlNamespacePrefix does not apply when using UIBuilder documents
aciil
Jul 30, 2025 00:49
Use case of this bug appearing is crafting a custom inspector for shaders. Such as If you do automation to swap the MaterialEditor's parent material during a shader swap (the shaders are almost identical in structure and editor path but with optimizations): you will likely see this happen during the management of the parent material (will happen when the editor is freshly launched).
As you are not able to swap the shader in the MaterialEditor until the parent material reference is null, the parent material will end up manually stored and migrated into this strange disk load state where the reproducible bug here is found.