Vulkan: Work around AMD exclusive fullscreen bug (21.3+) #9635
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
BhaaLseN
reviewed
Apr 11, 2021
|
how did this issue pop up just in 5.0-14002 but nothing before it? at any rate thanks for fixing it ^^ |
|
People were reporting it happening in older builds than that. It's a driver bug and nothing caused by anything dolphin changed. |
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.
AMD's binary driver as of 21.3 seems to return exclusive fullscreen lost even when it was never requested, so long as the caller requested it to be application controlled. Handle this ignoring the lost result and just continuing as normal if we never acquired it.
References: