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

Animation state machine Xfade time produces T pose appearing #76162

Closed
ilievmark opened this issue Apr 17, 2023 · 5 comments
Closed

Animation state machine Xfade time produces T pose appearing #76162

ilievmark opened this issue Apr 17, 2023 · 5 comments

Comments

@ilievmark
Copy link

Godot version

4.0.2 mono

System information

Mac OS Ventura 13.2.1

Issue description

If you setup cycled animation in state machine, with multiple states and internal state machine and put some transitions Xfade time to more than 0, T pose will start to appear for one frame

bug2.mp4

For this example I setup internal state machine for idle animations state machine with 4 animations. Ive set Xfade time 0.2
for transitions from idle to jump and jump landing to idle. This is just example, but Im facing this issue using multiple internal state machines. In attached example, use conditions to swith states

Steps to reproduce

Setup project from this report: #76159
Create internal state machine with some states
Create states to interact with the internal state machine
Between states and internal state machine create transitions and put Xfade time to value more that 0
T pose may appear in some cases

Minimal reproduction project

example.zip

@ilievmark
Copy link
Author

ilievmark commented Apr 17, 2023

The same problem appears between two internal state machines, if you put Xfade time to some value in transition between them

@TokageItLab
Copy link
Member

TokageItLab commented Apr 17, 2023

I remember I have fixed the 1-frame glitch in #75759 (but it is not merged yet).

@ilievmark
Copy link
Author

@TokageItLab
It there any assumptions in which version it may be merged? 4.0.3?

@TokageItLab
Copy link
Member

Maybe 4.1 since it has some breaking compatibilities.

@TokageItLab
Copy link
Member

Closed by #75759

@TokageItLab TokageItLab added this to the 4.1 milestone Apr 25, 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