Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AnimationTree resets Skeleton3D when playing empty animation #76036

Closed
Coxcopi opened this issue Apr 13, 2023 · 2 comments
Closed

AnimationTree resets Skeleton3D when playing empty animation #76036

Coxcopi opened this issue Apr 13, 2023 · 2 comments

Comments

@Coxcopi
Copy link

Coxcopi commented Apr 13, 2023

Godot version

v4.0.2.stable.official [7a0977c]

System information

Windows 10, Forward+ (Vulkan)

Issue description

In an AnimationTree (State Machine), when a Skeleton3D is posed/deformed through an animation, and the animation player travels to an empty animation (or an animation that does not contain keyframes for the bones of the Skeleton), the whole Skeleton3D is reset to its base pose.

The same does however not happen when only using an AnimationPlayer.

Expected Result (using an AnimationPlayer):

Desktop.2023.04.13.-.19.44.56.02_Trim.mp4

Playing the empty animation after the other one simply keeps the deformation of the Skeleton.

Actual Result (AnimationTree):

Desktop.2023.04.13.-.19.44.17.01_Trim.mp4

Playing the empty animation resets the Skeleton.

Steps to reproduce

  • Play an animation in the AnimationPlayer state machine that changes the pose of the Skeleton
  • Play an empty animation (one that does not have keyframes for the Skeletons bones) in the AnimationPlayer state machine
    -> the Skeleton3D resets.

  • Play both animations in the AnimationPlayer
    -> no reset.

Minimal reproduction project

animation_tree_bug.zip

@Coxcopi
Copy link
Author

Coxcopi commented May 7, 2023

This might actually be related to, or even caused by #76538, since every time I encountered the bug, the empty animation was inside another AnimationLibrary. I'm gonna do do some further testing to see if that's where the issue is coming from.

@TokageItLab
Copy link
Member

TokageItLab commented May 11, 2023

Dupe of #73571, this is the intended behavior for now.

@TokageItLab TokageItLab closed this as not planned Won't fix, can't repro, duplicate, stale May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants