Conversation
jenatali
approved these changes
Apr 9, 2026
vdwtanner
added a commit
that referenced
this pull request
Apr 14, 2026
…AT_OP_NOALPHABLEND Set D3DFORMAT_OP_NOALPHABLEND soley based on D3D12_FORMAT_SUPPORT1_BLENDABLE (cherry picked from commit 3cd2491)
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
2 participants
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.
Ran a bunch of comparison format queries between native9 and 9on12 on my AMD GPU.
Main interesting results:
When just checking for
D3DUSAGE_QUERY_POSTPIXELSHADER_BLENDING, the main difference was that native9 reported blendable for block compressed formats, while d3d12's checks don't support that. probably not an issue?D3DUSAGE_RENDERTARGET | D3DUSAGE_QUERY_POSTPIXELSHADER_BLENDINGcheck showed differences for bump map formats (eg: D3DFMT_Q8W8V8U8 or D3DFMT_V8U8) - 9on12 marks them as not RT while native 9 allows them as RT (on this device). Not changing this for now since there is a comment that indicates that this difference may cause test failures. Unsure of how IHV is working around this, but probably not a big deal.