Search Issue Tracker
By Design
Votes
0
Found in
5.2.2f1
Issue ID
745853
Regression
No
Mecanim isn't consistently writing defaults for animated properties with constant keyframe values
How to reproduce:
1. Open the attached project
2. Open and play Bug scene
3. Expand Daifni and Doctor model till you see "Bip001 Pelvis" (Daifni>Bip001>Bip001 Pelvis)
4. Attempt to move on X, Y,Z axis both models separately while animations are playing
5. Notice that you are able to move Daifni, this model doesn't rewrite constant values which are animated.
Expected behavior: we shouldn't be able to move Daifni as it has constant keyframes just like Doctor model.
By Design: developers did an optimization in Mecanim that makes when the current value of a parameter/Transform is the same in each clip of animation controller and is the same as the value in the scene, it is not written back. According to them this is the approach that is used right now and not going to be changed at least at the moment.
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
Add comment