h&UJ      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ Safe-Inferred( "%&()*0125;<=?FMVulkanMemoryAllocatorVmaVirtualAllocationInfo;Parameters of an existing virtual allocation, returned by .VulkanMemoryAllocatorOffset of the allocation.(Offset at which the allocation was made.VulkanMemoryAllocatorSize of the allocation.Same value as passed in $VmaVirtualAllocationCreateInfo::size.VulkanMemoryAllocator.Custom pointer associated with the allocation.Same value as passed in )VmaVirtualAllocationCreateInfo::pUserData or to .VulkanMemoryAllocatorVmaVirtualAllocationCreateInfo:Parameters of created virtual allocation to be passed to .VulkanMemoryAllocatorSize of the allocation.Cannot be zero.VulkanMemoryAllocator/Required alignment of the allocation. Optional.Must be power of two. Special value 0 has the same meaning as 1 - means no special alignment is required, so allocation can start at any offset. VulkanMemoryAllocatorUse combination of . VulkanMemoryAllocator>Custom pointer to be associated with the allocation. Optional.It can be any value and can be used for user-defined purposes. It can be fetched or changed later. VulkanMemoryAllocatorVmaVirtualBlockCreateInfoParameters of created  object to be passed to . VulkanMemoryAllocator Total size of the virtual block.Sizes can be expressed in bytes or any units you want as long as you are consistent in using them. For example, if you allocate from some array of structures, 1 can mean single instance of entire structure.VulkanMemoryAllocatorUse combination of .VulkanMemoryAllocator1Custom CPU memory allocation callbacks. Optional.Optional, can be null. When specified, they will be used for all CPU-side memory allocations.VulkanMemoryAllocatorVmaDefragmentationStats=Statistics returned for defragmentation process in function .VulkanMemoryAllocatorTotal number of bytes that have been copied while moving allocations to different places.VulkanMemoryAllocatorTotal number of bytes that have been released to the system by freeing empty VkDeviceMemory objects.VulkanMemoryAllocator?Number of allocations that have been moved to different places.VulkanMemoryAllocatorNumber of empty VkDeviceMemory0 objects that have been released to the system.VulkanMemoryAllocatorVmaDefragmentationPassMoveInfo1Parameters for incremental defragmentation steps.To be used with function .VulkanMemoryAllocatorNumber of elements in the pMoves array.VulkanMemoryAllocatorArray of moves to be performed by the user in the current defragmentation pass.Pointer to an array of  moveCount% elements, owned by VMA, created in , destroyed in .For each element, you should: Create a new buffer/image in the place pointed by VmaDefragmentationMove::dstMemory + VmaDefragmentationMove::dstOffset.Copy data from the %VmaDefragmentationMove::srcAllocation e.g. using vkCmdCopyBuffer, vkCmdCopyImage.7Make sure these commands finished executing on the GPU.Destroy the old buffer/image.:Only then you can finish defragmentation pass by calling . After this call, the allocation will point to the new place in memory.Alternatively, if you cannot move specific allocation, you can set !VmaDefragmentationMove::operation to .Alternatively, if you decide you want to completely remove the allocation: Destroy its buffer/image.Set !VmaDefragmentationMove::operation to . Then, after  the allocation will be freed.VulkanMemoryAllocatorVmaDefragmentationMoveHave to return true for breaking current defragmentation pass.&VulkanMemoryAllocatorOptional data to pass to custom callback for stopping pass of defragmentation.)VulkanMemoryAllocatorVmaAllocationInfoParameters of 0 objects, that can be retrieved using function .+VulkanMemoryAllocator:Memory type index that this allocation was allocated from.It never changes.,VulkanMemoryAllocatorHandle to Vulkan memory object.9Same memory object can be shared by multiple allocations.3It can change after the allocation is moved during Defragmentation.-VulkanMemoryAllocator Offset in VkDeviceMemory8 object to the beginning of this allocation, in bytes. (deviceMemory, offset)# pair is unique to this allocation.You usually don't need to use this offset. If you create a buffer or an image together with the allocation using e.g. function , , functions that operate on these resources refer to the beginning of the buffer or image, not entire device memory block. Functions like ,  also refer to the beginning of the allocation and apply this offset automatically.3It can change after the allocation is moved during Defragmentation..VulkanMemoryAllocator"Size of this allocation, in bytes.It never changes.NoteAllocation size returned in this variable may be greater than the size requested for the resource e.g. as VkBufferCreateInfo::size. Whole size of the allocation is accessible for operations on memory e.g. using a pointer after mapping with -, but operations on the resource e.g. using vkCmdCopyBuffer. must be limited to the size of the resource./VulkanMemoryAllocator;Pointer to the beginning of this allocation as mapped data.+If the allocation hasn't been mapped using  and hasn't been created with  flag, this value is null.It can change after call to , ;. It can also change after the allocation is moved during Defragmentation.0VulkanMemoryAllocator3Custom general-purpose pointer that was passed as "VmaAllocationCreateInfo::pUserData or set using .It can change after call to  for this allocation.1VulkanMemoryAllocator)Custom allocation name that was set with .It can change after call to  for this allocation.1Another way to set custom name is to pass it in "VmaAllocationCreateInfo::pUserData with additional flag  set [DEPRECATED].2VulkanMemoryAllocatorVmaPoolCreateInfoDescribes parameter of created .4VulkanMemoryAllocator4Vulkan memory type index to allocate this pool from.5VulkanMemoryAllocatorUse combination of .6VulkanMemoryAllocatorSize of a single VkDeviceMemory block to be allocated as part of this pool, in bytes. Optional.Specify nonzero to set explicit, constant size of memory blocks used by this pool.Leave 0 to use default and let the library manage block sizes automatically. Sizes of particular blocks may vary. In this case, the pool will also support dedicated allocations.7VulkanMemoryAllocatorMinimum number of blocks to be always allocated in this pool, even if they stay empty.Set to 0 to have no preallocated blocks and allow the pool be completely empty.8VulkanMemoryAllocatorMaximum number of blocks that can be allocated in this pool. Optional."Set to 0 to use default, which is SIZE_MAX, which means no limit.Set to same value as  VmaPoolCreateInfo::minBlockCount to have fixed amount of memory allocated throughout whole lifetime of this pool.9VulkanMemoryAllocatorA floating-point value between 0 and 1, indicating the priority of the allocations in this pool relative to other memory allocations.It is used only when ' flag was used during creation of the . object. Otherwise, this variable is ignored.:VulkanMemoryAllocatorAdditional minimum alignment to be used for all allocations created from this pool. Can be 0.Leave 0 (default) not to impose any additional alignment. If not 0, it must be a power of two. It can be useful in cases where alignment returned by Vulkan by functions like vkGetBufferMemoryRequirements5 is not enough, e.g. when doing interop with OpenGL.;VulkanMemoryAllocator Additional pNext chain to be attached to VkMemoryAllocateInfo8 used for every allocation made by this pool. Optional.7Optional, can be null. If not null, it must point to a pNext. chain of structures that can be attached to VkMemoryAllocateInfo5. It can be useful for special needs such as adding VkExportMemoryAllocateInfoKHR. Structures pointed by this member must remain alive and unchanged for the whole lifetime of the custom pool.(Please note that some structures, e.g. VkMemoryPriorityAllocateInfoEXT,  VkMemoryDedicatedAllocateInfoKHR, can be attached automatically by this library when using other, more convenient of its features.<VulkanMemoryAllocatorVmaAllocationCreateInfoParameters of new .To be used with functions like , , and many others.>VulkanMemoryAllocatorUse  enum.?VulkanMemoryAllocatorIntended usage of memory.You can leave 6 if you specify memory requirements in other way. If pool% is not null, this member is ignored.@VulkanMemoryAllocatorFlags that must be set in a Memory Type chosen for an allocation.Estimated amount of memory available to the program, in bytes.Fetched from system using VK_EXT_memory_budget extension if enabled.4It might be different (most probably smaller) than VkMemoryHeap::size[heapIndex] due to factors external to the program, decided by the operating system. Difference budget - usage is the amount of additional memory that can probably be allocated without problems. Exceeding the budget may result in various problems.KVulkanMemoryAllocatorVmaTotalStatisticsP  memoryType [VK_MAX_MEMORY_TYPES]P  memoryHeap [VK_MAX_MEMORY_HEAPS]P totalGeneral statistics from current state of the Allocator - total memory usage across all memory heaps and types.These are slower to calculate. Use for debugging purposes. See function . memoryHeapmemoryHeap VmaTotalStatistics VmaTotalStatistics memoryHeap VmaDetailedStatistics VmaTotalStatistics::memoryHeap[VK_MAX_MEMORY_HEAPS] memoryTypememoryType VmaTotalStatistics VmaTotalStatistics memoryType VmaDetailedStatistics VmaTotalStatistics::memoryType[VK_MAX_MEMORY_TYPES]PVulkanMemoryAllocatorVmaDetailedStatisticsMore detailed statistics than X.These are slower to calculate. Use for debugging purposes. See functions: , .Previous version of the statistics API provided averages, but they have been removed because they can be easily calculated as: VkDeviceSize allocationSizeAvg = detailedStats.statistics.allocationBytes / detailedStats.statistics.allocationCount; VkDeviceSize unusedBytes = detailedStats.statistics.blockBytes - detailedStats.statistics.allocationBytes; VkDeviceSize unusedRangeSizeAvg = unusedBytes / detailedStats.unusedRangeCount;RVulkanMemoryAllocatorBasic statistics.SVulkanMemoryAllocator4Number of free ranges of memory between allocations.TVulkanMemoryAllocatorSmallest allocation size.  VK_WHOLE_SIZE if there are 0 allocations.UVulkanMemoryAllocator6Largest allocation size. 0 if there are 0 allocations.VVulkanMemoryAllocatorSmallest empty range size.  VK_WHOLE_SIZE if there are 0 empty ranges.WVulkanMemoryAllocator8Largest empty range size. 0 if there are 0 empty ranges.XVulkanMemoryAllocator VmaStatisticsCalculated statistics of memory usage e.g. in a specific memory type, heap, custom pool, or total.,These are fast to calculate. See functions: , .ZVulkanMemoryAllocator Number of VkDeviceMemory* objects - Vulkan memory blocks allocated.[VulkanMemoryAllocator Number of  objects allocated.Dedicated allocations have their own blocks, so each one adds 1 to allocationCount as well as  blockCount.\VulkanMemoryAllocatorNumber of bytes allocated in VkDeviceMemory blocks.NoteTo avoid confusion, please be aware that what Vulkan calls an "allocation" - a whole VkDeviceMemory object (e.g. as in 0VkPhysicalDeviceLimits::maxMemoryAllocationCount>) is called a "block" in VMA, while VMA calls "allocation" a  object that represents a memory region sub-allocated from such block, usually for a single buffer or image.]VulkanMemoryAllocator&Total number of bytes occupied by all  objects.Always less or equal than  blockBytes. Difference (blockBytes - allocationBytes) is the amount of memory allocated from Vulkan but unused by any .^VulkanMemoryAllocatorVmaAllocatorInfoInformation about existing  object.`VulkanMemoryAllocator!Handle to Vulkan instance object.3This is the same value as has been passed through  VmaAllocatorCreateInfo::instance.aVulkanMemoryAllocator(Handle to Vulkan physical device object.3This is the same value as has been passed through &VmaAllocatorCreateInfo::physicalDevice.bVulkanMemoryAllocatorHandle to Vulkan device object.3This is the same value as has been passed through VmaAllocatorCreateInfo::device.cVulkanMemoryAllocatorVmaAllocatorCreateInfo)Description of a Allocator to be created.eVulkanMemoryAllocator!Flags for created allocator. Use  enum.fVulkanMemoryAllocatorVulkan physical device.It must be valid throughout whole lifetime of created allocator.gVulkanMemoryAllocatorVulkan device.It must be valid throughout whole lifetime of created allocator.hVulkanMemoryAllocatorPreferred size of a single VkDeviceMemory; block to be allocated from large heaps > 1 GiB. Optional.4Set to 0 to use default, which is currently 256 MiB.iVulkanMemoryAllocator1Custom CPU memory allocation callbacks. Optional.Optional, can be null. When specified, will also be used for all CPU-side memory allocations.jVulkanMemoryAllocatorInformative callbacks for vkAllocateMemory,  vkFreeMemory . Optional.Optional, can be null.kVulkanMemoryAllocatorEither null or a pointer to an array of limits on maximum number of bytes that can be allocated out of particular Vulkan memory heap.2If not NULL, it must be a pointer to an array of 1VkPhysicalDeviceMemoryProperties::memoryHeapCount elements, defining limit on maximum number of bytes that can be allocated out of particular Vulkan memory heap.$Any of the elements may be equal to  VK_WHOLE_SIZE, which means no limit on that heap. This is also the default in case of pHeapSizeLimit = NULL.'If there is a limit defined for a heap:If user tries to allocate more memory from that heap using this allocator, the allocation fails with VK_ERROR_OUT_OF_DEVICE_MEMORY.8If the limit is smaller than heap size reported in VkMemoryHeap::size, the value of this limit will be reported instead when using .Warning! Using this feature may not be equivalent to installing a GPU with smaller amount of memory, because graphics driver doesn't necessary fail new allocations with VK_ERROR_OUT_OF_DEVICE_MEMORY result when memory capacity is exceeded. It may return success and just silently migrate some device memory blocks to system RAM. This driver behavior can also be controlled using VK_AMD_memory_overallocation_behavior extension.lVulkanMemoryAllocator*Pointers to Vulkan functions. Can be null.For details see Pointers to Vulkan functions.mVulkanMemoryAllocator!Handle to Vulkan instance object.Starting from version 3.0.0 this member is no longer optional, it must be set!nVulkanMemoryAllocatorOptional. The highest version of Vulkan that the application is designed to use.5It must be a value in the format as created by macro VK_MAKE_VERSION or a constant like: VK_API_VERSION_1_1, VK_API_VERSION_1_0. The patch version number specified is ignored. Only the major and minor versions are considered. It must be less or equal (preferably equal) to value as passed to vkCreateInstance as VkApplicationInfo::apiVersion. Only versions 1.0, 1.1, 1.2, 1.3 are supported by the current implementation. Leaving it initialized to zero is equivalent to VK_API_VERSION_1_0.oVulkanMemoryAllocatorEither null or a pointer to an array of external memory handle types for each Vulkan memory type.2If not NULL, it must be a pointer to an array of 1VkPhysicalDeviceMemoryProperties::memoryTypeCount elements, defining external memory handle types of particular Vulkan memory type, to be passed using VkExportMemoryAllocateInfoKHR.?Any of the elements may be equal to 0, which means not to use VkExportMemoryAllocateInfoKHR; on this memory type. This is also the default in case of pTypeExternalMemoryHandleTypes = NULL.pVulkanMemoryAllocatorVmaVulkanFunctionsPointers to some Vulkan functions - a subset used by the library.Used in (VmaAllocatorCreateInfo::pVulkanFunctions.rVulkanMemoryAllocator1Required when using VMA_DYNAMIC_VULKAN_FUNCTIONS.sVulkanMemoryAllocator1Required when using VMA_DYNAMIC_VULKAN_FUNCTIONS.VulkanMemoryAllocatorFetch "vkGetBufferMemoryRequirements2" on Vulkan >= 1.1, fetch "vkGetBufferMemoryRequirements2KHR" when using VK_KHR_dedicated_allocation extension.VulkanMemoryAllocatorFetch "vkGetImageMemoryRequirements2" on Vulkan >= 1.1, fetch "vkGetImageMemoryRequirements2KHR" when using VK_KHR_dedicated_allocation extension.VulkanMemoryAllocatorFetch "vkBindBufferMemory2" on Vulkan >= 1.1, fetch "vkBindBufferMemory2KHR" when using VK_KHR_bind_memory2 extension.VulkanMemoryAllocatorFetch "vkBindImageMemory2" on Vulkan >= 1.1, fetch "vkBindImageMemory2KHR" when using VK_KHR_bind_memory2 extension.VulkanMemoryAllocatorFetch from "vkGetDeviceBufferMemoryRequirements" on Vulkan >= 1.3, but you can also fetch it from "vkGetDeviceBufferMemoryRequirementsKHR" if you enabled extension VK_KHR_maintenance4.VulkanMemoryAllocatorFetch from "vkGetDeviceImageMemoryRequirements" on Vulkan >= 1.3, but you can also fetch it from "vkGetDeviceImageMemoryRequirementsKHR" if you enabled extension VK_KHR_maintenance4.VulkanMemoryAllocatorVmaDeviceMemoryCallbacks0Set of callbacks that the library will call for vkAllocateMemory and  vkFreeMemory.Provided for informative purpose, e.g. to gather statistics about number of allocations or total amount of memory allocated in Vulkan.Used in .VmaAllocatorCreateInfo::pDeviceMemoryCallbacks.VulkanMemoryAllocatorOptional, can be null.VulkanMemoryAllocatorOptional, can be null.VulkanMemoryAllocatorOptional, can be null.VulkanMemoryAllocatorVmaVirtualBlockHandle to a virtual block object that allows to use core allocation algorithm without allocating any real GPU memory.Fill in   structure and use  to create it. Use  to destroy it. For more information, see documentation chapter Virtual allocator.This object is not thread-safe - should not be used from multiple threads simultaneously, must be synchronized externally.VulkanMemoryAllocatorVmaVirtualAllocation0Represents single memory allocation done inside .Use it as a unique identifier to virtual allocation within the single block. Use value VK_NULL_HANDLE( to represent a null/invalid allocation.VulkanMemoryAllocatorVmaDefragmentationContextAn opaque object that represents started defragmentation process.Fill structure  and call function  to create it. Call function  to destroy it.VulkanMemoryAllocator VmaAllocation$Represents single memory allocation.$It may be either dedicated block of VkDeviceMemory or a specific region of a bigger block of this type plus unique offset.There are multiple ways to create such object. You need to fill structure <3. For more information see /Choosing memory type/.Although the library provides convenience functions that create Vulkan buffer or image, allocate memory for it and bind them together, binding of the allocation to a buffer or an image is out of scope of the allocation itself. Allocation object can exist without buffer/image bound, binding can be done manually by the user, and destruction of it can be done independently of destruction of the allocation.The object also remembers its size and some other information. To retrieve this information, use function ! and inspect returned structure ).VulkanMemoryAllocatorVmaPoolRepresents custom memory pool.Fill structure 2 and call function  to create it. Call function  to destroy it.For more information see Custom memory pools.VulkanMemoryAllocator VmaAllocator3Represents main object of this library initialized.Fill structure c and call function  to create it. Call function  to destroy it.=It is recommended to create just one object of this type per VkDevice object, right after Vulkan is initialized and keep it alive until before Vulkan device is destroyed.VulkanMemoryAllocatorFlags to be passed as %VmaVirtualAllocationCreateInfo::flags.VulkanMemoryAllocatorFlags to be passed as  VmaVirtualBlockCreateInfo::flags.VulkanMemoryAllocatorOperation performed on single defragmentation move. See structure .VulkanMemoryAllocatorFlags to be passed as VmaDefragmentationInfo::flags.VulkanMemoryAllocatorFlags to be passed as VmaPoolCreateInfo::flags.VulkanMemoryAllocatorFlags to be passed as VmaAllocationCreateInfo::flags.VulkanMemoryAllocator'Intended usage of the allocated memory.VulkanMemoryAllocatorFlags for created .VulkanMemoryAllocatorA bit mask to extract only STRATEGY bits from entire set of flags.These strategy flags are binary compatible with equivalent flags in .VulkanMemoryAllocatorAllocation strategy that chooses always the lowest offset in available space. This is not the most efficient strategy but achieves highly packed data.VulkanMemoryAllocator;Allocation strategy that tries to minimize allocation time.VulkanMemoryAllocator8Allocation strategy that tries to minimize memory usage.VulkanMemoryAllocatorAllocation will be created from upper stack in a double stack pool.;This flag is only allowed for virtual blocks created with  flag.VulkanMemoryAllocatorBit mask to extract only  ALGORITHM bits from entire set of flags.VulkanMemoryAllocatorEnables alternative, linear allocation algorithm in this virtual block.Specify this flag to enable linear allocation algorithm, which always creates new allocations after last one and doesn't reuse space from allocations freed in between. It trades memory consumption for simplified algorithm and data structure, which has better performance and uses less memory for metadata.By using this flag, you can achieve behavior of free-at-once, stack, ring buffer, and double stack. For details, see documentation chapter Linear allocation algorithm.VulkanMemoryAllocatorSet this value if you decide to abandon the allocation and you destroyed the buffer/image. New place reserved at dstTmpAllocation will be freed, along with  srcAllocation, which will be destroyed.VulkanMemoryAllocatorSet this value if you cannot move the allocation. New place reserved at dstTmpAllocation will be freed.  srcAllocation will remain unchanged.VulkanMemoryAllocator#Buffer/image has been recreated at dstTmpAllocation>, data has been copied, old buffer/image has been destroyed.  srcAllocation should be changed to point to the new place. This is the default value set by .VulkanMemoryAllocatorA bit mask to extract only  ALGORITHM bits from entire set of flags.VulkanMemoryAllocatorUse the most roboust algorithm at the cost of time to compute and number of copies to make. Only available when bufferImageGranularity is greater than 1, since it aims to reduce alignment issues between different types of resources. Otherwise falls back to same behavior as .VulkanMemoryAllocatorBit mask to extract only  ALGORITHM bits from entire set of flags.VulkanMemoryAllocator>Enables alternative, linear allocation algorithm in this pool.Specify this flag to enable linear allocation algorithm, which always creates new allocations after last one and doesn't reuse space from allocations freed in between. It trades memory consumption for simplified algorithm and data structure, which has better performance and uses less memory for metadata.By using this flag, you can achieve behavior of free-at-once, stack, ring buffer, and double stack. For details, see documentation chapter Linear allocation algorithm.VulkanMemoryAllocatorUse this flag if you always allocate only buffers and linear images or only optimal images out of this pool and so Buffer-Image Granularity can be ignored.&This is an optional optimization flag.If you always allocate using , , , then you don't need to use it because allocator knows exact type of your allocations so it can handle Buffer-Image Granularity in the optimal way.If you also allocate using  or , exact type of such allocations is not known, so allocator must be conservative in handling Buffer-Image Granularity, which can lead to suboptimal allocation (wasted memory). In that case, if you can make sure you always allocate only buffers and linear images or only optimal images out of this pool, use this flag to make allocator disregard Buffer-Image Granularity and so make allocations faster and more optimal.VulkanMemoryAllocatorA bit mask to extract only STRATEGY bits from entire set of flags.VulkanMemoryAllocator Alias to .VulkanMemoryAllocator Alias to .VulkanMemoryAllocatorAllocation strategy that chooses always the lowest offset in available space. This is not the most efficient strategy but achieves highly packed data. Used internally by defragmentation, not recommended in typical usage.VulkanMemoryAllocatorAllocation strategy that chooses first suitable free range for the allocation - not necessarily in terms of the smallest offset but the one that is easiest and fastest to find to minimize allocation time, possibly at the expense of allocation quality.VulkanMemoryAllocatorAllocation strategy that chooses smallest possible free range for the allocation to minimize memory usage and fragmentation, possibly at the expense of allocation time.VulkanMemoryAllocatorTogether with  or 7, 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 ) 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.VulkanMemoryAllocator2Requests possibility to map the allocation (using  or ). If you use  or other VMA_MEMORY_USAGE_AUTO* value, you must use this flag to be able to map the allocation. Otherwise, mapping is incorrect.If you use other value of , this flag is ignored and mapping is always possible in memory types that are  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.VulkanMemoryAllocator2Requests possibility to map the allocation (using  or ). If you use  or other VMA_MEMORY_USAGE_AUTO* value, you must use this flag to be able to map the allocation. Otherwise, mapping is incorrect.If you use other value of , this flag is ignored and mapping is always possible in memory types that are  HOST_VISIBLE,. This includes allocations created in Custom memory pools.Declares that mapped memory will only be written sequentially, e.g. using memcpy() or a loop writing number-by-number, never read or accessed randomly, so a memory type can be selected that is uncached and write-combined.WarningViolating this declaration may work correctly, but will likely be very slow. Watch out for implicit reads introduced by doing e.g. pMappedData[i] += x;3 Better prepare your data in a local variable and memcpy()& it to the mapped pointer all at once.VulkanMemoryAllocatorSet this flag if the allocated memory will have aliasing resources.&Usage of this flag prevents supplying  VkMemoryDedicatedAllocateInfoKHR when  is specified. Otherwise created dedicated memory will not be suitable for aliasing resources, resulting in Vulkan Validation Layer errors.VulkanMemoryAllocatorCreate allocation only if additional device memory required for it, if any, won't exceed memory budget. Otherwise return VK_ERROR_OUT_OF_DEVICE_MEMORY.VulkanMemoryAllocatorCreate both buffer/image and allocation, but don't bind them together. It is useful when you want to bind yourself to do some more advanced binding, e.g. using some extensions. The flag is meaningful only with functions that bind by default: , . Otherwise it is ignored.If you want to make sure the new buffer/image is not tied to the new memory allocation through  VkMemoryDedicatedAllocateInfoKHR structure in case the allocation ends up in its own memory block, use also flag .VulkanMemoryAllocatorAllocation will be created from upper stack in a double stack pool.9This flag is only allowed for custom pools created with  flag.VulkanMemoryAllocator Deprecated5Preserved for backward compatibility. Consider using  instead.Set this flag to treat "VmaAllocationCreateInfo::pUserData as pointer to a null-terminated string. Instead of copying pointer value, a local copy of the string is made and stored in allocation's pName. The string is automatically freed together with the allocation. It is also used in .VulkanMemoryAllocatorSet this flag to use a memory that will be persistently mapped and retrieve pointer to it.3Pointer to mapped memory will be returned through VmaAllocationInfo::pMappedData.It is valid to use this flag for allocation made from memory type that is not  HOST_VISIBLE. This flag is then ignored and memory is not mapped. This is useful if you need an allocation that is efficient to use on GPU ( DEVICE_LOCAL) and still want to map it directly if possible on platforms that support it (e.g. Intel GPU).VulkanMemoryAllocator4Set this flag to only try to allocate from existing VkDeviceMemory) blocks and never create new such block.If new allocation cannot be placed in any of the existing blocks, allocation fails with VK_ERROR_OUT_OF_DEVICE_MEMORY error.You should not use  and & at the same time. It makes no sense.VulkanMemoryAllocatorSet this flag if the allocation should have its own memory block.Use it for special, big resources, like fullscreen images used as attachments.VulkanMemoryAllocatorSelects best memory type automatically with preference for CPU (host) memory.When using this flag, if you want to map the allocation (using  or $), you must pass one of the flags:  or  in VmaAllocationCreateInfo::flags.>It can be used only with functions that let the library know VkBufferCreateInfo or VkImageCreateInfo, e.g. , , , 3 and not with generic memory allocation functions.VulkanMemoryAllocatorSelects best memory type automatically with preference for GPU (device) memory.When using this flag, if you want to map the allocation (using  or $), you must pass one of the flags:  or  in VmaAllocationCreateInfo::flags.>It can be used only with functions that let the library know VkBufferCreateInfo or VkImageCreateInfo, e.g. , , , 3 and not with generic memory allocation functions.VulkanMemoryAllocatorSelects best memory type automatically. This flag is recommended for most common use cases.When using this flag, if you want to map the allocation (using  or $), you must pass one of the flags:  or  in VmaAllocationCreateInfo::flags.>It can be used only with functions that let the library know VkBufferCreateInfo or VkImageCreateInfo, e.g. , , , 3 and not with generic memory allocation functions.VulkanMemoryAllocator$Lazily allocated GPU memory having 'VK_MEMORY_PROPERTY_LAZILY_ALLOCATED_BIT. Exists mostly on mobile platforms. Using it on desktop PC or other GPUs with no such memory type present will fail the allocation.Usage: Memory for transient attachment images (color attachments, depth attachments etc.), created with 'VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT.Allocations with this usage are always created as dedicated - it implies .VulkanMemoryAllocator Deprecated=Obsolete, preserved for backward compatibility. Prefers not #VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT.VulkanMemoryAllocator DeprecatedrequiredFlags.Matches intended usage.Has as many flags from pAllocationCreateInfo->preferredFlags as possible.ReturnsReturns VK_ERROR_FEATURE_NOT_PRESENT if not found. Receiving such result from this function or any other allocating function probably means that your device doesn't support any memory type with requested features for the specific type of resource you want to use it for. Please check parameters of your resource, like image layout (OPTIMAL versus LINEAR) or mip level count.VulkanMemoryAllocator=Helps to find memoryTypeIndex, given VkBufferCreateInfo and <.8It can be useful e.g. to determine value to be used as "VmaPoolCreateInfo::memoryTypeIndex. It internally creates a temporary, dummy buffer that never has memory bound.VulkanMemoryAllocator - corruption detection has been performed and succeeded.VK_ERROR_UNKNOWN - corruption detection has been performed and found memory corruptions around one of the allocations.  VMA_ASSERT! is also fired in that case.Other value: Error returned by Vulkan, e.g. memory mapping failure.VulkanMemoryAllocator Retrieves name of a custom pool.After the call ppName is either null or points to an internally-owned null-terminated string containing name of the pool that was previously set. The pointer becomes invalid when the pool is destroyed or its name is changed using .VulkanMemoryAllocatorSets name of a custom pool.pName can be either null or pointer to a null-terminated string with new name for the pool. Function makes internal copy of the string, so it can be changed or freed immediately after this call.VulkanMemoryAllocator"General purpose memory allocation. Parameters allocatorpVkMemoryRequirements pCreateInfoout pAllocationHandle to allocated memory.out pAllocationInfo Optional. Information about allocated memory. It can be later fetched using function .!You should free the memory using  or .It is recommended to use , , ,  instead whenever possible.VulkanMemoryAllocator=A convenience wrapper to make a compatible pair of calls to  and To ensure that  is always called: pass  (or the allocate function from your favourite resource management library) as the last argument. To just extract the pair pass (,) as the last argument.VulkanMemoryAllocatorGeneral purpose memory allocation for multiple allocation objects at once. Parameters allocatorAllocator object.pVkMemoryRequirements(Memory requirements for each allocation. pCreateInfo(Creation parameters for each allocation.allocationCountNumber of allocations to make.out  pAllocations Pointer to array that will be filled with handles to created allocations.out pAllocationInfo Optional. Pointer to array that will be filled with parameters of created allocations.!You should free the memory using  or .Word "pages" is just a suggestion to use this function to allocate pieces of memory needed for sparse binding. It is just a general purpose allocation function able to make multiple allocations at once. It may be internally optimized to be more efficient than calling  allocationCount times.All allocations are made using same parameters. All of them are created out of the same memory pool and type. If any allocation fails, all allocations already made within this function call are also freed, so that when returned result is not  VK_SUCCESS,  pAllocation' array is always entirely filled with VK_NULL_HANDLE.VulkanMemoryAllocator=A convenience wrapper to make a compatible pair of calls to  and To ensure that  is always called: pass  (or the allocate function from your favourite resource management library) as the last argument. To just extract the pair pass (,) as the last argument.VulkanMemoryAllocator$Allocates memory suitable for given VkBuffer. Parameters allocatorbuffer pCreateInfoout pAllocationHandle to allocated memory.out pAllocationInfo Optional. Information about allocated memory. It can be later fetched using function .It only creates ). To bind the memory to the buffer, use .This is a special-purpose function. In most cases you should use .#You must free the allocation using  when no longer needed.VulkanMemoryAllocator=A convenience wrapper to make a compatible pair of calls to  and To ensure that  is always called: pass  (or the allocate function from your favourite resource management library) as the last argument. To just extract the pair pass (,) as the last argument.VulkanMemoryAllocator$Allocates memory suitable for given VkImage. Parameters allocatorimage pCreateInfoout pAllocationHandle to allocated memory.out pAllocationInfo Optional. Information about allocated memory. It can be later fetched using function .It only creates ). To bind the memory to the buffer, use .This is a special-purpose function. In most cases you should use .#You must free the allocation using  when no longer needed.VulkanMemoryAllocator=A convenience wrapper to make a compatible pair of calls to  and To ensure that  is always called: pass  (or the allocate function from your favourite resource management library) as the last argument. To just extract the pair pass (,) as the last argument.VulkanMemoryAllocator(Frees memory previously allocated using , , or .Passing VK_NULL_HANDLE as  allocation/ is valid. Such function call is just skipped.VulkanMemoryAllocator/Frees memory and destroys multiple allocations.Word "pages" is just a suggestion to use this function to free pieces of memory used for sparse binding. It is just a general purpose function to free memory and destroy allocations made using e.g. ,  and other functions. It may be internally optimized to be more efficient than calling  allocationCount times.Allocations in  pAllocations: array can come from any memory pools and types. Passing VK_NULL_HANDLE as elements of  pAllocations0 array is valid. Such entries are just skipped.VulkanMemoryAllocator7Returns current information about specified allocation.8Current parameters of given allocation are returned in pAllocationInfo.Although this function doesn't lock any mutex, so it should be quite efficient, you should avoid calling it too often. You can retrieve same )8 structure while creating your resource, from function , . You can remember it if you are sure parameters don't change (e.g. due to defragmentation).VulkanMemoryAllocator0Sets pUserData in given allocation to new value.The value of pointer  pUserData is copied to allocation's  pUserData. It is opaque, so you can use it however you want - e.g. as a pointer, ordinal number or some handle to you own data.VulkanMemoryAllocator,Sets pName in given allocation to new value.pName must be either null, or pointer to a null-terminated string. The function makes local copy of the string and sets it as allocation's pName. String passed as pName doesn't need to be valid for whole lifetime of the allocation - you can free it after this call. String previously pointed by allocation's pName is freed from memory.VulkanMemoryAllocator?Given an allocation, returns Property Flags of its memory type.This is just a convenience function. Same information can be obtained using  + .VulkanMemoryAllocatorMaps memory represented by given allocation and returns pointer to it.Maps memory represented by given allocation to make it accessible to CPU code. When succeeded, *ppData0 contains pointer to first byte of this memory.Warning&If the allocation is part of a bigger VkDeviceMemory block, returned pointer is correctly offsetted to the beginning of region assigned to this particular allocation. Unlike the result of  vkMapMemory, it points to the allocation, not to the beginning of the whole block. You should not add VmaAllocationInfo::offset to it!Mapping is internally reference-counted and synchronized, so despite raw Vulkan function  vkMapMemory()& cannot be used to map same block of VkDeviceMemory multiple times simultaneously, it is safe to call this function on allocations assigned to the same memory block. Actual Vulkan memory will be mapped on first mapping and unmapped on last unmapping.)If the function succeeded, you must call  to unmap the allocation when mapping is no longer needed or before freeing the allocation, at the latest.It also safe to call this function multiple times on the same allocation. You must call % same number of times as you called .It is also safe to call this function on allocation created with  flag. Its memory stays mapped all the time. You must still call % same number of times as you called . You must not call  additional time to free the "0-th" mapping made automatically due to  flag.This function fails when used on allocation made in memory type that is not  HOST_VISIBLE.This function doesn't automatically flush or invalidate caches. If the allocation is made from a memory types that is not  HOST_COHERENT, you also need to use  / ', as required by Vulkan specification.VulkanMemoryAllocator - corruption detection has been performed and succeeded.VK_ERROR_UNKNOWN - corruption detection has been performed and found memory corruptions around one of the allocations.  VMA_ASSERT! is also fired in that case.Other value: Error returned by Vulkan, e.g. memory mapping failure.VulkanMemoryAllocatorBegins defragmentation process. Parameters allocatorAllocator object. pInfo 4Structure filled with parameters of defragmentation.out  pContext &Context object that must be passed to  to finish defragmentation.Returns VK_SUCCESS if defragmentation can begin.VK_ERROR_FEATURE_NOT_PRESENT% if defragmentation is not supported.For more information about defragmentation, see documentation chapter: Defragmentation.VulkanMemoryAllocator=A convenience wrapper to make a compatible pair of calls to  and To ensure that  is always called: pass  (or the allocate function from your favourite resource management library) as the last argument. To just extract the pair pass (,) as the last argument.VulkanMemoryAllocatorEnds defragmentation process. Parameters allocatorAllocator object. context (Context object that has been created by .out pStats 4Optional stats for the defragmentation. Can be null.8Use this function to finish defragmentation started by .VulkanMemoryAllocator#Starts single defragmentation pass. Parameters allocatorAllocator object. context (Context object that has been created by .out pPassInfo&Computed information for current pass.Returns VK_SUCCESS? if no more moves are possible. Then you can omit call to & and simply end whole defragmentation. VK_INCOMPLETE( if there are pending moves returned in  pPassInfo&. You need to perform them, call 1, and then preferably try another pass with .VulkanMemoryAllocator>This function will call the supplied action between calls to  and  Note that  is *not* called if an exception is thrown by the inner action.VulkanMemoryAllocator!Ends single defragmentation pass. Parameters allocatorAllocator object.context (Context object that has been created by . pPassInfo 0Computed information for current pass filled by  and possibly modified by you.Returns  VK_SUCCESS" if no more moves are possible or  VK_INCOMPLETE( if more defragmentations are possible.Ends incremental defragmentation pass and commits all defragmentation moves from  pPassInfo. After this call:Allocations at pPassInfo[i].srcAllocation that had pPassInfo[i].operation ==  (which is the default) will be pointing to the new destination place.Allocation at pPassInfo[i].srcAllocation that had pPassInfo[i].operation ==  will be freed.If no more moves are possible you can end whole defragmentation.VulkanMemoryAllocatorBinds 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 VkDeviceMemory3 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  instead of this one.VulkanMemoryAllocator6Binds buffer to allocation with additional parameters. Parameters allocator allocationallocationLocalOffset Additional offset to be added while binding, relative to the beginning of the  allocation. Normally it should be 0.bufferpNext (A chain of structures to be attached to VkBindBufferMemoryInfoKHR7 structure used internally. Normally it should be null.This function is similar to ), but it provides additional parameters.If pNext is not null, % object must have been created with  flag or with (VmaAllocatorCreateInfo::vulkanApiVersion >= VK_API_VERSION_1_1. Otherwise the call fails.VulkanMemoryAllocatorBinds 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 VkDeviceMemory3 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  instead of this one.VulkanMemoryAllocator5Binds image to allocation with additional parameters. Parameters allocator allocationallocationLocalOffset Additional offset to be added while binding, relative to the beginning of the  allocation. Normally it should be 0.imagepNext (A chain of structures to be attached to VkBindImageMemoryInfoKHR7 structure used internally. Normally it should be null.This function is similar to ), but it provides additional parameters.If pNext is not null, % object must have been created with  flag or with (VmaAllocatorCreateInfo::vulkanApiVersion >= VK_API_VERSION_1_1. Otherwise the call fails.VulkanMemoryAllocatorCreates a new VkBuffer$, allocates and binds memory for it. Parameters allocatorpBufferCreateInfopAllocationCreateInfooutpBufferBuffer that was created.out pAllocationAllocation that was created.out pAllocationInfo Optional. Information about allocated memory. It can be later fetched using function .This function automatically: Creates buffer.$Allocates appropriate memory for it.!Binds the buffer with the memory.If any of these operations fail, buffer and allocation are not created, returned value is negative error code, *pBuffer and  *pAllocation are null.If the function succeeded, you must destroy both buffer and allocation when you no longer need them using either convenience function  or separately, using vkDestroyBuffer() and .If  flag was used, VK_KHR_dedicated_allocation extension is used internally to query driver whether it requires or prefers the new buffer to have dedicated allocation. If yes, and if dedicated allocation is possible ( is not used), it creates dedicated allocation for this buffer, just like when using .NoteThis function creates a new VkBuffer. Sub-allocation of parts of one large buffer, although recommended as a good practice, is out of scope of this library and could be implemented by the user as a higher-level logic on top of VMA.VulkanMemoryAllocator=A convenience wrapper to make a compatible pair of calls to  and To ensure that  is always called: pass  (or the allocate function from your favourite resource management library) as the last argument. To just extract the pair pass (,) as the last argument.VulkanMemoryAllocator3Creates a buffer with additional minimum alignment. Similar to $ but provides additional parameter  minAlignment which allows to specify custom, minimum alignment to be used when placing the buffer inside a larger memory block, which may be needed e.g. for interop with OpenGL.VulkanMemoryAllocatorCreates a new VkBuffer&, binds already created memory for it. Parameters allocator  allocation Allocation that provides memory to be used for binding new buffer to it.pBufferCreateInfooutpBufferBuffer that was created.This function automatically: Creates buffer.*Binds the buffer with the supplied memory.If any of these operations fail, buffer is not created, returned value is negative error code and *pBuffer is null.If the function succeeded, you must destroy the buffer when you no longer need it using vkDestroyBuffer(). If you want to also destroy the corresponding allocation you can use convenience function .NoteThere is a new version of this function augmented with parameter allocationLocalOffset - see .VulkanMemoryAllocatorCreates a new VkBuffer&, binds already created memory for it. Parameters allocator  allocation Allocation that provides memory to be used for binding new buffer to it. allocationLocalOffset Additional offset to be added while binding, relative to the beginning of the allocation. Normally it should be 0.pBufferCreateInfooutpBufferBuffer that was created.This function automatically: Creates buffer.*Binds the buffer with the supplied memory.If any of these operations fail, buffer is not created, returned value is negative error code and *pBuffer is null.If the function succeeded, you must destroy the buffer when you no longer need it using vkDestroyBuffer(). If you want to also destroy the corresponding allocation you can use convenience function .NoteThis is a new version of the function augmented with parameter allocationLocalOffset.VulkanMemoryAllocator2Destroys Vulkan buffer and frees allocated memory.2This is just a convenience function equivalent to: vkDestroyBuffer(device, buffer, allocationCallbacks); vmaFreeMemory(allocator, allocation);4It is safe to pass null as buffer and/or allocation.VulkanMemoryAllocatorFunction similar to .VulkanMemoryAllocator=A convenience wrapper to make a compatible pair of calls to  and To ensure that  is always called: pass  (or the allocate function from your favourite resource management library) as the last argument. To just extract the pair pass (,) as the last argument.VulkanMemoryAllocatorFunction similar to  but for images.VulkanMemoryAllocatorFunction similar to  but for images.VulkanMemoryAllocator1Destroys Vulkan image and frees allocated memory.2This is just a convenience function equivalent to: vkDestroyImage(device, image, allocationCallbacks); vmaFreeMemory(allocator, allocation);3It is safe to pass null as image and/or allocation.VulkanMemoryAllocator Creates new  object. Parameters pCreateInfoParameters for creation.out pVirtualBlock !Returned virtual block object or VMA_NULL if creation failed.VulkanMemoryAllocator=A convenience wrapper to make a compatible pair of calls to  and To ensure that  is always called: pass  (or the allocate function from your favourite resource management library) as the last argument. To just extract the pair pass (,) as the last argument.VulkanMemoryAllocator Destroys  object.Please note that you should consciously handle virtual allocations that could remain unfreed in the block. You should either free them individually using  or call  if you are sure this is what you want. If you do neither, an assert is called.If you keep pointers to some additional metadata associated with your virtual allocations in their  pUserData, don't forget to free them.VulkanMemoryAllocatorReturns true of the  is empty - contains 0 virtual allocations and has all its space available for new allocations.VulkanMemoryAllocatorReturns information about a specific virtual allocation within a virtual block, like its size and  pUserData pointer.VulkanMemoryAllocator.Allocates new virtual allocation inside given .If the allocation fails due to not enough free space available, VK_ERROR_OUT_OF_DEVICE_MEMORY is returned (despite the function doesn't ever allocate actual GPU memory).  pAllocation is then set to VK_NULL_HANDLE and pOffset, if not null, it set to  UINT64_MAX. Parameters virtualBlock Virtual block pCreateInfoParameters for the allocationout pAllocation%Returned handle of the new allocationout pOffset =Returned offset of the new allocation. Optional, can be null.VulkanMemoryAllocator=A convenience wrapper to make a compatible pair of calls to  and To ensure that  is always called: pass  (or the allocate function from your favourite resource management library) as the last argument. To just extract the pair pass (,) as the last argument.VulkanMemoryAllocator&Frees virtual allocation inside given .)It is correct to call this function with allocation == VK_NULL_HANDLE - it does nothing.VulkanMemoryAllocator+Frees all virtual allocations inside given .You must either call this function or free each virtual allocation individually with  before destroying a virtual block. Otherwise, an assert is called.If you keep pointer to some additional metadata associated with your virtual allocation in its  pUserData", don't forget to free it as well.VulkanMemoryAllocatorChanges custom pointer associated with given virtual allocation.VulkanMemoryAllocatorCalculates and returns statistics about virtual allocations and memory usage in given .This function is fast to call. For more detailed statistics, see .VulkanMemoryAllocatorCalculates and returns detailed statistics about virtual allocations and memory usage in given .This function is slow to call. Use for debugging purposes. For less detailed statistics, see .VulkanMemoryAllocatorBuilds and returns a null-terminated string in JSON format with information about given . Parameters virtualBlockVirtual block.out ppStatsStringReturned string. detailedMap Pass VK_FALSE* to only obtain statistics as returned by . Pass VK_TRUE9 to also obtain full list of allocations and free spaces.$Returned string must be freed using .VulkanMemoryAllocatorFrees a string returned by .VulkanMemoryAllocatorBuilds and returns statistics as a null-terminated string in JSON format. Parameters allocatorout ppStatsString Must be freed using  function. detailedMap  "!#$%&'()*.10-+,/23459678:;<=BCD>?@AEFGHIJKLMNOPQRSTUVWXYZ[\]^_ab`cdefghijklmnopqrstuvwxyz{|}~pqrstuvwxyz{|}~cdefghijklmno^_ab`XYZ[\]PQRSTUVWKLMNOFGHIJ<=BCD>?@AE23459678:;)*.10-+,/'( "!#$%&         !"#$%&&'()*+,-../01234567789:;<=>?@@ABCDDEFGHHIJKLMNOOPQRSTTUVWXXYZ[\]^_`abcddefghijklmnopqrstuvwxyz{|}~1VulkanMemoryAllocator-0.11-4xJMC0qaoNKK4NUWakzFb5VulkanMemoryAllocatorControl.ExceptionbracketVirtualAllocationInfo!$sel:offset:VirtualAllocationInfo$sel:size:VirtualAllocationInfo#$sel:userData:VirtualAllocationInfoVirtualAllocationCreateInfo%$sel:size:VirtualAllocationCreateInfo*$sel:alignment:VirtualAllocationCreateInfo&$sel:flags:VirtualAllocationCreateInfo)$sel:userData:VirtualAllocationCreateInfoVirtualBlockCreateInfo $sel:size:VirtualBlockCreateInfo!$sel:flags:VirtualBlockCreateInfo/$sel:allocationCallbacks:VirtualBlockCreateInfoDefragmentationStats$$sel:bytesMoved:DefragmentationStats$$sel:bytesFreed:DefragmentationStats*$sel:allocationsMoved:DefragmentationStats1$sel:deviceMemoryBlocksFreed:DefragmentationStatsDefragmentationPassMoveInfo*$sel:moveCount:DefragmentationPassMoveInfo&$sel:moves:DefragmentationPassMoveInfoDefragmentationMove"$sel:operation:DefragmentationMove&$sel:srcAllocation:DefragmentationMove)$sel:dstTmpAllocation:DefragmentationMoveDefragmentationInfo$sel:flags:DefragmentationInfo$sel:pool:DefragmentationInfo($sel:maxBytesPerPass:DefragmentationInfo.$sel:maxAllocationsPerPass:DefragmentationInfo)$sel:pfnBreakCallback:DefragmentationInfo.$sel:breakCallbackUserData:DefragmentationInfo(PFN_vmaCheckDefragmentationBreakFunction'FN_vmaCheckDefragmentationBreakFunctionAllocationInfo$sel:memoryType:AllocationInfo $sel:deviceMemory:AllocationInfo$sel:offset:AllocationInfo$sel:size:AllocationInfo$sel:mappedData:AllocationInfo$sel:userData:AllocationInfo$sel:name:AllocationInfoPoolCreateInfo#$sel:memoryTypeIndex:PoolCreateInfo$sel:flags:PoolCreateInfo$sel:blockSize:PoolCreateInfo!$sel:minBlockCount:PoolCreateInfo!$sel:maxBlockCount:PoolCreateInfo$sel:priority:PoolCreateInfo*$sel:minAllocationAlignment:PoolCreateInfo&$sel:memoryAllocateNext:PoolCreateInfoAllocationCreateInfo$sel:flags:AllocationCreateInfo$sel:usage:AllocationCreateInfo'$sel:requiredFlags:AllocationCreateInfo($sel:preferredFlags:AllocationCreateInfo($sel:memoryTypeBits:AllocationCreateInfo$sel:pool:AllocationCreateInfo"$sel:userData:AllocationCreateInfo"$sel:priority:AllocationCreateInfoBudget$sel:statistics:Budget$sel:usage:Budget$sel:budget:BudgetTotalStatistics$sel:memoryType:TotalStatistics$sel:memoryHeap:TotalStatistics$sel:total:TotalStatisticsDetailedStatistics"$sel:statistics:DetailedStatistics($sel:unusedRangeCount:DetailedStatistics)$sel:allocationSizeMin:DetailedStatistics)$sel:allocationSizeMax:DetailedStatistics*$sel:unusedRangeSizeMin:DetailedStatistics*$sel:unusedRangeSizeMax:DetailedStatistics Statistics$sel:blockCount:Statistics$sel:allocationCount:Statistics$sel:blockBytes:Statistics$sel:allocationBytes:Statistics AllocatorInfo$sel:instance':AllocatorInfo!$sel:physicalDevice:AllocatorInfo$sel:device:AllocatorInfoAllocatorCreateInfo$sel:flags:AllocatorCreateInfo'$sel:physicalDevice:AllocatorCreateInfo$sel:device:AllocatorCreateInfo4$sel:preferredLargeHeapBlockSize:AllocatorCreateInfo,$sel:allocationCallbacks:AllocatorCreateInfo.$sel:deviceMemoryCallbacks:AllocatorCreateInfo&$sel:heapSizeLimit:AllocatorCreateInfo($sel:vulkanFunctions:AllocatorCreateInfo"$sel:instance':AllocatorCreateInfo)$sel:vulkanApiVersion:AllocatorCreateInfo6$sel:typeExternalMemoryHandleTypes:AllocatorCreateInfoVulkanFunctions*$sel:vkGetInstanceProcAddr:VulkanFunctions($sel:vkGetDeviceProcAddr:VulkanFunctions2$sel:vkGetPhysicalDeviceProperties:VulkanFunctions8$sel:vkGetPhysicalDeviceMemoryProperties:VulkanFunctions%$sel:vkAllocateMemory:VulkanFunctions!$sel:vkFreeMemory:VulkanFunctions $sel:vkMapMemory:VulkanFunctions"$sel:vkUnmapMemory:VulkanFunctions.$sel:vkFlushMappedMemoryRanges:VulkanFunctions3$sel:vkInvalidateMappedMemoryRanges:VulkanFunctions'$sel:vkBindBufferMemory:VulkanFunctions&$sel:vkBindImageMemory:VulkanFunctions2$sel:vkGetBufferMemoryRequirements:VulkanFunctions1$sel:vkGetImageMemoryRequirements:VulkanFunctions#$sel:vkCreateBuffer:VulkanFunctions$$sel:vkDestroyBuffer:VulkanFunctions"$sel:vkCreateImage:VulkanFunctions#$sel:vkDestroyImage:VulkanFunctions$$sel:vkCmdCopyBuffer:VulkanFunctions6$sel:vkGetBufferMemoryRequirements2KHR:VulkanFunctions5$sel:vkGetImageMemoryRequirements2KHR:VulkanFunctions+$sel:vkBindBufferMemory2KHR:VulkanFunctions*$sel:vkBindImageMemory2KHR:VulkanFunctions<$sel:vkGetPhysicalDeviceMemoryProperties2KHR:VulkanFunctions8$sel:vkGetDeviceBufferMemoryRequirements:VulkanFunctions7$sel:vkGetDeviceImageMemoryRequirements:VulkanFunctionsDeviceMemoryCallbacks&$sel:pfnAllocate:DeviceMemoryCallbacks"$sel:pfnFree:DeviceMemoryCallbacks#$sel:userData:DeviceMemoryCallbacksPFN_vmaFreeDeviceMemoryFunctionFN_vmaFreeDeviceMemoryFunction#PFN_vmaAllocateDeviceMemoryFunction"FN_vmaAllocateDeviceMemoryFunction VirtualBlockVirtualAllocationDefragmentationContext AllocationPool AllocatorVirtualAllocationCreateFlagBitsVirtualAllocationCreateFlagsVirtualBlockCreateFlagBitsVirtualBlockCreateFlagsDefragmentationMoveOperationDefragmentationFlagBitsDefragmentationFlagsPoolCreateFlagBitsPoolCreateFlagsAllocationCreateFlagBitsAllocationCreateFlags MemoryUsageAllocatorCreateFlagBitsAllocatorCreateFlags'VIRTUAL_ALLOCATION_CREATE_STRATEGY_MASK1VIRTUAL_ALLOCATION_CREATE_STRATEGY_MIN_OFFSET_BIT/VIRTUAL_ALLOCATION_CREATE_STRATEGY_MIN_TIME_BIT1VIRTUAL_ALLOCATION_CREATE_STRATEGY_MIN_MEMORY_BIT+VIRTUAL_ALLOCATION_CREATE_UPPER_ADDRESS_BIT#VIRTUAL_BLOCK_CREATE_ALGORITHM_MASK)VIRTUAL_BLOCK_CREATE_LINEAR_ALGORITHM_BIT&DEFRAGMENTATION_MOVE_OPERATION_DESTROY%DEFRAGMENTATION_MOVE_OPERATION_IGNORE#DEFRAGMENTATION_MOVE_OPERATION_COPY#DEFRAGMENTATION_FLAG_ALGORITHM_MASK,DEFRAGMENTATION_FLAG_ALGORITHM_EXTENSIVE_BIT'DEFRAGMENTATION_FLAG_ALGORITHM_FULL_BIT+DEFRAGMENTATION_FLAG_ALGORITHM_BALANCED_BIT'DEFRAGMENTATION_FLAG_ALGORITHM_FAST_BITPOOL_CREATE_ALGORITHM_MASK POOL_CREATE_LINEAR_ALGORITHM_BIT/POOL_CREATE_IGNORE_BUFFER_IMAGE_GRANULARITY_BITALLOCATION_CREATE_STRATEGY_MASK(ALLOCATION_CREATE_STRATEGY_FIRST_FIT_BIT'ALLOCATION_CREATE_STRATEGY_BEST_FIT_BIT)ALLOCATION_CREATE_STRATEGY_MIN_OFFSET_BIT'ALLOCATION_CREATE_STRATEGY_MIN_TIME_BIT)ALLOCATION_CREATE_STRATEGY_MIN_MEMORY_BIT8ALLOCATION_CREATE_HOST_ACCESS_ALLOW_TRANSFER_INSTEAD_BIT(ALLOCATION_CREATE_HOST_ACCESS_RANDOM_BIT2ALLOCATION_CREATE_HOST_ACCESS_SEQUENTIAL_WRITE_BITALLOCATION_CREATE_CAN_ALIAS_BIT#ALLOCATION_CREATE_WITHIN_BUDGET_BITALLOCATION_CREATE_DONT_BIND_BIT#ALLOCATION_CREATE_UPPER_ADDRESS_BIT+ALLOCATION_CREATE_USER_DATA_COPY_STRING_BITALLOCATION_CREATE_MAPPED_BIT$ALLOCATION_CREATE_NEVER_ALLOCATE_BIT&ALLOCATION_CREATE_DEDICATED_MEMORY_BITMEMORY_USAGE_AUTO_PREFER_HOSTMEMORY_USAGE_AUTO_PREFER_DEVICEMEMORY_USAGE_AUTO!MEMORY_USAGE_GPU_LAZILY_ALLOCATEDMEMORY_USAGE_CPU_COPYMEMORY_USAGE_GPU_TO_CPUMEMORY_USAGE_CPU_TO_GPUMEMORY_USAGE_CPU_ONLYMEMORY_USAGE_GPU_ONLYMEMORY_USAGE_UNKNOWN(ALLOCATOR_CREATE_EXT_MEMORY_PRIORITY_BIT*ALLOCATOR_CREATE_BUFFER_DEVICE_ADDRESS_BIT/ALLOCATOR_CREATE_AMD_DEVICE_COHERENT_MEMORY_BIT&ALLOCATOR_CREATE_EXT_MEMORY_BUDGET_BIT%ALLOCATOR_CREATE_KHR_BIND_MEMORY2_BIT-ALLOCATOR_CREATE_KHR_DEDICATED_ALLOCATION_BIT,ALLOCATOR_CREATE_EXTERNALLY_SYNCHRONIZED_BITcreateAllocator withAllocatordestroyAllocatorgetAllocatorInfogetPhysicalDevicePropertiesgetMemoryPropertiesgetMemoryTypePropertiessetCurrentFrameIndexcalculateStatisticsgetHeapBudgetsfindMemoryTypeIndex findMemoryTypeIndexForBufferInfofindMemoryTypeIndexForImageInfo createPoolwithPool destroyPoolgetPoolStatisticscalculatePoolStatisticscheckPoolCorruption getPoolName setPoolNameallocateMemory withMemoryallocateMemoryPageswithMemoryPagesallocateMemoryForBufferwithMemoryForBufferallocateMemoryForImagewithMemoryForImage freeMemoryfreeMemoryPagesgetAllocationInfosetAllocationUserDatasetAllocationNamegetAllocationMemoryProperties mapMemorywithMappedMemory unmapMemoryflushAllocationinvalidateAllocationflushAllocationsinvalidateAllocationscheckCorruptionbeginDefragmentationwithDefragmentationendDefragmentationbeginDefragmentationPassuseDefragmentationPassendDefragmentationPassbindBufferMemorybindBufferMemory2bindImageMemorybindImageMemory2 createBuffer withBuffercreateBufferWithAlignmentcreateAliasingBuffercreateAliasingBuffer2 destroyBuffer createImage withImagecreateAliasingImagecreateAliasingImage2 destroyImagecreateVirtualBlockwithVirtualBlockdestroyVirtualBlockisVirtualBlockEmptygetVirtualAllocationInfovirtualAllocatewithVirtualAllocation virtualFreeclearVirtualBlocksetVirtualAllocationUserDatagetVirtualBlockStatisticscalculateVirtualBlockStatisticsbuildVirtualBlockStatsStringfreeVirtualBlockStatsStringbuildStatsStringfreeStatsString$fReadAllocatorCreateFlagBits$fShowAllocatorCreateFlagBits$fReadMemoryUsage$fShowMemoryUsage$fReadAllocationCreateFlagBits$fShowAllocationCreateFlagBits$fReadPoolCreateFlagBits$fShowPoolCreateFlagBits$fReadDefragmentationFlagBits$fShowDefragmentationFlagBits"$fReadDefragmentationMoveOperation"$fShowDefragmentationMoveOperation $fReadVirtualBlockCreateFlagBits $fShowVirtualBlockCreateFlagBits%$fReadVirtualAllocationCreateFlagBits%$fShowVirtualAllocationCreateFlagBits$fShowAllocator $fShowPool$fShowAllocation$fShowDefragmentationContext$fShowVirtualAllocation$fShowVirtualBlock$fZeroDeviceMemoryCallbacks$fStorableDeviceMemoryCallbacks"$fFromCStructDeviceMemoryCallbacks $fToCStructDeviceMemoryCallbacks$fZeroVulkanFunctions$fStorableVulkanFunctions$fFromCStructVulkanFunctions$fToCStructVulkanFunctions$fZeroAllocatorCreateInfo $fFromCStructAllocatorCreateInfo$fToCStructAllocatorCreateInfo$fZeroAllocatorInfo$fStorableAllocatorInfo$fFromCStructAllocatorInfo$fToCStructAllocatorInfo$fZeroStatistics$fStorableStatistics$fFromCStructStatistics$fToCStructStatistics$fZeroDetailedStatistics$fStorableDetailedStatistics$fFromCStructDetailedStatistics$fToCStructDetailedStatistics$fZeroTotalStatistics$fStorableTotalStatistics$fFromCStructTotalStatistics$fToCStructTotalStatistics $fZeroBudget$fStorableBudget$fFromCStructBudget$fToCStructBudget$fZeroAllocationCreateInfo$fStorableAllocationCreateInfo!$fFromCStructAllocationCreateInfo$fToCStructAllocationCreateInfo$fZeroPoolCreateInfo$fStorablePoolCreateInfo$fFromCStructPoolCreateInfo$fToCStructPoolCreateInfo$fZeroAllocationInfo$fFromCStructAllocationInfo$fToCStructAllocationInfo$fZeroDefragmentationInfo$fStorableDefragmentationInfo $fFromCStructDefragmentationInfo$fToCStructDefragmentationInfo$fZeroDefragmentationMove$fStorableDefragmentationMove $fFromCStructDefragmentationMove$fToCStructDefragmentationMove!$fZeroDefragmentationPassMoveInfo%$fStorableDefragmentationPassMoveInfo($fFromCStructDefragmentationPassMoveInfo&$fToCStructDefragmentationPassMoveInfo$fZeroDefragmentationStats$fStorableDefragmentationStats!$fFromCStructDefragmentationStats$fToCStructDefragmentationStats$fZeroVirtualBlockCreateInfo#$fFromCStructVirtualBlockCreateInfo!$fToCStructVirtualBlockCreateInfo!$fZeroVirtualAllocationCreateInfo%$fStorableVirtualAllocationCreateInfo($fFromCStructVirtualAllocationCreateInfo&$fToCStructVirtualAllocationCreateInfo$fZeroVirtualAllocationInfo$fStorableVirtualAllocationInfo"$fFromCStructVirtualAllocationInfo $fToCStructVirtualAllocationInfo$fEqDefragmentationStats$fEqDefragmentationPassMoveInfo$fEqDefragmentationMove$fEqStatistics$fEqAllocatorInfo$fEqVulkanFunctions$fEqVirtualBlock$fOrdVirtualBlock$fStorableVirtualBlock$fZeroVirtualBlock$fIsHandleVirtualBlock$fEqVirtualAllocation$fOrdVirtualAllocation$fStorableVirtualAllocation$fZeroVirtualAllocation$fIsHandleVirtualAllocation$fEqDefragmentationContext$fOrdDefragmentationContext $fStorableDefragmentationContext$fZeroDefragmentationContext $fIsHandleDefragmentationContext$fEqAllocation$fOrdAllocation$fStorableAllocation$fZeroAllocation$fIsHandleAllocation$fEqPool $fOrdPool$fStorablePool $fZeroPool$fIsHandlePool $fEqAllocator$fOrdAllocator$fStorableAllocator$fZeroAllocator$fIsHandleAllocator#$fEqVirtualAllocationCreateFlagBits$$fOrdVirtualAllocationCreateFlagBits)$fStorableVirtualAllocationCreateFlagBits%$fZeroVirtualAllocationCreateFlagBits%$fBitsVirtualAllocationCreateFlagBits+$fFiniteBitsVirtualAllocationCreateFlagBits$fEqVirtualBlockCreateFlagBits$fOrdVirtualBlockCreateFlagBits$$fStorableVirtualBlockCreateFlagBits $fZeroVirtualBlockCreateFlagBits $fBitsVirtualBlockCreateFlagBits&$fFiniteBitsVirtualBlockCreateFlagBits $fEqDefragmentationMoveOperation!$fOrdDefragmentationMoveOperation&$fStorableDefragmentationMoveOperation"$fZeroDefragmentationMoveOperation$fEqDefragmentationFlagBits$fOrdDefragmentationFlagBits!$fStorableDefragmentationFlagBits$fZeroDefragmentationFlagBits$fBitsDefragmentationFlagBits#$fFiniteBitsDefragmentationFlagBits$fEqPoolCreateFlagBits$fOrdPoolCreateFlagBits$fStorablePoolCreateFlagBits$fZeroPoolCreateFlagBits$fBitsPoolCreateFlagBits$fFiniteBitsPoolCreateFlagBits$fEqAllocationCreateFlagBits$fOrdAllocationCreateFlagBits"$fStorableAllocationCreateFlagBits$fZeroAllocationCreateFlagBits$fBitsAllocationCreateFlagBits$$fFiniteBitsAllocationCreateFlagBits$fEqMemoryUsage$fOrdMemoryUsage$fStorableMemoryUsage$fZeroMemoryUsage$fEqAllocatorCreateFlagBits$fOrdAllocatorCreateFlagBits!$fStorableAllocatorCreateFlagBits$fZeroAllocatorCreateFlagBits$fBitsAllocatorCreateFlagBits#$fFiniteBitsAllocatorCreateFlagBits$fShowVirtualAllocationInfo!$fShowVirtualAllocationCreateInfo$fShowVirtualBlockCreateInfo$fShowDefragmentationStats!$fShowDefragmentationPassMoveInfo$fShowDefragmentationMove$fShowDefragmentationInfo$fShowAllocationInfo$fShowPoolCreateInfo$fShowAllocationCreateInfo $fShowBudget$fShowTotalStatistics$fShowDetailedStatistics$fShowStatistics$fShowAllocatorInfo$fShowAllocatorCreateInfo$fShowVulkanFunctions$fShowDeviceMemoryCallbacks