I have a little misunderstanding for the pre presentation barrier presented on https://www.khronos.org/registry/vulkan/specs/1.0-wsi_extensions/xhtml/vkspec.html#_examples_2
The third example in swapchain’s example.
They use a
vkCmdPipelineBarrier( cmdBuffers[i], VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT, VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT, VK_FALSE, 1, &acquireImageBarrier)
They put the same stage, does it mean that it doesn’t matter (that seems obvious for me, but I prefer to be sure ^^) and only layout and access changing matters?
Triangle example from Sascha Willem use :
But according to me, we don’t have to wait again the end of commands because (in my case) I used a fence just before it ^^. But maybe it means that we have to wait the end of prior presentation (just after thinking at that, the Sascha Willem’s case fits better ^^).