Use correct scaling type when falling back to bilinear#110672
Merged
Repiteo merged 1 commit intogodotengine:masterfrom Oct 6, 2025
Merged
Use correct scaling type when falling back to bilinear#110672Repiteo merged 1 commit intogodotengine:masterfrom
Repiteo merged 1 commit intogodotengine:masterfrom
Conversation
clayjohn
approved these changes
Oct 4, 2025
Member
clayjohn
left a comment
There was a problem hiding this comment.
This entire function is starting to get really messy and could probably do with some cleanup. But I won't let that block this simple fix. Given the state of the code currently, this is the correct fix.
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
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.
When falling back to bilinear scaling under multiple circumstances the scaling type was not updated and could still be temporal even though bilinear is spatial.
Fixes #107704