KhronosGroup / KhronosGroup/Vulkan-Docs
Sparse binding with disjoint multi-planar images
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
Several parts of the sparse binding spec reference the fields of `VkMemoryRequirements`, but when you're doing an opaque image bind on a disjoint image with more than one plane, this gets complicated. There is no single `VkMemoryRequirements` in that case, but rather one for each plane, indicated with a `VkImagePlaneMemoryRequirementsInfo` struct when requesting the requirements. Which of the `VkMemoryRequirements` should be followed when doing sparse binds? Note that opaque image binds have no way to specify which plane you're binding for, since the image layout is meant to be opaque to the user to begin with.
Contributor guide
Assessment
This issue has not been assessed yet.