Vulkan/D3D12: Make resource transitions explicit, remove the Vulkan auto-transition pass - #3338
Merged
Merged
Conversation
xen2
force-pushed
the
feature/explicit-compute-transitions
branch
from
August 8, 2026 16:47
bbd054f to
a987b91
Compare
8 tasks
xen2
force-pushed
the
feature/explicit-compute-transitions
branch
from
August 9, 2026 09:10
bdf0356 to
004fb6e
Compare
8 tasks
xen2
force-pushed
the
feature/explicit-compute-transitions
branch
from
August 9, 2026 11:36
004fb6e to
c9f5541
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
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.
PR Details
Stacked on #3337.
Counter-proposal to #3329: instead of adding automatic barrier tracking to D3D12, resource transitions are now explicit at the renderer level on all backends.
This removes stopgap and temporary code from old implementation and align all platforms as intended.
Changes
ComputeEffectShader) transition their bound textures explicitly, based on effect reflection.Clearnow leaves targets in their write layout, matching D3D12.DepthStencilReadOnlyflag, with an explicit transition whereForwardRendererbinds it, instead of layouts baked into the pipeline.TransitionBoundResources) is deleted, along with the unused D3D12ResourceTrackingscaffolding.Related Issue
Types of changes
Checklist