Search Issue Tracker
By Design
Votes
0
Found in
5.5.1f1
Issue ID
910419
Regression
No
Flat animation curves with value of 0 do not update every frame
Steps to reproduce:
1. Open attached project
2. Open "scene" scene
3. Select "GameObject" in the Hierarchy
"GameObject/Cube" has a flat animation curve setting its local position to Vector3.zero
4. Select "FlatAt1" in the Hierarchy
"FlatAt1/Cube" has a flat animation curve setting its local position to Vector3.one
Both cubes local positions are altered in the LateUpdate in CubeMove.cs
5. Enter play mode
Expected result: both cubes stay at the local position set by their animations even though their position is altered in the LateUpdate
Actual result: cube with a flat curve setting its local position to Vector3.zero doesn't update everyframe, therefore it keeps moving when altered by the script
Cube animation behaves as expected if local position value is very close to zero, but not zero
Reproducible with: 5.5.3p3, 5.6.1f1, 2017.1.0b5
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note (2017.1.0f3):
The animation system only evaluates constant curves once and then gameplay can modify the value afterwards. Thus, you'll get a change in behaviour depending on what curve (constant or non-constant) is used to animate a parameter. Constant curves that have the same values as the default scene values will not write to the scene every frame. This is been done to save the cost of writing to transforms.