Add missing sparse VUs to VkImageCreateInfo

This commit is contained in:
Petr Kraus 2018-03-10 01:07:49 +01:00
parent ce60b9c887
commit b7b1952cc2

View File

@ -805,6 +805,9 @@ endif::VK_VERSION_1_1,VK_KHR_maintenance1[]
If the <<features-features-sparseBinding,sparse bindings>> feature is
not enabled, pname:flags must: not contain
ename:VK_IMAGE_CREATE_SPARSE_BINDING_BIT
* If the <<features-features-sparseResidencyAliased,sparse aliased
residency>> feature is not enabled, pname:flags must: not contain
ename:VK_IMAGE_CREATE_SPARSE_ALIASED_BIT
* [[VUID-VkImageCreateInfo-imageType-00970]]
If pname:imageType is ename:VK_IMAGE_TYPE_1D, pname:flags must: not
contain ename:VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT
@ -914,6 +917,10 @@ endif::VK_VERSION_1_1,VK_KHR_maintenance1[]
If pname:flags contains ename:VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT or
ename:VK_IMAGE_CREATE_SPARSE_ALIASED_BIT, it must: also contain
ename:VK_IMAGE_CREATE_SPARSE_BINDING_BIT
* If any of the bits ename:VK_IMAGE_CREATE_SPARSE_BINDING_BIT,
ename:VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT, or
ename:VK_IMAGE_CREATE_SPARSE_ALIASED_BIT are set,
ename:VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT must: not also be set
ifdef::VK_VERSION_1_1[]
* If the protected memory feature is not enabled, pname:flags must: not
contain ename:VK_IMAGE_CREATE_PROTECTED_BIT.
@ -1351,11 +1358,6 @@ ifdef::VK_EXT_sample_locations[]
attachment.
endif::VK_EXT_sample_locations[]
If any of the bits ename:VK_IMAGE_CREATE_SPARSE_BINDING_BIT,
ename:VK_IMAGE_CREATE_SPARSE_RESIDENCY_BIT, or
ename:VK_IMAGE_CREATE_SPARSE_ALIASED_BIT are set,
ename:VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT must: not also be set.
See <<sparsememory-sparseresourcefeatures,Sparse Resource Features>> and
<<sparsememory-physicalfeatures,Sparse Physical Device Features>> for more
details.