Subpass Dependency添加约束及反向同步失效问题咨询

Let's break down why your second subpass dependency isn't working, and clarify the key constraints of subpass dependencies involving VK_SUBPASS_EXTERNAL.

Why Your Second Dependency Fails #

The core issue comes down to two critical details in Vulkan's subpass dependency rules, especially when combining VK_SUBPASS_EXTERNAL with the ByRegion flag:

1. Region Scoping for VK_SUBPASS_EXTERNAL + ByRegion

When you set DependencyFlags.ByRegion and SourceSubpass = VK_SUBPASS_EXTERNAL, Vulkan restricts the synchronization scope to the render area of the current (destination) render pass—not the previous one.

In your first working dependency, where DestinationSubpass = VK_SUBPASS_EXTERNAL, the ByRegion flag uses the render area of the source (first) pass. This guarantees every region written by the first pass is complete before the external pass reads it, which aligns perfectly with your needs.

But in your second dependency, ByRegion only syncs the areas covered by the second pass. If the second pass reads parts of the texture written by the first pass that fall outside its own render area, those regions won’t be synced. Even if render areas match, Vulkan’s by-region sync for external sources has strict alignment requirements that can lead to race conditions (and artifacts) if not perfectly configured.

2. Incomplete Pipeline Stage Coverage

Your second dependency uses SourceStageMask = PipelineStageFlags.ColorAttachmentOutput, but this might not capture all stages needed to ensure the color attachment write is fully committed to memory. For example, if your first render pass uses depth/stencil testing, the actual color write doesn’t finish until after the LateFragmentTests stage. If you don’t include this stage in SourceStageMask, Vulkan might allow the second pass’s fragment shader to read the texture before the write is truly complete.

Fixes to Try #

Here are two straightforward solutions to resolve the artifacts:

Option 1: Remove ByRegion for Cross-Render-Pass Sync

Switch to a global dependency (no ByRegion flag) to ensure the entire texture write from the first pass is complete before the second pass reads any part of it:

SubpassDependency subpassDependency = new SubpassDependency() {
    SourceSubpass = (~0U), // VK_SUBPASS_EXTERNAL
    DestinationSubpass = 0,
    SourceAccessMask = AccessFlags.ColorAttachmentWrite,
    SourceStageMask = PipelineStageFlags.ColorAttachmentOutput | PipelineStageFlags.LateFragmentTests, // Include late fragment tests if your pass uses depth/stencil
    DestinationAccessMask = AccessFlags.ShaderRead,
    DestinationStageMask = PipelineStageFlags.FragmentShader,
    DependencyFlags = DependencyFlags.None, // Disable per-region sync
};

Option 2: Keep ByRegion (If Needed) but Align Render Areas and Stages

If you need per-region sync (e.g., for tiled rendering), make sure:

• The render areas of both render passes are identical (double-check your RenderPassBeginInfo settings for both passes).
• Expand SourceStageMask to include all stages that affect the color write:

  SourceStageMask = PipelineStageFlags.ColorAttachmentOutput | PipelineStageFlags.LateFragmentTests,
  

Key Rule to Remember #

When working with VK_SUBPASS_EXTERNAL in subpass dependencies:

• For dependencies waiting on prior queue commands (source = external), ByRegion syncs to the destination pass's render area.
• For dependencies signaling subsequent queue commands (destination = external), ByRegion syncs to the source pass's render area.
• Always ensure your pipeline stages cover all operations that affect the resource you're syncing (don’t forget late fragment tests, depth/stencil operations, etc.).

内容的提问来源于stack exchange，提问作者Bähny