You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Validation Error: [ VUID-VkImageCreateInfo-pNext-06722 ] | MessageID = 0x1a04b807 | vkCreateImage(): pCreateInfo->pNext<VkImageFormatListCreateInfo>.pViewFormats[0] (VK_FORMAT_R8_UNORM) and VkImageCreateInfo::format (VK_FORMAT_G8_B8R8_2PLANE_420_UNORM) are not compatible. The Vulkan spec states: If a VkImageFormatListCreateInfo structure was included in the pNext chain and VkImageFormatListCreateInfo::viewFormatCount is not zero, then each format in VkImageFormatListCreateInfo::pViewFormats must either be compatible with the format as described in the compatibility table or, if flags contains VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT, be an uncompressed format that is size-compatible with format
Looking at this table, I don't think it's valid to pass the plane formats as view_formats. The plane functionality is similar to the existing aspect functionality used for combined depth-stencil textures where the format specified for the view is the format of one of the planes/aspects.
I think it would have made sense to add variants for the planes to TextureAspect rather than the new plane param.
CI is now running into after a mesa update:
Looking at this table, I don't think it's valid to pass the plane formats as
view_formats
. The plane functionality is similar to the existing aspect functionality used for combined depth-stencil textures where the format specified for the view is the format of one of the planes/aspects.I think it would have made sense to add variants for the planes to
TextureAspect
rather than the newplane
param.Originally posted by @teoxoy in #4573 (comment)
The text was updated successfully, but these errors were encountered: