D3D11: Allow shader blend to self #11584
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
It was forcing from black before. See hrydgard#9616.
Also, use triangle strip like D3D11.
|
While D3D doesn't have framebuffers that are upside down relative to textures like OpenGL does, it considers positive y to be up in clip space. I think that's the explanation, at least... |
|
Oops, I typed shader blend in the title but meant depal, derp. -[Unknown] |
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 fixes #9616, which was black because D3D11 was checking
currentRenderVfb_even when the actual depal temp target was different.Also, D3D9 and D3D11 weren't applying bounds correctly - D3D11 was skipping them, and D3D9 had them upside down. That said, I'm a bit unclear why they needed flipping, since we don't flip framebufs on D3D... but it matches the pos/uv when not applying bounds.
-[Unknown]