From 03de856edf997106d08167dcbf321500631e01bb Mon Sep 17 00:00:00 2001
From: baldurk <baldurk@baldurk.org>
Date: Wed, 21 Jan 2026 11:42:32 +0000
Subject: [PATCH] Track CPU-based image layout transitions while idle. Closes
 #3778

* Similar to proper image transitions we must always track the state of images,
  even if we only serialise the calls during active capturing.
---
 renderdoc/driver/vulkan/wrappers/vk_sync_funcs.cpp | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/renderdoc/driver/vulkan/wrappers/vk_sync_funcs.cpp b/renderdoc/driver/vulkan/wrappers/vk_sync_funcs.cpp
index ede0df5df..ae6630627 100644
--- a/renderdoc/driver/vulkan/wrappers/vk_sync_funcs.cpp
+++ b/renderdoc/driver/vulkan/wrappers/vk_sync_funcs.cpp
@@ -1572,7 +1572,10 @@ VkResult WrappedVulkan::vkTransitionImageLayout(VkDevice device, uint32_t transi
     Serialise_vkTransitionImageLayout(ser, device, transitionCount, pTransitions);
 
     m_FrameCaptureRecord->AddChunk(scope.Get());
+  }
 
+  if(IsCaptureMode(m_State))
+  {
     for(uint32_t i = 0; i < transitionCount; ++i)
     {
       const VkHostImageLayoutTransitionInfo &transition = pTransitions[i];