Search Issue Tracker
Fixed in 2019.3.X
Votes
1
Found in
2017.4.0f1
2018.3.0a1
2018.3.14f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1156287
Regression
No
AnimatorStateInfo.normalizedTime returns the total play time of animation state when Normalized Value is set to Parameter
How to reproduce:
1. Open the attached project ("case_1156287")
2. Enter Play Mode
Expected result: Console prints ("Normalized time: 0.0")
Actual result: Normalized time is equal to the time the state is playing
Reproducible with: 2017.4.27f1, 2018.4.1f1, 2019.1.4f1, 2019.2.0b4, 2019.3.0a4
-
Byvar
Jul 24, 2019 15:05
If this is the expected behavior, is it possible to expose a property for motionTime as well then?
For our project, we need the time when the motion is evaluated rather than the time the animation has been playing... there is currently no way to see this in Unity, which means that other animation systems that integrate with Mecanim cannot support this parameter-driven Motion Time. Thank you in advance.
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
- Treeview is infinitely populating items when using IL2CPP build
- ProBuilder prefab thumbnails do not showcase the prefab when observed in the Project window
- Wrong documentation page is displayed for the "Scene Template Pipeline" help icon
- Missing Device Simulator API
- Shadow gets cut off when in Play Mode and using shader "Shader Graph/Rotation Shader" for material
Resolution Note (fix version 2019.3):
This is the expected behaviour, but there is a confusion because the AnimatorStateInfo's normalized time refers to the internal time in the state machine (useful to make transitions) while the AnimatorStateEditor's normalized time refers to the time at which the motion is evaluated. I changed the Editor's string to "Motion Time" to better convey that tey are two different times and that getting different values is normal. I also updated the Manual accordingly (pending review).
------------------------------------------------
Fixed in 2019.3.0a8