Vulkan中光线追踪图像与交换链图像转场同步问题排查

我是Vulkan/图形API新手，学习同步知识后代码仍有异常：光线追踪管线本该输出纯蓝色图像，却频繁在蓝色与黑色间闪烁。验证层每帧提示“提交的图像需处于VK_IMAGE_LAYOUT_PRESENT_SRC_KHR或VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR布局，当前为VK_IMAGE_LAYOUT_UNDEFINED”。

已定位问题根源是选错交换链图像，但想确认代码中阶段与访问掩码设置的合理性，比如将信号量等待阶段设为VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BIT未触发异常的原因。

核心代码逻辑 #

vkBeginCommandBuffer();
// ... bind pipeline and descriptor sets
vkCmdTraceRaysKHR();

        // Prepare current swap chain image as transfer destination
        VkImageMemoryBarrier barrier{};
        barrier.sType = VK_STRUCTURE_TYPE_IMAGE_MEMORY_BARRIER;
        barrier.oldLayout = VK_IMAGE_LAYOUT_UNDEFINED;
        barrier.newLayout = VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL;
        barrier.srcQueueFamilyIndex = VK_QUEUE_FAMILY_IGNORED;
        barrier.dstQueueFamilyIndex = VK_QUEUE_FAMILY_IGNORED;
        barrier.image = swapchainImage;
        barrier.subresourceRange = subresource_range;
        // No need to make anything available
        barrier.srcAccessMask = 0;
        // The result of this transition should be visible for transfers
        barrier.dstAccessMask = VK_ACCESS_TRANSFER_WRITE_BIT | VK_ACCESS_TRANSFER_READ_BIT; 

        vkCmdPipelineBarrier(
            cmdBuffer,
            VK_PIPELINE_STAGE_TOP_OF_PIPE_BIT, // No need to wait for anything
            VK_PIPELINE_STAGE_TRANSFER_BIT,    // Should make transfers wait
            0,
            0, nullptr,
            0, nullptr,
            1, &barrier
        );

        // Prepare ray tracing output image as transfer source
        VkImageMemoryBarrier barrier{};
        barrier.sType = VK_STRUCTURE_TYPE_IMAGE_MEMORY_BARRIER;
        barrier.oldLayout = VK_IMAGE_LAYOUT_GENERAL;
        barrier.newLayout = VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL;
        barrier.srcQueueFamilyIndex = VK_QUEUE_FAMILY_IGNORED;
        barrier.dstQueueFamilyIndex = VK_QUEUE_FAMILY_IGNORED;
        barrier.image = renderImage.image;
        barrier.subresourceRange = subresource_range;
        // The data written by the ray tracing should be made available
        barrier.srcAccessMask = VK_ACCESS_SHADER_WRITE_BIT;
        // The transition and data should be visible for transitions
        barrier.dstAccessMask = VK_ACCESS_TRANSFER_WRITE_BIT | VK_ACCESS_TRANSFER_READ_BIT;

        vkCmdPipelineBarrier(
            cmdBuffer,
            VK_PIPELINE_STAGE_RAY_TRACING_SHADER_BIT_KHR, // Should wait until ray tracing is done
            VK_PIPELINE_STAGE_TRANSFER_BIT,               // Should make transfers wait
            0,
            0, nullptr,
            0, nullptr,
            1, &barrier
        );

vkCmdCopyImage();

        // Transition swap chain image back for presentation
        VkImageMemoryBarrier barrier{};
        barrier.sType = VK_STRUCTURE_TYPE_IMAGE_MEMORY_BARRIER;
        barrier.oldLayout = VK_IMAGE_LAYOUT_TRANSFER_DST_OPTIMAL;
        barrier.newLayout = VK_IMAGE_LAYOUT_PRESENT_SRC_KHR;
        barrier.srcQueueFamilyIndex = VK_QUEUE_FAMILY_IGNORED;
        barrier.dstQueueFamilyIndex = VK_QUEUE_FAMILY_IGNORED;
        barrier.image = swapchainImage;
        barrier.subresourceRange = subresource_range;
        // The effects of the transfer should be made available
        barrier.srcAccessMask = VK_ACCESS_TRANSFER_WRITE_BIT;
        // The effects of the transfer should be made visible for swapchain presentation
        barrier.dstAccessMask = VK_ACCESS_COLOR_ATTACHMENT_READ_BIT;

        vkCmdPipelineBarrier(
            cmdBuffer,
            VK_PIPELINE_STAGE_TRANSFER_BIT,      // Wait for transfers
            VK_PIPELINE_STAGE_ALL_COMMANDS_BIT,  // Block all commands after this barrier
            0,
            0, nullptr,
            0, nullptr,
            1, &barrier
        );

        // Transition ray tracing output image back to general layout
        VkImageMemoryBarrier barrier{};
        barrier.sType = VK_STRUCTURE_TYPE_IMAGE_MEMORY_BARRIER;
        barrier.oldLayout = VK_IMAGE_LAYOUT_TRANSFER_SRC_OPTIMAL;
        barrier.newLayout = VK_IMAGE_LAYOUT_GENERAL;
        barrier.srcQueueFamilyIndex = VK_QUEUE_FAMILY_IGNORED;
        barrier.dstQueueFamilyIndex = VK_QUEUE_FAMILY_IGNORED;
        barrier.image = renderImage.image;
        barrier.subresourceRange = subresource_range;
        // The effects of the transfer should be made available (possibly unnecessary?)
        barrier.srcAccessMask = VK_ACCESS_TRANSFER_READ_BIT;
        // (possibly unnecessary?)
        barrier.dstAccessMask = VK_ACCESS_MEMORY_WRITE_BIT;

        vkCmdPipelineBarrier(
            cmdBuffer,
            VK_PIPELINE_STAGE_TRANSFER_BIT,      // Wait for transfers
            VK_PIPELINE_STAGE_ALL_COMMANDS_BIT,  // Block all commands after this barrier
            0,
            0, nullptr,
            0, nullptr,
            1, &barrier
        );

队列提交时使用两个信号量：一个等待由vkAcquireNextImageKHR触发的信号量，等待阶段设为VK_PIPELINE_STAGE_RAY_TRACING_SHADER_BIT_KHR；另一个信号量用于vkQueuePresentKHR的等待。

阶段与访问掩码的合理性分析 #

1. 交换链图像初始布局转换的问题 #

第一个屏障中，把交换链图像的oldLayout设为VK_IMAGE_LAYOUT_UNDEFINED是错误的。调用vkAcquireNextImageKHR后，交换链图像的布局默认是VK_IMAGE_LAYOUT_PRESENT_SRC_KHR（除非创建交换链时指定了其他初始布局）。用UNDEFINED会忽略图像之前的展示状态，导致验证层报错。正确的设置应为：

• oldLayout设为VK_IMAGE_LAYOUT_PRESENT_SRC_KHR
• srcAccessMask设为VK_ACCESS_MEMORY_READ_BIT（对应展示操作的读取访问）
• srcStageMask设为VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BIT（等待上一帧的展示操作完全结束）

2. 光线追踪输出图像的转换屏障 #

这个屏障的设置整体合理，但可优化：

• dstAccessMask只需保留VK_ACCESS_TRANSFER_READ_BIT即可，因为后续vkCmdCopyImage是读取该图像作为源，不需要TRANSFER_WRITE权限。

3. 交换链图像转展示布局的屏障 #

这里的dstAccessMask和dstStageMask设置不够精准：

• 展示操作对应的访问是VK_ACCESS_MEMORY_READ_BIT，而非VK_ACCESS_COLOR_ATTACHMENT_READ_BIT
• dstStageMask应该设为VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BIT（对应后续的展示操作阶段），VK_PIPELINE_STAGE_ALL_COMMANDS_BIT范围太广，会不必要阻塞后续命令，虽功能正常但效率偏低。

4. 光线追踪图像转回GENERAL布局的屏障 #

可以简化设置：

• dstAccessMask设为0即可，因为转回GENERAL布局后，后续光线追踪Shader的写操作会由对应的屏障处理，无需提前指定
• dstStageMask设为VK_PIPELINE_STAGE_RAY_TRACING_SHADER_BIT_KHR更精准，避免阻塞无关命令

信号量等待阶段的问题 #

将vkAcquireNextImageKHR的等待阶段设为VK_PIPELINE_STAGE_RAY_TRACING_SHADER_BIT_KHR时，会导致交换链图像的上一帧展示操作还未完成，光线追踪就开始执行，和图像转换操作冲突，引发布局未定义的错误。而设为VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BIT时，会等待队列中所有之前的操作（包括展示操作）完全结束，确保图像处于稳定的PRESENT_SRC_KHR布局，后续的转换操作就能正确执行，因此不会触发异常。

内容的提问来源于stack exchange，提问作者Radosław Rzeczkowski