From 12b0de281de898af9c8ee42ff818fe36e46a7151 Mon Sep 17 00:00:00 2001
From: baldurk <baldurk@baldurk.org>
Date: Sun, 30 Aug 2015 17:31:35 +0200
Subject: [PATCH] make sure to fully initialis eserialised image memory barrier
 structs

---
 renderdoc/driver/vulkan/vk_manager.cpp | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/renderdoc/driver/vulkan/vk_manager.cpp b/renderdoc/driver/vulkan/vk_manager.cpp
index 291094298..3b4151a13 100644
--- a/renderdoc/driver/vulkan/vk_manager.cpp
+++ b/renderdoc/driver/vulkan/vk_manager.cpp
@@ -228,6 +228,17 @@ void VulkanResourceManager::SerialiseImageStates(Serialiser *m_pSerialiser, map<
 			if(m_State < WRITING && srcit != states.end())
 			{
 				VkImageMemoryBarrier t;
+				t.sType = VK_STRUCTURE_TYPE_IMAGE_MEMORY_BARRIER;
+				t.pNext = NULL;
+				// VKTODO losing information? what are in/out mask and queues
+				// if input/output mask are just same as memory barriers, for
+				// the memory bound to the image, it's maybe fine as we don't need
+				// those for this purpose, they were replayed when the non-collapsed
+				// barrier happened.
+				t.inputMask = 0;
+				t.outputMask = 0;
+				t.srcQueueFamilyIndex = 0;
+				t.destQueueFamilyIndex = 0;
 				t.image = (VkImage)GetCurrentResource(liveid).handle;
 				t.oldLayout = VK_IMAGE_LAYOUT_UNDEFINED;
 				t.newLayout = state.state;