Skip to content

Document the synchronization2 requirement for pipelineBarrier2 #477

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gpx1000 wants to merge 1 commit into from
Closed

Document the synchronization2 requirement for pipelineBarrier2 #477

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions en/03_Drawing_a_triangle/03_Drawing/01_Command_buffers.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -208,6 +208,12 @@ void transition_image_layout(

This function will be used to transition the image layout before and after rendering.

NOTE: `vk::raii::CommandBuffer::pipelineBarrier2`, along with the `vk::ImageMemoryBarrier2` and
`vk::DependencyInfo` structures used above, are part of the `synchronization2` functionality
promoted to core in Vulkan 1.3. This requires enabling the `synchronization2` feature via
`vk::PhysicalDeviceVulkan13Features` when creating the logical device, the same way we enabled
`dynamicRendering`. Without it, `pipelineBarrier2` will fail validation.

== Starting dynamic rendering

With dynamic rendering, we don't need to create a render pass or framebuffers. Instead, we specify the attachments directly when we begin rendering:
Expand Down
Loading