KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
CreateImage does not currently respect `VK_IMAGE_CREATE_EXTENDED_USAGE_BIT_KHR`
Nobody has claimed this yet.
- #3724 by @sfricke-samsung — closed without merging
- Dominant language
- C++
- Stars
- 1k
- Forks
- 505
- Avg merge
- 11h 25m
- Merged PRs (30d)
- 229
Description
As originally reported here, creating an image with VK_IMAGE_CREATE_EXTENDED_USAGE_BIT_KHR can trigger a false error.
Valid Usage ID
VUID-VkImageCreateInfo-imageCreateMaxMipLevels-02251 and similar VUIDs that take image format + usage into account, as only the format + usage matters at image view creation time when extended usage is used (more or less).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the original report linked in the issue and the Vulkan valid usage IDs VUID-VkImageCreateInfo-imageCreateMaxMipLevels-02251 and similar VUIDs. Trace CreateImage validation and determine how VK_IMAGE_CREATE_EXTENDED_USAGE_BIT_KHR should affect format-and-usage checks; done means the false error no longer occurs for this flag and relevant validation coverage passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100