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

Cannot set the transition node for Animationtree statemachines #79486

Closed
christianbecker3 opened this issue Jul 14, 2023 · 1 comment
Closed

Comments

@christianbecker3
Copy link

Godot version

Godot Engine v4.1.stable.official [9704596]

System information

Godot v4.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1070 (NVIDIA; 31.0.15.3598) - Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 Threads)

Issue description

Hi,
unfortunately the ability to select the exit destination for an animation node to a statemachine inside the animationtree seems to be broken.
Before 4.1, there was a menu which let you select the destination node for the animationtree. But when you connect now in 4.1 any node to a statemachine, you won't see the menu to select any node as an exit destination. It seems like that the transition from the animation to the statemachine doesn't work either. Also, if you open up projects before 4.1, all connections to from animations to statemachines are removed.
I also attached a freshly made project in 4.1, where you see that I was able to connect an animationnode to the statemachine, but I couldn't set anything up.

Steps to reproduce

  • Create an Animationplayer with two animations
  • Create an Animationtree
  • Add an animation to the Animationtree
  • Add a statemachine to the Animationtree
  • Add one Animation inside the statemachine
  • Connect the animation outside the statemachine to the statemachine
  • No prompt/menu whatsoever to select which node will be connected inside the statemachine

Minimal reproduction project

AnimationTreeTestProject.zip

@TokageItLab
Copy link
Member

TokageItLab commented Jul 16, 2023

That feature was removed in #75759 for the pointer safety. The procedure for migrating is commented in #75759 (comment).

@TokageItLab TokageItLab closed this as not planned Won't fix, can't repro, duplicate, stale Jul 16, 2023
@TokageItLab TokageItLab removed this from the 4.2 milestone Jul 16, 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