KhronosGroup / KhronosGroup/Vulkan-Docs
Clarification regarding externalMemoryFeatures returned by vkGetPhysicalDeviceExternalBufferProperties
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
In a similar vein to the guarantees provided by [vkGetDeviceBufferMemoryRequirements](https://docs.vulkan.org/spec/latest/chapters/resources.html#:~:text=The%20memoryTypeBits%20member%20is,values%20of%20flags.), if `usage1` and `usage2` of type VkBufferUsageFlags are such that the bits set in `usage2` are a subset of the bits set in `usage1`, and they are passed as `pExternalBufferInfo->flags` to vkGetPhysicalDeviceExternalBufferProperties, assuming all else is identical, is it guaranteed that the `pExternalBufferProperties->externalMemoryProperties.externalMemoryFeatures` of the latter is a superset of the former? In other words, can an application assume that adding `usage` bits will not suddenly make it possible to back a buffer with exportable/importable external memory (where it couldn't be before)?
Contributor guide
Assessment
This issue has not been assessed yet.