Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.4.5p1
Issue ID
897821
Regression
No
[Animation] Changing Animator.Speed during animation transition does not affect the cross-fade speed
Reproduction Steps:
1. Import attached project.
2. Open "MyScene" scene.
3. Enter Play mode.
Expected results: Transition to attack_light should accordingly make animator speed be 1.
Actual results: Transition to attack_light is much slower than 1.
Note: The character in the hierarchy has a few parameters to fiddle with:
-Trigger: Uses triggers to transition the animation
-CrossFade: Uses CrossFade method in code to transition the animation
-CrossFade in Fixed Time: Uses CrossFadeInFixedTime method in code to transition the animation
The bug reproduces with both Trigger and CrossFade. It does not reproduce with CrossFadeInFixedTime.
Reproducible with: 5.4.4p1, 5.5.3f1, 5.6.0f3, 2017.1.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment