#vulkan #vulkan-graphics #ash #graphics #3d #api-bindings


Simplification of core Vulkan synchronization mechanisms such as pipeline barriers and events

7 releases

0.1.6 Jul 14, 2019
0.1.5 Jun 1, 2019
0.1.4 Dec 7, 2018
0.1.2 Nov 17, 2018
0.1.0 Aug 26, 2018

#351 in Graphics APIs

Download history 7/week @ 2024-02-19 16/week @ 2024-02-26 12/week @ 2024-03-04 10/week @ 2024-03-11 7/week @ 2024-03-18 114/week @ 2024-04-01

133 downloads per month


660 lines


vk-sync on travis-ci.com vk-sync on appveyor.com Latest version Documentation

Simplified Vulkan synchronization logic, written in rust.


In an effort to make Vulkan synchronization more accessible, this library provides an efficient simplification of core synchronization mechanisms such as pipeline barriers and events.

Rather than the complex maze of enums and bit flags in Vulkan - many combinations of which are invalid or nonsensical - this library collapses this to a much shorter list of ~40 distinct usage types, and a couple of options for handling image layouts.

Additionally, these usage types provide an easier mapping to other graphics APIs like DirectX 12.

Use of other synchronization mechanisms such as semaphores, fences and render passes are not addressed in this library at present.


There are a number of Vulkan ffi bindings available, and I do plan to support the most common bindings, but for now this library only implements support for ash. Please add other bindings you need via a pull-request; I would happily accept it.


Despite the fact that this library is fairly simple, it expresses 99% of what you'd actually ever want to do in practice. Adding the missing expressiveness would result in increased complexity which does not seem worth the trade-off. If you have any pattern you need express, please file an issue!

Here's a list of known things you cannot express:

  • Execution only dependencies cannot be expressed. These are occasionally useful in conjunction with semaphores, or when trying to be clever with scheduling - but their usage is both limited and fairly tricky to get right anyway.

  • Depth/Stencil Input Attachments can be read in a shader using either ImageLayout::ShaderReadOnlyOptimal or ImageLayout::DepthStencilReadOnlyOptimal - this library always uses ImageLayout::DepthStencilReadOnlyOptimal. It is possible (though highly unlikely) when aliasing images that this results in unnecessary transitions.


Add this to your Cargo.toml:

vk-sync = "0.1.6"

and this to your crate root:

extern crate vk_sync;


Licensed under either of

at your option.


This library is heavily based on work by Tobias Hector (https://github.com/Tobski/simple_vulkan_synchronization)


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Code of Conduct

Contribution to the vk-sync crate is organized under the terms of the Contributor Covenant, the maintainer of vk-sync, @gwihlidal, promises to intervene to uphold that code of conduct.


~32K SLoC