Search Issue Tracker
By Design
Votes
0
Found in
2022.3.58f1
6000.0.38f1
6000.1.0b6
6000.2.0a3
Issue ID
UUM-97495
Regression
No
Emission property of the material can't be modified using script when an Animation is set to change it overriding the script
How to reproduce:
1. Open the “AnimationOverrideBug_2025_02_10“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Observe the “Sphere” and “Cube” GameObjects in the Scene view
Expected result: “Sphere” is changing color similarly as “Cube”
Actual result: “Sphere” stays black
Reproducible in: 2022.3.58f1, 6000.0.38f1, 6000.1.0b6, 6000.2.0a3
Reproduced on: Windows 10, Windows 11 (user’s)
Not reproduced on: No other environments tested
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
While this is understandably frustrating, this is the behavior of the Animator as it was designed: it will write the current value of every property in any clip connected to the Animator, even if that clip is not actively being evaluated.
This is a longstanding behavior, which cannot be changed without subtly breaking existing games.
If you need to override this behavior, then applying your overrides in LateUpdate is a strategy you can use to bypass this issue.