Fix framebuffer size flopping back and forth #9603
Merged
Conversation
This file contains 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
If block transfers are keeping it larger, keep it larger.
This was probably always meant to be <=, since it logically makes sense for them to be equal. Might fix cases of resizing down a framebuf in throughmode, where viewport isn't as good a heuristic.
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.
This avoids a performance regression in God of War caused by #8867.
Just reusing the existing tracking to make sure we don't flop sizes of framebuffers back and forth. Still renders the ending video of Valkyrie Profile correctly (although it still crashes at the end because the mpeg is timed inaccurately.)
-[Unknown]