layers: Hack to remove incorrect implicit VU
VUID-VkFramebufferCreateInfo-pAttachments-parameter should've been
removed for VK_KHR_imageless_framebuffer, and replaced with explicit
VU instead - but this hasn't yet happened.
In order to ship validation for this functionality in the next SDK,
the VU has temporarily been hardcoded out in the generator script.
Added in an explicit check temporarily to ensure that
Most of these changes (other than the change to
parameter_validation_generator.py) will remain intact after the spec is
updated. The script change won't cause any issues after it the spec is
updated either, so it can be reverted in slow time.
diff --git a/layers/generated/parameter_validation.cpp b/layers/generated/parameter_validation.cpp
index 35184be..7953aa5 100644
--- a/layers/generated/parameter_validation.cpp
+++ b/layers/generated/parameter_validation.cpp
@@ -3640,8 +3640,6 @@
skip |= validate_flags("vkCreateFramebuffer", "pCreateInfo->flags", "VkFramebufferCreateFlagBits", AllVkFramebufferCreateFlagBits, pCreateInfo->flags, false, false, "VUID-VkFramebufferCreateInfo-flags-parameter");
skip |= validate_required_handle("vkCreateFramebuffer", "pCreateInfo->renderPass", pCreateInfo->renderPass);
-
- skip |= validate_array("vkCreateFramebuffer", "pCreateInfo->attachmentCount", "pCreateInfo->pAttachments", pCreateInfo->attachmentCount, &pCreateInfo->pAttachments, false, true, kVUIDUndefined, "VUID-VkFramebufferCreateInfo-pAttachments-parameter");
}
if (pAllocator != NULL)
{
@@ -3664,6 +3662,7 @@
}
}
skip |= validate_required_pointer("vkCreateFramebuffer", "pFramebuffer", pFramebuffer, "VUID-vkCreateFramebuffer-pFramebuffer-parameter");
+ skip |= manual_PreCallValidateCreateFramebuffer(device, pCreateInfo, pAllocator, pFramebuffer);
return skip;
}