diff --git a/docs/html/group__group__alloc.html b/docs/html/group__group__alloc.html index 8d89dcb..1a823f1 100644 --- a/docs/html/group__group__alloc.html +++ b/docs/html/group__group__alloc.html @@ -713,7 +713,7 @@ Functions
VMA_MEMORY_USAGE_AUTO*
value, you must use this flag to be able to map the allocation. Otherwise, mapping is incorrect.HOST_VISIBLE
. This includes allocations created in Custom memory pools.Declares that mapped memory can be read, written, and accessed in random order, so a HOST_CACHED
memory type is required.
Declares that mapped memory can be read, written, and accessed in random order, so a HOST_CACHED
memory type is preferred.
Together with VMA_ALLOCATION_CREATE_HOST_ACCESS_SEQUENTIAL_WRITE_BIT or VMA_ALLOCATION_CREATE_HOST_ACCESS_RANDOM_BIT, it says that despite request for host access, a not-HOST_VISIBLE
memory type can be selected if it may improve performance.
By using this flag, you declare that you will check if the allocation ended up in a HOST_VISIBLE
memory type (e.g. using vmaGetAllocationMemoryProperties()) and if not, you will create some "staging" buffer and issue an explicit transfer to write/read your data. To prepare for this possibility, don't forget to add appropriate flags like VK_BUFFER_USAGE_TRANSFER_DST_BIT
, VK_BUFFER_USAGE_TRANSFER_SRC_BIT
to the parameters of created buffer or image.