Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0a5
2017.1.0a6
Issue ID
1035635
Regression
Yes
[Animation] Rotation and scale is not reset to curve values every frame when having animation curves driven objects
To reproduce:
1. Open user's attached project
2. Enter Play mode
3. Using Hierarchy search, find "Weapon_root" object in the scene
4. While object's selected, try rotating it (any method)
Expected: objects controlled by animation curves have their transform reset to appropriate values every frame
Actual: objects controlled by animation curves do not get their transform reset
Reproduced in: 2017.1.0a6, 2017.1.3p4, 2017.2.3f1, 2017.4.3f1, 2018.1.0f2, 2018.2.0b3
Not reproduced in: 2017.1.0a1, 2017.1.0a5
Resolved "By Design":
When all the curves that affect a property in an AnimatorController are constant, this property is considered constant. For performance reasons, we write the constant values once, and never write them again. Between 2017.1.0a5 and 2017.1.0a6, we fixed a longstanding bug where some constant curves were wrongly evaluated as non-constant.
In order to work around this change, you can include an animation clip that modifies the curves you want to be written in your AnimatorController. You can include this clip anywhere, and it doesn't need to be played or reachable by transitions, just to exist.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment