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

Fix force continuous with un-interpolatable value is not applied correctly #93185

Merged
merged 1 commit into from
Jun 17, 2024

Conversation

TokageItLab
Copy link
Member

The un-interpolatable value is forced into discrete mode by the constraints previously described in godotengine/godot-proposals#8085, but it was exclusive of the conversion by force continous. Force continous needs to take precedence over everything else, so I fixed the branching about it.

@TokageItLab TokageItLab added bug topic:animation cherrypick:4.2 Considered for cherry-picking into a future 4.2.x release labels Jun 15, 2024
@TokageItLab TokageItLab added this to the 4.3 milestone Jun 15, 2024
@TokageItLab TokageItLab requested a review from a team as a code owner June 15, 2024 02:32
Copy link
Member

@fire fire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The section of the animation code is hard to evaluate for me, but looks good to me.

@akien-mga akien-mga merged commit ab91c36 into godotengine:master Jun 17, 2024
16 checks passed
@akien-mga
Copy link
Member

Thanks!

@TokageItLab TokageItLab deleted the fix-force-continuous branch June 29, 2024 11:45
@TokageItLab TokageItLab removed the cherrypick:4.2 Considered for cherry-picking into a future 4.2.x release label Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AnimationTree StateMachine transition animation reset behaves weird depending on blend position
3 participants