[d3d8] Use D3D8 compatibilty mode to set HUD API level #4664
+2
−31
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
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.
Kind of a minor derp that went unnoticed so far: in d8vk we were only setting the correct API level for the implicit swapchain. If games decided to create any additional swapchains, the HUD would incorrectly show D3D9.
I've uncovered this thanks to Serious Sam (The First/Second Encounter), which does just that.
The PR removes the needless
SetAPINamecascading calls from the d3d9 bridge and simply relies on the D3D8 compatibility mode when determining the HUD API level.