summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGeorges Basile Stavracas Neto <georges.stavracas@gmail.com>2023-04-01 15:33:10 -0300
committerGeorges Basile Stavracas Neto <georges.stavracas@gmail.com>2023-04-03 10:59:45 -0300
commit724d07ef8a4a5150640acdc164d933487bbab9c5 (patch)
treec6df3a3f727f194d06f1c70d9da24e6f53e563f2
parenta33ddd54ac8557bf49b204573c3088f748d3e61a (diff)
downloadgtk+-724d07ef8a4a5150640acdc164d933487bbab9c5.tar.gz
gsk/vulkan/image: Use UNDEFINED for initial layout
When creating an image using gsk_vulkan_image_new_for_framebuffer(), it passes VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL. However, this is a mistake. The spec demands that the initial layout must be either VK_IMAGE_LAYOUT_UNDEFINED or VK_IMAGE_LAYOUT_PREINITIALIZED. Apparently this was an oversight from commit b97fb751469, since the commit message even documents that, and all other calls pass either VK_IMAGE_LAYOUT_UNDEFINED or VK_IMAGE_LAYOUT_PREINITIALIZED. Create framebuffer images using VK_IMAGE_LAYOUT_UNDEFINED, which is what was originally expected.
-rw-r--r--gsk/vulkan/gskvulkanimage.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gsk/vulkan/gskvulkanimage.c b/gsk/vulkan/gskvulkanimage.c
index b6d4eee548..102d5281bc 100644
--- a/gsk/vulkan/gskvulkanimage.c
+++ b/gsk/vulkan/gskvulkanimage.c
@@ -575,7 +575,7 @@ gsk_vulkan_image_new_for_framebuffer (GdkVulkanContext *context,
height,
VK_IMAGE_TILING_OPTIMAL,
VK_IMAGE_USAGE_TRANSFER_SRC_BIT | VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT,
- VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL,
+ VK_IMAGE_LAYOUT_UNDEFINED,
VK_ACCESS_COLOR_ATTACHMENT_WRITE_BIT,
VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT);