vkCopyMemoryToMicromapEXT
To copy host accessible memory to a micromap, call:
VkResult vkCopyMemoryToMicromapEXT(
VkDevice device,
VkDeferredOperationKHR deferredOperation,
const VkCopyMemoryToMicromapInfoEXT* pInfo);
device
is the device which ownspInfo→dst
.deferredOperation
is an optional VkDeferredOperationKHR to request deferral for this command.pInfo
is a pointer to a VkCopyMemoryToMicromapInfoEXT structure defining the copy operation.
This command fulfills the same task as vkCmdCopyMemoryToMicromapEXT but is executed by the host.
This command can accept micromaps produced by either vkCmdCopyMicromapToMemoryEXT or vkCopyMicromapToMemoryEXT.
Valid Usage
VUID-vkCopyMemoryToMicromapEXT-deferredOperation-03678
Any previous deferred operation that was associated with
deferredOperation
must be complete
VUID-vkCopyMemoryToMicromapEXT-pInfo-07563
pInfo→src.hostAddress
must be a valid host pointer
VUID-vkCopyMemoryToMicromapEXT-pInfo-07564
pInfo→src.hostAddress
must be aligned to 16 bytes
VUID-vkCopyMemoryToMicromapEXT-buffer-07565
The buffer
used to create pInfo→dst
must be bound to
host-visible device memory
VUID-vkCopyMemoryToMicromapEXT-micromapHostCommands-07566
The VkPhysicalDeviceOpacityMicromapFeaturesEXT
::micromapHostCommands
feature must be enabled
VUID-vkCopyMemoryToMicromapEXT-buffer-07567
The buffer
used to create pInfo→dst
must be bound to
memory that was not allocated with multiple instances
Valid Usage (Implicit)
VUID-vkCopyMemoryToMicromapEXT-device-parameter
device
must be a valid VkDevice handle
VUID-vkCopyMemoryToMicromapEXT-deferredOperation-parameter
If deferredOperation
is not VK_NULL_HANDLE, deferredOperation
must be a valid VkDeferredOperationKHR handle
VUID-vkCopyMemoryToMicromapEXT-pInfo-parameter
pInfo
must be a valid pointer to a valid VkCopyMemoryToMicromapInfoEXT structure
VUID-vkCopyMemoryToMicromapEXT-deferredOperation-parent
If deferredOperation
is a valid handle, it must have been created, allocated, or retrieved from device