You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In an Animation BlendTree, if you connect a TimeScale node with a negative value (to play an animation, in this case, with Linear Loop, in reverse) after a Transition node with XFade Time, and request a switch between states, the resulting animation gets completely messed up.
Putting the timescale before the transition (and right after the Animation nodes) solves the problem, but creates an excessively large number of repeated nodes if you have several animations to transition between.
Other issues may steam from improper handling of animations being played in reverse, specially in complex Animation BlendTrees. Blend2 doesn't seem to take too kindly to them, with weird blending between looped animations with positive and negative timescales.
Steps to reproduce
Create a BlendTree for an animated character (in my case Imported from Blender as a .glb file and created as an Inherited Scene).
Setup your BlendTree like this:
Click in the Transition node (Make sure it has an XFade Time of like 0.25s) to switch between states.
If the auto transitions don't work, that is expected behavior1, but if the manual Xfade is broken, that may not be a good thing. Perhaps the fade time accumlator in Xfade does not support negative values. I assume this can be solved by using absolute values.
Footnotes
Negative timescale does not treat the beginning of the NodeAnimation as the end of the animation. ↩
Godot version
v4.0.3.stable.official [5222a99]
System information
Windows 10
Issue description
In an Animation BlendTree, if you connect a TimeScale node with a negative value (to play an animation, in this case, with Linear Loop, in reverse) after a Transition node with XFade Time, and request a switch between states, the resulting animation gets completely messed up.
Putting the timescale before the transition (and right after the Animation nodes) solves the problem, but creates an excessively large number of repeated nodes if you have several animations to transition between.
Other issues may steam from improper handling of animations being played in reverse, specially in complex Animation BlendTrees. Blend2 doesn't seem to take too kindly to them, with weird blending between looped animations with positive and negative timescales.
Steps to reproduce
Minimal reproduction project
TestRoom.zip
The text was updated successfully, but these errors were encountered: