VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_BIT and VUID-vkGetDeviceMemoryOpaqueCaptureAddress-pInfo-10727 contradict each other

[romigrou]

The documentation for VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_BIT states the following:

VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_BIT specifies that the memory can be attached to a buffer object created with the VK_BUFFER_USAGE_SHADER_DEVICE_ADDRESS_BIT bit set in usage, and that the memory handle can be used to retrieve an opaque address via vkGetDeviceMemoryOpaqueCaptureAddress.

Which, if I understand correctly, means that by setting just the VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_BIT flag I should be able to call vkGetDeviceMemoryOpaqueCaptureAddress() on a VkDeviceMemory.

However, VUID-vkGetDeviceMemoryOpaqueCaptureAddress-pInfo-10727 tells me that I must have set VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_CAPTURE_REPLAY_BIT in order to be able to call vkGetDeviceMemoryOpaqueCaptureAddress():

VUID-vkGetDeviceMemoryOpaqueCaptureAddress-pInfo-10727
pInfo->memory must have been allocated using the VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_CAPTURE_REPLAY_BIT flag