GS/DX12: Expand the fb optimization hit detection backport from GL/DX11.#14595
Merged
Conversation
lightningterror
force-pushed
the
gs_aggressive_fb_opt_the_sequel
branch
from
809a3f7 to
96eb9de
Compare
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
1 participant
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.
Description of Changes
We can actually expand the hit detection even if either color or depth trigger a state change. This allows not the current but subsequent potential state changes to be avoided.
Note this includes the proper RP changes from #14555 so maybe merge that PR first, dump run was used with those changes included as a base.
Rationale behind Changes
Follow up from #14567
Speed, optimizations.
Suggested Testing Steps
Same games as that pr, single to double digit reductions in render passes.
Did you use AI to help find, test, or implement this issue or feature?
No.