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
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.
The text was updated successfully, but these errors were encountered:
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 singleVkMemoryRequirements
in that case, but rather one for each plane, indicated with aVkImagePlaneMemoryRequirementsInfo
struct when requesting the requirements. Which of theVkMemoryRequirements
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.The text was updated successfully, but these errors were encountered: