Search Issue Tracker
By Design
Votes
0
Found in
2017.4
2018.4
2019.2
2019.2.0f1
2019.3
2020.1
Issue ID
1212274
Regression
No
Updated Material properties are not copied to a new instance when they were changed using Material.Lerp
Reproduction steps:
1. Open attached project "1212274_material_lerp" and "SampleScene"
2. Enter Play Mode
Expected result: "instance", changed from red to blue using Material.Lerp, and "instance2" are both blue
Actual result: "instance2" color is red, while "instance" is blue
Reproducible with: 2017.4.36f1, 2018.4.16f1, 2019.2.19f1, 2019.3.0f5, 2020.1.0a20
Note: "instance2" color is set to the color that "instance" was originally instantiated with.
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note:
Creating an instance is just “copying the serialized material object” and it will not contain anything that is set to the shader. Please use CopyPropertiesFromMaterial for copying one material to another: https://docs.unity3d.com/ScriptReference/Material.CopyPropertiesFromMaterial.html