Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.2.0b1
2019.2.0b5
2019.3.0a9
2020.1.0a1
Issue ID
1178593
Regression
No
Additional Curve Data on model animation is offset when it is read by the script
How to reproduce:
1. Open attached project ("authoring-rig.zip") and open MonoBehaviourScene
2. Press Play and then after a few seconds Stop
3. Open Console window
4. Open @EllenWalkForward asset and open Inspector window
5. Compare Additional Curve Data in console vs Additional Curve Data in Inspector window
Expected result: Additional Curve Data matches console output
Actual result: Additional Curve Data is offset
Reproducible with: 2019.2.4f1, 2019.3.0b2, 2020.1.0a3
Not reproducible with: 2017.4.32f1 (Package Manager was not present), 2018.4.8f1, 2019.2.0a14 (Packages namespace errors), 2019.3.0a8 (Packages namespace errors)
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Resolution Note:
“AnimatorState.cycleOffset” specifies where in the animation the cycle should start.
The fractional part of “AnimatorStateInfo.normalizedTime” specifies the % through the current cycle.
Even where cycleOffset is not 0.0, “AnimatorStateInfo.normalizedTime” still starts at 0.0, and thus should not match up to the inspector curve in the supplied case.