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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Add comment