diff --git a/docs/html/choosing_memory_type.html b/docs/html/choosing_memory_type.html index c0e6daa..b713e77 100644 --- a/docs/html/choosing_memory_type.html +++ b/docs/html/choosing_memory_type.html @@ -70,7 +70,7 @@ $(function() {
When using 3. or 4., the library internally queries Vulkan for memory types supported for that buffer or image (function vkGetBufferMemoryRequirements()
) and uses only one of these types.
You can query for information about specific allocation using function vmaGetAllocationInfo(). It fill structure VmaAllocationInfo.
You can dump internal state of the allocator to a string in JSON format using function vmaBuildStatsString(). The result is guaranteed to be correct JSON. It uses ANSI encoding. Any strings provided by user (see Allocation names) are copied as-is and properly escaped for JSON, so if they use UTF-8, ISO-8859-2 or any other encoding, this JSON string can be treted as using this encoding. It must be freed using function vmaFreeStatsString().
-The format of this string is not part of official documentation of the library, but it will not change in backward-incompatible way without increasing library major version number and mention in changelog.
-The string contains all the data that can be obtained using vmaCalculateStats(). It can also contain detailed map of allocated memory blocks and their regions - free and occupied by allocations. This allows e.g. to visualize the memory or assess fragmentation.
+You can dump internal state of the allocator to a string in JSON format using function vmaBuildStatsString(). The result is guaranteed to be correct JSON. It uses ANSI encoding. Any strings provided by user (see Allocation names) are copied as-is and properly escaped for JSON, so if they use UTF-8, ISO-8859-2 or any other encoding, this JSON string can be treated as using this encoding. It must be freed using function vmaFreeStatsString().
+The format of this JSON string is not part of official documentation of the library, but it will not change in backward-incompatible way without increasing library major version number and appropriate mention in changelog.
+The JSON string contains all the data that can be obtained using vmaCalculateStats(). It can also contain detailed map of allocated memory blocks and their regions - free and occupied by allocations. This allows e.g. to visualize the memory or assess fragmentation.
Function similar to vmaAllocateMemoryForBuffer().
+ + + +VkResult vmaBindBufferMemory | +( | +VmaAllocator | +allocator, | +
+ | + | VmaAllocation | +allocation, | +
+ | + | VkBuffer | +buffer | +
+ | ) | ++ |
Binds buffer to allocation.
+Binds specified buffer to region of memory represented by specified allocation. Gets VkDeviceMemory
handle and offset from the allocation. If you want to create a buffer, allocate memory for it and bind them together separately, you should use this function for binding instead of standard vkBindBufferMemory()
, because it ensures proper synchronization so that when a VkDeviceMemory
object is used by multiple allocations, calls to vkBind*Memory()
or vkMapMemory()
won't happen from multiple threads simultaneously (which is illegal in Vulkan).
It is recommended to use function vmaCreateBuffer() instead of this one.
+ +VkResult vmaBindImageMemory | +( | +VmaAllocator | +allocator, | +
+ | + | VmaAllocation | +allocation, | +
+ | + | VkImage | +image | +
+ | ) | ++ |
Binds image to allocation.
+Binds specified image to region of memory represented by specified allocation. Gets VkDeviceMemory
handle and offset from the allocation. If you want to create an image, allocate memory for it and bind them together separately, you should use this function for binding instead of standard vkBindImageMemory()
, because it ensures proper synchronization so that when a VkDeviceMemory
object is used by multiple allocations, calls to vkBind*Memory()
or vkMapMemory()
won't happen from multiple threads simultaneously (which is illegal in Vulkan).
It is recommended to use function vmaCreateImage() instead of this one.
+