GLTF: Enforce STEP interpolation for integer and boolean animations#111615
Merged
Repiteo merged 1 commit intoOct 21, 2025
Conversation
This was referenced Oct 13, 2025
fire
approved these changes
Oct 14, 2025
Contributor
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The KHR_animation_pointer specification is very clear:
This PR updates the glTF animation export to ensure that STEP interpolation is used. For the sake of user-friendliness, if a Godot animation track has an incorrect interpolation type, a warning will be printed:
This is required to fix incorrect exports of KHR_node_visibility animations.