Home / Forums / Vulkan Pipeline Barriers, Memory Hazards & Layout Transitions

UnreliableCode Community

Developer Research, Reverse Engineering & Coding Community

Subforums Leaderboard Log In to Post
Discussion

Vulkan Pipeline Barriers, Memory Hazards & Layout Transitions

DirectXRay
DirectX 12 / Vulkan Dev
MEMBER
Rep: 240
Join Date: Feb 2023
Posts: 31
Thanks: 60
4y ago · Jul 19, 2022 7:03 PM
#1
Vulkan requires explicit pipeline barriers (vkCmdPipelineBarrier) to synchronize write-after-read (WAR) and write-after-write (WAW) hazards.
DirectXRay · DirectX 12 & Vulkan Command Lists
The following users thanked DirectXRay for this post:
VectorByte
Graphics & DirectX Dev
VIP
Rep: 420
Join Date: Aug 2022
Posts: 39
Thanks: 115
4y ago · Jul 19, 2022 9:20 PM
#2
Transitioning image layouts from COLOR_ATTACHMENT_OPTIMAL to SHADER_READ_ONLY_OPTIMAL requires proper stage masks.
VectorByte | DirectX 11/12 Hooking & ImGui Overlays
Quote
Math is the language of game engines.
PEHeader
PE Format & Linker Tech
VIP
Rep: 350
Join Date: Jun 2023
Posts: 35
Thanks: 95
4y ago · Jul 20, 2022 3:20 AM
#3
Using the Vulkan Validation Layers (VK_LAYER_KHRONOS_validation) catches 99% of synchronization bugs during development.
PEHeader | IMAGE_NT_HEADERS & Section Parsing