Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.2f1
Issue ID
938505
Regression
No
Editor displays incorrect "Average Velocity" for animation clips
Steps to reproduce:
1. Open the attached project
2. Open the TestScene scene
3. Play the scene
4. Observe the blue, red and green fields:
The blue 'speed' field updates every second and displays the speed of the character is calculated by taking the difference in positions between updates
The red fields show the value that the method 'apparentSpeed' reports for the run 'AnimationClip' instance that is playing - this corresponds to the inspector value 'Average Velocity' for the clip
The green fields display the value derived from examining 'RootT' first and last keyframes. Once adjusted for human scale, this value appears to match the actual character speed when under root motion control
5. Notice that the red values do not match the observed speed of the character under root motion control
Actual result: The red values do not match the observed speed of the character under root motion control
Expected result: The red values should match the observed speed of the character under root motion control
Reproduced with: 5.5.4p2, 5.6.3f1 , 2017.1.0p3, 2017.2.0b6, 2017.3.0a2
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
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
Resolution Note:
No duplicates or other reports since 2017, and the only person that worked on this is no longer working here. Will probably never fix