h&VtJ      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~None( #$&'(./0289:<>?FVulkanMemoryAllocatorVmaVirtualBlockHandle 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.VulkanMemoryAllocatorVmaVirtualAllocationInfo;Parameters of an existing virtual allocation, returned by .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. VulkanMemoryAllocatorFlags to be passed as %VmaVirtualAllocationCreateInfo::flags.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.VulkanMemoryAllocatorFlags to be passed as  VmaVirtualBlockCreateInfo::flags.VulkanMemoryAllocatorVmaDefragmentationStats Statistics returned by 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.VulkanMemoryAllocatorVmaDefragmentationInfoDeprecated. Optional configuration parameters to be passed to function . DeprecatedThis is a part of the old interface. It is recommended to use structure * and function  instead.VulkanMemoryAllocatorMaximum total numbers of bytes that can be copied while moving allocations to different places. Default is  VK_WHOLE_SIZE, which means no limit. VulkanMemoryAllocatorMaximum number of allocations that can be moved to different place. Default is  UINT32_MAX, which means no limit.!VulkanMemoryAllocatorVmaDefragmentationPassInfo1Parameters for incremental defragmentation steps.To be used with function .%VulkanMemoryAllocatorVmaDefragmentationPassMoveInfo*VulkanMemoryAllocatorVmaDefragmentationInfo2Parameters for defragmentation.To be used with function .,VulkanMemoryAllocator%Reserved for future use. Should be 0.-VulkanMemoryAllocator9Pointer to array of allocations that can be defragmented.The array should have allocationCount elements. The array should not contain nulls. Elements in the array should be unique - same allocation cannot occur twice. It is safe to pass allocations that are in the lost state - they are ignored. All allocations not present in this array are considered non-moveable during this defragmentation..VulkanMemoryAllocatorOptional, output. Pointer to array that will be filled with information whether the allocation at certain index has been changed during defragmentation.The array should have allocationCount elements. You can pass null if you are not interested in this information./VulkanMemoryAllocatorVulkanMemoryAllocator 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.It can change after call to  if this allocation is passed to the function, or if allocation is lost.?VulkanMemoryAllocator"Size of this allocation, in bytes.,It never changes, unless allocation is lost.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 call to / if this allocation is passed to the function.AVulkanMemoryAllocator3Custom general-purpose pointer that was passed as "VmaAllocationCreateInfo::pUserData or set using .It can change after call to  for this allocation.BVulkanMemoryAllocator 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 Z3. 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 :.Some kinds allocations can be in lost state. For more information, see Lost allocations.DVulkanMemoryAllocator VmaPoolStats Describes parameter of existing i.FVulkanMemoryAllocatorTotal amount of VkDeviceMemory0 allocated from Vulkan for this pool, in bytes.GVulkanMemoryAllocator2Total number of bytes in the pool not used by any B.HVulkanMemoryAllocator Number of B objects created from this pool that were not destroyed or lost.IVulkanMemoryAllocatorNumber of continuous memory ranges in the pool not used by any B.JVulkanMemoryAllocatorSize of the largest continuous free memory region available for new allocation.Making a new allocation of that size is not guaranteed to succeed because of possible additional margin required to respect alignment and buffer/image granularity.KVulkanMemoryAllocator Number of VkDeviceMemory blocks allocated for this pool.LVulkanMemoryAllocatorVmaPoolCreateInfoDescribes parameter of created i.NVulkanMemoryAllocator4Vulkan memory type index to allocate this pool from.OVulkanMemoryAllocatorUse combination of W.PVulkanMemoryAllocatorSize 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.QVulkanMemoryAllocatorMinimum 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.RVulkanMemoryAllocatorMaximum 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.SVulkanMemoryAllocatorMaximum number of additional frames that are in use at the same time as current frame.8This value is used only when you make allocations with  flag. Such allocation cannot become lost if allocation.lastUseFrameIndex >= allocator.currentFrameIndex - frameInUseCount.For example, if you double-buffer your command buffers, so resources used for rendering in previous frame may still be in use by the GPU at the moment you allocate resources needed for the current frame, set this value to 1.If you want to allow any allocations other than used in the current frame to become lost, set this value to 0.TVulkanMemoryAllocatorA 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.UVulkanMemoryAllocatorAdditional 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.VVulkanMemoryAllocator 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.WVulkanMemoryAllocatorFlags to be passed as VmaPoolCreateInfo::flags.ZVulkanMemoryAllocatorVmaAllocationCreateInfo\VulkanMemoryAllocatorUse d enum.]VulkanMemoryAllocatorIntended usage of memory.You can leave 2 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.8Leave 0 if you specify memory requirements in other way. If pool% is not null, this member is ignored._VulkanMemoryAllocatorFlags that preferably should be set in a memory type chosen for an allocation..Set to 0 if no additional flags are preferred. If pool% is not null, this member is ignored.`VulkanMemoryAllocatorBitmask containing one bit set for every memory type acceptable for this allocation.Value 0 is equivalent to  UINT32_MAX - it means any memory type is accepted if it meets other requirements specified by this structure, with no further restrictions on memory type index. If pool% is not null, this member is ignored.aVulkanMemoryAllocator/Pool that this allocation should be created in.Leave VK_NULL_HANDLE7 to allocate from default pool. If not null, members: usage,  requiredFlags, preferredFlags, memoryTypeBits are ignored.bVulkanMemoryAllocator6Custom general-purpose pointer that will be stored in B, can be read as VmaAllocationInfo::pUserData and changed using .If  is used, it must be either null or pointer to a null-terminated string. The string will be then copied to internal buffer, so it doesn't need to be valid after allocation call.cVulkanMemoryAllocatorA floating-point value between 0 and 1, indicating the priority of the allocation relative to other memory allocations.It is used only when ' flag was used during creation of the  object and this allocation ends up as dedicated or is explicitly forced as dedicated using . Otherwise, it has the priority of a memory block where it is placed and this variable is ignored.dVulkanMemoryAllocatorFlags to be passed as VmaAllocationCreateInfo::flags.iVulkanMemoryAllocatorVmaPoolRepresents custom memory pool.Fill structure L and call function  to create it. Call function  to destroy it.For more information see Custom memory pools.kVulkanMemoryAllocator VmaBudgetStatistics of current memory usage and available budget, in bytes, for specific memory heap.mVulkanMemoryAllocatorSum size of all VkDeviceMemory2 blocks allocated from particular heap, in bytes.nVulkanMemoryAllocatorSum size of all allocations created in particular heap, in bytes.Usually less or equal than  blockBytes. Difference blockBytes - allocationBytes is the amount of memory allocated but unused - available for new allocations or wasted due to fragmentation.It might be greater than  blockBytes if there are some allocations in lost state, as they account to this value as well.oVulkanMemoryAllocator8Estimated current memory usage of the program, in bytes.Fetched from system using VK_EXT_memory_budget extension if enabled.It might be different than  blockBytes (usually higher) due to additional implicit objects also occupying the memory, like swapchain, pipelines, descriptor heaps, command buffers, or VkDeviceMemory3 blocks allocated outside of this library, if any.pVulkanMemoryAllocator>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, like other programs also consuming system resources. Difference budget - usage is the amount of additional memory that can probably be allocated without problems. Exceeding the budget may result in various problems.qVulkanMemoryAllocatorVmaStatsv  memoryType [VK_MAX_MEMORY_TYPES]v  memoryHeap [VK_MAX_MEMORY_HEAPS]v total3General statistics from current state of Allocator. memoryHeap,memoryHeap VmaStats VmaStats memoryHeap 5VmaStatInfo VmaStats::memoryHeap[VK_MAX_MEMORY_HEAPS] memoryType,memoryType VmaStats VmaStats memoryType 5VmaStatInfo VmaStats::memoryType[VK_MAX_MEMORY_TYPES]vVulkanMemoryAllocator VmaStatInfo:Calculated statistics of memory usage in entire allocator.xVulkanMemoryAllocator Number of VkDeviceMemory Vulkan memory blocks allocated.yVulkanMemoryAllocator Number of B allocation objects allocated.zVulkanMemoryAllocator4Number of free ranges of memory between allocations.{VulkanMemoryAllocator2Total number of bytes occupied by all allocations.|VulkanMemoryAllocator0Total number of bytes occupied by unused ranges.VulkanMemoryAllocatorVmaAllocatorInfoInformation about existing  object.VulkanMemoryAllocator!Handle to Vulkan instance object.3This is the same value as has been passed through  VmaAllocatorCreateInfo::instance.VulkanMemoryAllocator(Handle to Vulkan physical device object.3This is the same value as has been passed through &VmaAllocatorCreateInfo::physicalDevice.VulkanMemoryAllocatorHandle to Vulkan device object.3This is the same value as has been passed through VmaAllocatorCreateInfo::device.VulkanMemoryAllocatorVmaAllocatorCreateInfo)Description of a Allocator to be created.VulkanMemoryAllocator!Flags for created allocator. Use  enum.VulkanMemoryAllocatorVulkan physical device.It must be valid throughout whole lifetime of created allocator.VulkanMemoryAllocatorVulkan device.It must be valid throughout whole lifetime of created allocator.VulkanMemoryAllocatorPreferred 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.VulkanMemoryAllocator1Custom CPU memory allocation callbacks. Optional.Optional, can be null. When specified, will also be used for all CPU-side memory allocations.VulkanMemoryAllocatorInformative callbacks for vkAllocateMemory,  vkFreeMemory . Optional.Optional, can be null.VulkanMemoryAllocatorMaximum number of additional frames that are in use at the same time as current frame.This value is used only when you make allocations with VMA_ALLOCATION_CREATE_CAN_BECOME_LOST_BIT flag. Such allocation cannot become lost if allocation.lastUseFrameIndex >= allocator.currentFrameIndex - frameInUseCount.For example, if you double-buffer your command buffers, so resources used for rendering in previous frame may still be in use by the GPU at the moment you allocate resources needed for the current frame, set this value to 1.If you want to allow any allocations other than used in the current frame to become lost, set this value to 0.VulkanMemoryAllocatorEither 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.VulkanMemoryAllocator*Pointers to Vulkan functions. Can be null.For details see Pointers to Vulkan functions.VulkanMemoryAllocator3Parameters for recording of VMA calls. Can be null.If not null, it enables recording of calls to VMA functions to a file. If support for recording is not enabled using VMA_RECORDING_ENABLED6 macro, creation of the allocator object fails with VK_ERROR_FEATURE_NOT_PRESENT.VulkanMemoryAllocator!Handle to Vulkan instance object.Starting from version 3.0.0 this member is no longer optional, it must be set!VulkanMemoryAllocatorOptional. 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 are supported by the current implementation. Leaving it initialized to zero is equivalent to VK_API_VERSION_1_0.VulkanMemoryAllocatorEither 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.VulkanMemoryAllocatorVmaRecordSettingsParameters for recording calls to VMA functions. To be used in 'VmaAllocatorCreateInfo::pRecordSettings.VulkanMemoryAllocatorFlags for recording. Use  enum.VulkanMemoryAllocator9Path to the file that should be written by the recording.Suggested extension: "csv". If the file already exists, it will be overwritten. It will be opened for the whole time  object is alive. If opening this file fails, creation of the whole allocator object fails.VulkanMemoryAllocatorFlags to be used in VmaRecordSettings::flags.VulkanMemoryAllocatorVmaVulkanFunctionsPointers to some Vulkan functions - a subset used by the library.Used in (VmaAllocatorCreateInfo::pVulkanFunctions.VulkanMemoryAllocatorFetch "vkGetBufferMemoryRequirements2" on Vulkan >= 1.1, fetch "vkGetBufferMemoryRequirements2KHR" when using VK_KHR_dedicated_allocation extension.VulkanMemoryAllocatorFetch "vkGetImageMemoryRequirements 2" 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.VulkanMemoryAllocatorFlags for created .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.VulkanMemoryAllocator VmaAllocator3Represents main object of this library initialized.Fill structure  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.VulkanMemoryAllocatorA bit mask to extract only STRATEGY bits from entire set of flags.These stategy flags are binary compatible with equivalent flags in d.VulkanMemoryAllocatorAllocation strategy that tries to minimize memory fragmentation.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, buddy allocation algorithm in this virtual block.It operates on a tree of blocks, each having size that is a power of two and a half of its parent's size. Comparing to default algorithm, this one provides faster allocation and deallocation and decreased external fragmentation, at the expense of more memory wasted (internal fragmentation). For details, see documentation chapter /Buddy allocation algorithm/.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.VulkanMemoryAllocatorBit mask to extract only  ALGORITHM bits from entire set of flags.VulkanMemoryAllocator=Enables alternative, buddy allocation algorithm in this pool.It operates on a tree of blocks, each having size that is a power of two and a half of its parent's size. Comparing to default algorithm, this one provides faster allocation and deallocation and decreased external fragmentation, at the expense of more memory wasted (internal fragmentation). For details, see documentation chapter /Buddy allocation algorithm/.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.(When using this flag, you must specify  VmaPoolCreateInfo::maxBlockCount == 1 (or 0 for default).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.VulkanMemoryAllocatorAllocation strategy that tries to minimize memory fragmentation.VulkanMemoryAllocator;Allocation strategy that tries to minimize allocation time.VulkanMemoryAllocator8Allocation strategy that tries to minimize memory usage.VulkanMemoryAllocatorAllocation strategy that chooses first suitable free range for the allocation."First" doesn't necessarily means the one with smallest offset in memory, but rather the one that is easiest and fastest to find.VulkanMemoryAllocatorAllocation strategy that chooses biggest possible free range for the allocation.VulkanMemoryAllocatorAllocation strategy that chooses smallest possible free range for the allocation.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.VulkanMemoryAllocatorAllocation will be created from upper stack in a double stack pool.9This flag is only allowed for custom pools created with  flag.VulkanMemoryAllocatorSet 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  pUserData. The string is automatically freed together with the allocation. It is also used in .VulkanMemoryAllocatorWhile creating allocation using this flag, other allocations that were created with flag  can become lost.For details about supporting lost allocations, see Lost Allocations chapter of User Guide on Main Page.VulkanMemoryAllocatorAllocation created with this flag can become lost as a result of another allocation with ( flag, so you must check it before use.)To check if allocation is not lost, call  and check if VmaAllocationInfo::deviceMemory is not VK_NULL_HANDLE.For details about supporting lost allocations, see Lost Allocations chapter of User Guide on Main Page.,You should not use this flag together with .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).,You should not use this flag together with .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.If VmaAllocationCreateInfo::pool0 is not null, this flag is implied and ignored.VulkanMemoryAllocatorSet this flag if the allocation should have its own memory block.Use it for special, big resources, like fullscreen images used as attachments. You should not use this flag if VmaAllocationCreateInfo::pool is not null.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+CPU memory - memory that is preferably not  DEVICE_LOCAL!, but also not guaranteed to be  HOST_VISIBLE.Usage: Staging copy of resources moved from GPU memory to CPU memory as part of custom paging/residency mechanism, to be moved back to GPU memory when needed.VulkanMemoryAllocator*Memory mappable on host (guarantees to be  HOST_VISIBLE+) and cached. It is roughly equivalent of D3D12_HEAP_TYPE_READBACK.Usage:Resources written by device, read by host - results of some computations, e.g. screen capture, average scene luminance for HDR tone mapping.Any resources read or accessed randomly on host, e.g. CPU-side copy of vertex buffer used as source of transfer, but also used for collision detection.VulkanMemoryAllocator7Memory that is both mappable on host (guarantees to be  HOST_VISIBLE) and preferably fast to access by GPU. CPU access is typically uncached. Writes may be write-combined.Usage: Resources written frequently by host (dynamic), read by device. E.g. textures (with LINEAR layout), vertex buffers, uniform buffers updated every frame or every draw call.VulkanMemoryAllocatorMemory will be mappable on host. It usually means CPU (system) memory. Guarantees to be  HOST_VISIBLE and  HOST_COHERENT. CPU access is typically uncached. Writes may be write-combined. Resources created in this pool may still be accessible to the device, but access to them can be slow. It is roughly equivalent of D3D12_HEAP_TYPE_UPLOAD.9Usage: Staging copy of resources used as transfer source.VulkanMemoryAllocatorMemory will be used on device only, so fast access from the device is preferred. It usually means device-local GPU (video) memory. No need to be mappable on host. It is roughly equivalent of D3D12_HEAP_TYPE_DEFAULT.Usage:Resources written and read by device, e.g. images used as attachments.Resources transferred from host once (immutable) or infrequently and read by device multiple times, e.g. textures to be sampled, vertex buffers, uniform (constant) buffers, and majority of other types of resources used on GPU.Allocation may still end up in  HOST_VISIBLE memory on some implementations. In such case, you are free to map it. You can use  with this usage type.VulkanMemoryAllocator:No intended memory usage specified. Use other members of Z to specify your requirements.VulkanMemoryAllocator2Enables flush after recording every function call.Enable it if you expect your application to crash, which may leave recording file truncated. It may degrade performance though.VulkanMemoryAllocatorEnables usage of VK_EXT_memory_priority extension in the library.You may set this flag only if you found available and enabled this device extension, along with VkPhysicalDeviceMemoryPriorityFeaturesEXT::memoryPriority == VK_TRUE*, while creating Vulkan device passed as VmaAllocatorCreateInfo::device.When this flag is used, !VmaAllocationCreateInfo::priority and VmaPoolCreateInfo::priority are used to set priorities of allocated Vulkan memory. Without it, these variables are ignored.A priority must be a floating-point value between 0 and 1, indicating the priority of the allocation relative to other memory allocations. Larger values are higher priority. The granularity of the priorities is implementation-dependent. It is automatically passed to every call to vkAllocateMemory& done by the library using structure VkMemoryPriorityAllocateInfoEXT. The value to be used for default priority is 0.5. For more details, see the documentation of the VK_EXT_memory_priority extension.VulkanMemoryAllocatorEnables usage of "buffer device address" feature, which allows you to use function vkGetBufferDeviceAddress* to get raw GPU pointer to a buffer and pass it for usage inside a shader."You may set this flag only if you: (For Vulkan version < 1.2) Found as available and enabled device extension VK_KHR_buffer_device_address. This extension is promoted to core Vulkan 1.2.3Found as available and enabled device feature VkPhysicalDeviceBufferDeviceAddressFeatures::bufferDeviceAddress.4When this flag is set, you can create buffers with )VK_BUFFER_USAGE_SHADER_DEVICE_ADDRESS_BIT, using VMA. The library automatically adds %VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_BIT9 to allocated memory blocks wherever it might be needed.For more information, see documentation chapter /Enabling buffer device address/.VulkanMemoryAllocator9Enables usage of VK_AMD_device_coherent_memory extension."You may set this flag only if you:found out that this device extension is supported and enabled it while creating Vulkan device passed as VmaAllocatorCreateInfo::device,checked that ?VkPhysicalDeviceCoherentMemoryFeaturesAMD::deviceCoherentMemory: is true and set it while creating the Vulkan device,.want it to be used internally by this library.The extension and accompanying device feature provide access to memory types with *VK_MEMORY_PROPERTY_DEVICE_COHERENT_BIT_AMD and *VK_MEMORY_PROPERTY_DEVICE_UNCACHED_BIT_AMD flags. They are useful mostly for writing breadcrumb markers - a common method for debugging GPU crash/hang/TDR.When the extension is not enabled, such memory types are still enumerated, but their usage is illegal. To protect from this error, if you don't create the allocator with this flag, it will refuse to allocate any memory or create a custom pool in such memory type, returning VK_ERROR_FEATURE_NOT_PRESENT.VulkanMemoryAllocator0Enables usage of VK_EXT_memory_budget extension.You may set this flag only if you found out that this device extension is supported, you enabled it while creating Vulkan device passed as VmaAllocatorCreateInfo::device, and you want it to be used internally by this library, along with another instance extension VK_KHR_get_physical_device_properties2, which is required by it (or Vulkan 1.1, where this extension is promoted).The extension provides query for current memory usage and budget, which will probably be more accurate than an estimation used by the library otherwise.VulkanMemoryAllocator/Enables usage of VK_KHR_bind_memory2 extension.The flag works only if (VmaAllocatorCreateInfo::vulkanApiVersion == VK_API_VERSION_1_0 . When it is VK_API_VERSION_1_1, the flag is ignored because the extension has been promoted to Vulkan 1.1.You may set this flag only if you found out that this device extension is supported, you enabled it while creating Vulkan device passed as VmaAllocatorCreateInfo::device9, and you want it to be used internally by this library.!The extension provides functions vkBindBufferMemory2KHR and vkBindImageMemory2KHR!, which allow to pass a chain of pNext= structures while binding. This flag is required if you use pNext parameter in  or .VulkanMemoryAllocator7Enables usage of VK_KHR_dedicated_allocation extension.The flag works only if (VmaAllocatorCreateInfo::vulkanApiVersion == VK_API_VERSION_1_0 . When it is VK_API_VERSION_1_1, the flag is ignored because the extension has been promoted to Vulkan 1.1.Using this extension will automatically allocate dedicated blocks of memory for some buffers and images instead of suballocating place for them out of bigger memory blocks (as if you explicitly used  flag) when it is recommended by the driver. It may improve performance on some GPUs.You may set this flag only if you found out that following device extensions are supported, you enabled them while creating Vulkan device passed as VmaAllocatorCreateInfo::device;, and you want them to be used internally by this library:2VK_KHR_get_memory_requirements2 (device extension).VK_KHR_dedicated_allocation (device extension)When this flag is set, you can experience following warnings reported by Vulkan validation layer. You can ignore them.vkBindBufferMemory(): Binding memory to buffer 0x2d but vkGetBufferMemoryRequirements() has not been called on that buffer.VulkanMemoryAllocatorAllocator and all objects created from it will not be synchronized internally, so you must guarantee they are used from only one thread at a time or synchronized externally by you.Using this flag may increase performance because internal mutexes are not used.VulkanMemoryAllocatorCreates Allocator object.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.VulkanMemoryAllocatorDestroys allocator object.VulkanMemoryAllocator#Returns information about existing ' object - handle to Vulkan device etc.0It might be useful if you want to keep just the - handle and fetch other required handles to VkPhysicalDevice, VkDevice& etc. every time using this function.VulkanMemoryAllocatorPhysicalDeviceProperties are fetched from physicalDevice by the allocator. You can access it here, without fetching it again on your own.VulkanMemoryAllocatorPhysicalDeviceMemoryProperties are fetched from physicalDevice by the allocator. You can access it here, without fetching it again on your own.VulkanMemoryAllocatorGiven Memory Type Index, returns Property Flags of this memory type.This is just a convenience function. Same information can be obtained using .VulkanMemoryAllocator Sets index of the current frame.9This function must be used if you make allocations with  and  flags to inform the allocator when a new frame begins. Allocations queried using ) cannot become lost in the current frame.VulkanMemoryAllocator9Retrieves statistics from current state of the Allocator.This function is called "calculate" not "get" because it has to traverse all internal data structures, so it may be quite slow. For faster but more brief statistics suitable to be called every frame or every allocation, use .Note that when using allocator from multiple threads, returned information may immediately become outdated.VulkanMemoryAllocatorRetrieves information about current memory budget for all memory heaps. Parameters allocatorout  pBudget Must point to array with number of elements at least equal to number of memory heaps in physical device used.This function is called "get" not "calculate" because it is very fast, suitable to be called every frame or every allocation. For more detailed statistics use .Note that when using allocator from multiple threads, returned information may immediately become outdated.VulkanMemoryAllocatorBuilds and returns statistics as a null-terminated string in JSON format. Parameters allocatorout ppStatsString Must be freed using  function. detailedMapVulkanMemoryAllocator9Helps to find memoryTypeIndex, given memoryTypeBits and Z.0This algorithm tries to find a memory type that:Is allowed by memoryTypeBits.Contains all the flags from pAllocationCreateInfo->requiredFlags.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 Z.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. It is just a convenience function, equivalent to calling: vkCreateBuffer vkGetBufferMemoryRequirements vkDestroyBufferVulkanMemoryAllocator - 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 alloction.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 Parameters allocatorbuffer 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 .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 .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.VulkanMemoryAllocatorReturns current information about specified allocation and atomically marks it as used in current frame.8Current paramteres of given allocation are returned in pAllocationInfo.This function also atomically "touches" allocation - marks it as used in current frame, just like '. If the allocation is in lost state, /pAllocationInfo->deviceMemory == VK_NULL_HANDLE.Although this function uses atomics and doesn't lock any mutex, so it should be quite efficient, you can avoid calling it too often.You can retrieve same :< structure while creating your resource, from function , . You can remember it if you are sure parameters don't change (e.g. due to defragmentation or allocation becoming lost).:If you just want to check if allocation is not lost,  will work faster.VulkanMemoryAllocatorReturns VK_TRUE if allocation is not lost and atomically marks it as used in current frame.)If the allocation has been created with  flag, this function returns VK_TRUE if it is not in lost state, so it can still be used. It then also atomically "touches" the allocation - marks it as used in current frame, so that you can be sure it won't become lost in current frame or next frameInUseCount frames.9If the allocation is in lost state, the function returns VK_FALSE. Memory of such allocation, as well as buffer or image bound to it, should not be used. Lost allocation and the buffer/image still need to be destroyed.,If the allocation has been created without % flag, this function always returns VK_TRUE.VulkanMemoryAllocator0Sets pUserData in given allocation to new value.If the allocation was created with VMA_ALLOCATION_CREATE_USER_DATA_COPY_STRING_BIT, pUserData 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  pUserData. String passed as pUserData 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 pUserData is freed from memory./If the flag was not used, the value of pointer  pUserData! is just 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.VulkanMemoryAllocatorCreates new allocation that is in lost state from the beginning.:It can be useful if you need a dummy, non-null allocation./You still need to destroy created object using .Returned allocation is not tied to any specific memory pool or memory type and not bound to any image or buffer. It has size = 0. It cannot be turned into a real, non-empty allocation.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.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, *ppData contains pointer to first byte of this memory. If the allocation is part of bigger VkDeviceMemory block, the pointer is correctly offsetted to the beginning of region assigned to this particular allocation.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 always fails when called for allocation that was created with * flag. Such allocations cannot be mapped.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 pStats Optional. Statistics of defragmentation. You can pass null if you are not interested in this information.out  pContext &Context object that must be passed to  to finish defragmentation.Returns VK_SUCCESS and *pContext == null9 if defragmentation finished within this function call.  VK_NOT_READY and *pContext != null< if defragmentation has been started and you need to call / to finish it. Negative value in case of error.-Use this function instead of old, deprecated .Warning! Between the call to  and :5You should not use any of allocations passed as pInfo->pAllocations8 or any allocations that belong to pools passed as  pInfo->pPools, including calling , , or access their data.Some mutexes protecting internal data structures may be locked, so trying to make or free any allocations, bind buffers or images, map memory, or launch another simultaneous defragmentation in between may cause stall (when done on another thread) or deadlock (when done on the same thread), unless you are 100% sure that defragmented allocations are in different pools.Information returned via pStats and pInfo->pAllocationsChanged5 are undefined. They become valid after call to .If pInfo->commandBuffer is not null, you must submit that command buffer and make sure it finished execution before calling .For more information and important limitations regarding 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.8Use this function to finish defragmentation started by . It is safe to pass context == null". The function then does nothing.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.VulkanMemoryAllocator2Deprecated. Compacts memory by moving allocations. Parameters allocator  pAllocations =Array of allocations that can be moved during this compation. allocationCount Number of elements in pAllocations and pAllocationsChanged arrays.out pAllocationsChanged Array of boolean values that will indicate whether matching allocation in pAllocations array has been moved. This parameter is optional. Pass null if you don't need this information. pDefragmentationInfo Configuration parameters. Optional - pass null to use default values.out pDefragmentationStats Statistics returned by the function. Optional - pass null if you don't need this information.Returns VK_SUCCESS4 if completed, negative error code in case of error. DeprecatedThis is a part of the old interface. It is recommended to use structure * and function  instead.This function works by moving allocations to different places (different VkDeviceMemory objects and/or different offsets) in order to optimize memory usage. Only allocations that are in  pAllocations array can be moved. All other allocations are considered nonmovable in this call. Basic rules:5Only allocations made in memory types that have #VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT and $VK_MEMORY_PROPERTY_HOST_COHERENT_BIT flags can be compacted. You may pass other allocations but it makes no sense - these will never be moved.Custom pools created with  or  flag are not defragmented. Allocations passed to this function that come from such pools are ignored.Allocations created with  or created as dedicated allocations for any other reason are also ignored.&Both allocations made with or without  flag can be compacted. If not persistently mapped, memory will be mapped temporarily inside this function if needed.You must not pass same B object multiple times in  pAllocations array.The function also frees empty VkDeviceMemory blocks.Warning: This function may be time-consuming, so you shouldn't call it too often (like after every resource creation/destruction). You can call it on special occasions (like when reloading a game level or when you just destroyed a lot of objects). Calling it every frame may be OK, but you should measure that on your platform.For more information, see Defragmentation chapter.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.VulkanMemoryAllocator 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 (VmaAllocationCreateInfo::pool is null and  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.VulkanMemoryAllocator2Destroys Vulkan buffer and frees allocated memory.2This is just a convenience function equivalent to: vkDestroyBuffer(device, buffer, allocationCallbacks); vmaFreeMemory(allocator, allocation);4It it 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.VulkanMemoryAllocator1Destroys Vulkan image and frees allocated memory.2This is just a convenience function equivalent to: vkDestroyImage(device, image, allocationCallbacks); vmaFreeMemory(allocator, allocation);3It it 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 .There is no handle type for a virtual allocation. Virtual allocations within a specific virtual block are uniquely identified by their offsets.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).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 .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 .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 .    !"#$%&')(*+-,./0123456789:;?A><=@BCDEFKHIJGLMNOSTPQRUVWXYZ[`ab\]^_cdefghijklmnopqrstuvwxyz{|}~vwxyz{|}~qrstuklmnopijghfdeZ[`ab\]^_cYWXLMNOSTPQRUVDEFKHIJGBC:;?A><=@89756*+-,./01234%&')(!"#$             !"#$$%&'()*+,-../00112345678899:;<=>?@@ABCDEFGHIJJKLLMNOPQRSTUUVWWXXYYZ[\]^^_`abbcdefghijklmnnopqrrstuvwxyz{|}~1VulkanMemoryAllocator-0.7.4-VcEE1EU2w59PXS4ZpC2w2VulkanMemoryAllocatorControl.Exceptionbracket VirtualBlockVirtualAllocationInfo$sel:size:VirtualAllocationInfo#$sel:userData:VirtualAllocationInfoVirtualAllocationCreateInfo%$sel:size:VirtualAllocationCreateInfo*$sel:alignment:VirtualAllocationCreateInfo&$sel:flags:VirtualAllocationCreateInfo)$sel:userData:VirtualAllocationCreateInfoVirtualAllocationCreateFlagBitsVirtualAllocationCreateFlagsVirtualBlockCreateInfo $sel:size:VirtualBlockCreateInfo!$sel:flags:VirtualBlockCreateInfo/$sel:allocationCallbacks:VirtualBlockCreateInfoVirtualBlockCreateFlagBitsVirtualBlockCreateFlagsDefragmentationStats$$sel:bytesMoved:DefragmentationStats$$sel:bytesFreed:DefragmentationStats*$sel:allocationsMoved:DefragmentationStats1$sel:deviceMemoryBlocksFreed:DefragmentationStatsDefragmentationInfo'$sel:maxBytesToMove:DefragmentationInfo-$sel:maxAllocationsToMove:DefragmentationInfoDefragmentationPassInfo&$sel:moveCount:DefragmentationPassInfo"$sel:moves:DefragmentationPassInfoDefragmentationPassMoveInfo+$sel:allocation:DefragmentationPassMoveInfo'$sel:memory:DefragmentationPassMoveInfo'$sel:offset:DefragmentationPassMoveInfoDefragmentationInfo2$sel:flags:DefragmentationInfo2%$sel:allocations:DefragmentationInfo2,$sel:allocationsChanged:DefragmentationInfo2$sel:pools:DefragmentationInfo2+$sel:maxCpuBytesToMove:DefragmentationInfo21$sel:maxCpuAllocationsToMove:DefragmentationInfo2+$sel:maxGpuBytesToMove:DefragmentationInfo21$sel:maxGpuAllocationsToMove:DefragmentationInfo2'$sel:commandBuffer:DefragmentationInfo2DefragmentationFlagBitsDefragmentationFlagsDefragmentationContextAllocationInfo$sel:memoryType:AllocationInfo $sel:deviceMemory:AllocationInfo$sel:offset:AllocationInfo$sel:size:AllocationInfo$sel:mappedData:AllocationInfo$sel:userData:AllocationInfo Allocation PoolStats$sel:size:PoolStats$sel:unusedSize:PoolStats$sel:allocationCount:PoolStats$sel:unusedRangeCount:PoolStats!$sel:unusedRangeSizeMax:PoolStats$sel:blockCount:PoolStatsPoolCreateInfo#$sel:memoryTypeIndex:PoolCreateInfo$sel:flags:PoolCreateInfo$sel:blockSize:PoolCreateInfo!$sel:minBlockCount:PoolCreateInfo!$sel:maxBlockCount:PoolCreateInfo#$sel:frameInUseCount:PoolCreateInfo$sel:priority:PoolCreateInfo*$sel:minAllocationAlignment:PoolCreateInfo&$sel:memoryAllocateNext:PoolCreateInfoPoolCreateFlagBitsPoolCreateFlagsAllocationCreateInfo$sel:flags:AllocationCreateInfo$sel:usage:AllocationCreateInfo'$sel:requiredFlags:AllocationCreateInfo($sel:preferredFlags:AllocationCreateInfo($sel:memoryTypeBits:AllocationCreateInfo$sel:pool:AllocationCreateInfo"$sel:userData:AllocationCreateInfo"$sel:priority:AllocationCreateInfoAllocationCreateFlagBitsAllocationCreateFlags MemoryUsagePoolBudget$sel:blockBytes:Budget$sel:allocationBytes:Budget$sel:usage:Budget$sel:budget:BudgetStats$sel:memoryType:Stats$sel:memoryHeap:Stats$sel:total:StatsStatInfo$sel:blockCount:StatInfo$sel:allocationCount:StatInfo$sel:unusedRangeCount:StatInfo$sel:usedBytes:StatInfo$sel:unusedBytes:StatInfo$sel:allocationSizeMin:StatInfo$sel:allocationSizeAvg:StatInfo$sel:allocationSizeMax:StatInfo $sel:unusedRangeSizeMin:StatInfo $sel:unusedRangeSizeAvg:StatInfo $sel:unusedRangeSizeMax:StatInfo 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:frameInUseCount:AllocatorCreateInfo&$sel:heapSizeLimit:AllocatorCreateInfo($sel:vulkanFunctions:AllocatorCreateInfo'$sel:recordSettings:AllocatorCreateInfo"$sel:instance':AllocatorCreateInfo)$sel:vulkanApiVersion:AllocatorCreateInfo6$sel:typeExternalMemoryHandleTypes:AllocatorCreateInfoRecordSettings$sel:flags:RecordSettings$sel:filePath:RecordSettingsRecordFlagBits RecordFlagsVulkanFunctions2$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:VulkanFunctionsAllocatorCreateFlagBitsAllocatorCreateFlagsDeviceMemoryCallbacks&$sel:pfnAllocate:DeviceMemoryCallbacks"$sel:pfnFree:DeviceMemoryCallbacks#$sel:userData:DeviceMemoryCallbacksPFN_vmaFreeDeviceMemoryFunctionFN_vmaFreeDeviceMemoryFunction#PFN_vmaAllocateDeviceMemoryFunction"FN_vmaAllocateDeviceMemoryFunction Allocator'VIRTUAL_ALLOCATION_CREATE_STRATEGY_MASK8VIRTUAL_ALLOCATION_CREATE_STRATEGY_MIN_FRAGMENTATION_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_BUDDY_ALGORITHM_BIT)VIRTUAL_BLOCK_CREATE_LINEAR_ALGORITHM_BIT DEFRAGMENTATION_FLAG_INCREMENTALPOOL_CREATE_ALGORITHM_MASKPOOL_CREATE_BUDDY_ALGORITHM_BIT POOL_CREATE_LINEAR_ALGORITHM_BIT/POOL_CREATE_IGNORE_BUFFER_IMAGE_GRANULARITY_BITALLOCATION_CREATE_STRATEGY_MASK0ALLOCATION_CREATE_STRATEGY_MIN_FRAGMENTATION_BIT'ALLOCATION_CREATE_STRATEGY_MIN_TIME_BIT)ALLOCATION_CREATE_STRATEGY_MIN_MEMORY_BIT(ALLOCATION_CREATE_STRATEGY_FIRST_FIT_BIT(ALLOCATION_CREATE_STRATEGY_WORST_FIT_BIT'ALLOCATION_CREATE_STRATEGY_BEST_FIT_BIT#ALLOCATION_CREATE_WITHIN_BUDGET_BITALLOCATION_CREATE_DONT_BIND_BIT#ALLOCATION_CREATE_UPPER_ADDRESS_BIT+ALLOCATION_CREATE_USER_DATA_COPY_STRING_BIT)ALLOCATION_CREATE_CAN_MAKE_OTHER_LOST_BIT%ALLOCATION_CREATE_CAN_BECOME_LOST_BITALLOCATION_CREATE_MAPPED_BIT$ALLOCATION_CREATE_NEVER_ALLOCATE_BIT&ALLOCATION_CREATE_DEDICATED_MEMORY_BIT!MEMORY_USAGE_GPU_LAZILY_ALLOCATEDMEMORY_USAGE_CPU_COPYMEMORY_USAGE_GPU_TO_CPUMEMORY_USAGE_CPU_TO_GPUMEMORY_USAGE_CPU_ONLYMEMORY_USAGE_GPU_ONLYMEMORY_USAGE_UNKNOWNRECORD_FLUSH_AFTER_CALL_BIT(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 withAllocatordestroyAllocatorgetAllocatorInfogetPhysicalDevicePropertiesgetMemoryPropertiesgetMemoryTypePropertiessetCurrentFrameIndexcalculateStats getBudgetbuildStatsStringfreeStatsStringfindMemoryTypeIndex findMemoryTypeIndexForBufferInfofindMemoryTypeIndexForImageInfo createPoolwithPool destroyPool getPoolStatsmakePoolAllocationsLostcheckPoolCorruption getPoolName setPoolNameallocateMemory withMemoryallocateMemoryPageswithMemoryPagesallocateMemoryForBufferwithMemoryForBufferallocateMemoryForImagewithMemoryForImage freeMemoryfreeMemoryPagesgetAllocationInfotouchAllocationsetAllocationUserDatacreateLostAllocationwithLostAllocation mapMemorywithMappedMemory unmapMemoryflushAllocationinvalidateAllocationflushAllocationsinvalidateAllocationscheckCorruptiondefragmentationBeginwithDefragmentationdefragmentationEndbeginDefragmentationPassuseDefragmentationPassendDefragmentationPass defragmentbindBufferMemorybindBufferMemory2bindImageMemorybindImageMemory2 createBuffer withBuffercreateBufferWithAlignment destroyBuffer createImage withImage destroyImagecreateVirtualBlockwithVirtualBlockdestroyVirtualBlockisVirtualBlockEmptygetVirtualAllocationInfovirtualAllocatewithVirtualAllocation virtualFreeclearVirtualBlocksetVirtualAllocationUserDatacalculateVirtualBlockStatsbuildVirtualBlockStatsStringfreeVirtualBlockStatsString$fShowAllocator$fZeroDeviceMemoryCallbacks$fStorableDeviceMemoryCallbacks"$fFromCStructDeviceMemoryCallbacks $fToCStructDeviceMemoryCallbacks$fReadAllocatorCreateFlagBits$fShowAllocatorCreateFlagBits$fZeroVulkanFunctions$fStorableVulkanFunctions$fFromCStructVulkanFunctions$fToCStructVulkanFunctions$fReadRecordFlagBits$fShowRecordFlagBits$fZeroRecordSettings$fFromCStructRecordSettings$fToCStructRecordSettings$fZeroAllocatorCreateInfo $fFromCStructAllocatorCreateInfo$fToCStructAllocatorCreateInfo$fZeroAllocatorInfo$fStorableAllocatorInfo$fFromCStructAllocatorInfo$fToCStructAllocatorInfo$fZeroStatInfo$fStorableStatInfo$fFromCStructStatInfo$fToCStructStatInfo $fZeroStats$fStorableStats$fFromCStructStats$fToCStructStats $fZeroBudget$fStorableBudget$fFromCStructBudget$fToCStructBudget $fShowPool$fReadMemoryUsage$fShowMemoryUsage$fReadAllocationCreateFlagBits$fShowAllocationCreateFlagBits$fZeroAllocationCreateInfo$fStorableAllocationCreateInfo!$fFromCStructAllocationCreateInfo$fToCStructAllocationCreateInfo$fReadPoolCreateFlagBits$fShowPoolCreateFlagBits$fZeroPoolCreateInfo$fStorablePoolCreateInfo$fFromCStructPoolCreateInfo$fToCStructPoolCreateInfo$fZeroPoolStats$fStorablePoolStats$fFromCStructPoolStats$fToCStructPoolStats$fShowAllocation$fZeroAllocationInfo$fStorableAllocationInfo$fFromCStructAllocationInfo$fToCStructAllocationInfo$fShowDefragmentationContext$fReadDefragmentationFlagBits$fShowDefragmentationFlagBits$fZeroDefragmentationInfo2!$fFromCStructDefragmentationInfo2$fToCStructDefragmentationInfo2!$fZeroDefragmentationPassMoveInfo%$fStorableDefragmentationPassMoveInfo($fFromCStructDefragmentationPassMoveInfo&$fToCStructDefragmentationPassMoveInfo$fZeroDefragmentationPassInfo!$fStorableDefragmentationPassInfo$$fFromCStructDefragmentationPassInfo"$fToCStructDefragmentationPassInfo$fZeroDefragmentationInfo$fStorableDefragmentationInfo $fFromCStructDefragmentationInfo$fToCStructDefragmentationInfo$fZeroDefragmentationStats$fStorableDefragmentationStats!$fFromCStructDefragmentationStats$fToCStructDefragmentationStats $fReadVirtualBlockCreateFlagBits $fShowVirtualBlockCreateFlagBits$fZeroVirtualBlockCreateInfo#$fFromCStructVirtualBlockCreateInfo!$fToCStructVirtualBlockCreateInfo%$fReadVirtualAllocationCreateFlagBits%$fShowVirtualAllocationCreateFlagBits!$fZeroVirtualAllocationCreateInfo%$fStorableVirtualAllocationCreateInfo($fFromCStructVirtualAllocationCreateInfo&$fToCStructVirtualAllocationCreateInfo$fZeroVirtualAllocationInfo$fStorableVirtualAllocationInfo"$fFromCStructVirtualAllocationInfo $fToCStructVirtualAllocationInfo$fShowVirtualBlock$fEqVirtualBlock$fOrdVirtualBlock$fStorableVirtualBlock$fZeroVirtualBlock$fIsHandleVirtualBlock#$fEqVirtualAllocationCreateFlagBits$$fOrdVirtualAllocationCreateFlagBits)$fStorableVirtualAllocationCreateFlagBits%$fZeroVirtualAllocationCreateFlagBits%$fBitsVirtualAllocationCreateFlagBits+$fFiniteBitsVirtualAllocationCreateFlagBits$fEqVirtualBlockCreateFlagBits$fOrdVirtualBlockCreateFlagBits$$fStorableVirtualBlockCreateFlagBits $fZeroVirtualBlockCreateFlagBits $fBitsVirtualBlockCreateFlagBits&$fFiniteBitsVirtualBlockCreateFlagBits$fEqDefragmentationStats$fEqDefragmentationInfo$fEqDefragmentationPassInfo$fEqDefragmentationPassMoveInfo$fEqDefragmentationFlagBits$fOrdDefragmentationFlagBits!$fStorableDefragmentationFlagBits$fZeroDefragmentationFlagBits$fBitsDefragmentationFlagBits#$fFiniteBitsDefragmentationFlagBits$fEqDefragmentationContext$fOrdDefragmentationContext $fStorableDefragmentationContext$fZeroDefragmentationContext $fIsHandleDefragmentationContext$fEqAllocation$fOrdAllocation$fStorableAllocation$fZeroAllocation$fIsHandleAllocation $fEqPoolStats$fEqPoolCreateFlagBits$fOrdPoolCreateFlagBits$fStorablePoolCreateFlagBits$fZeroPoolCreateFlagBits$fBitsPoolCreateFlagBits$fFiniteBitsPoolCreateFlagBits$fEqAllocationCreateFlagBits$fOrdAllocationCreateFlagBits"$fStorableAllocationCreateFlagBits$fZeroAllocationCreateFlagBits$fBitsAllocationCreateFlagBits$$fFiniteBitsAllocationCreateFlagBits$fEqMemoryUsage$fOrdMemoryUsage$fStorableMemoryUsage$fZeroMemoryUsage$fEqPool $fOrdPool$fStorablePool $fZeroPool$fIsHandlePool $fEqBudget $fEqStatInfo$fEqAllocatorInfo$fEqRecordFlagBits$fOrdRecordFlagBits$fStorableRecordFlagBits$fZeroRecordFlagBits$fBitsRecordFlagBits$fFiniteBitsRecordFlagBits$fEqVulkanFunctions$fEqAllocatorCreateFlagBits$fOrdAllocatorCreateFlagBits!$fStorableAllocatorCreateFlagBits$fZeroAllocatorCreateFlagBits$fBitsAllocatorCreateFlagBits#$fFiniteBitsAllocatorCreateFlagBits $fEqAllocator$fOrdAllocator$fStorableAllocator$fZeroAllocator$fIsHandleAllocator$fShowVirtualAllocationInfo!$fShowVirtualAllocationCreateInfo$fShowVirtualBlockCreateInfo$fShowDefragmentationStats$fShowDefragmentationInfo$fShowDefragmentationPassInfo!$fShowDefragmentationPassMoveInfo$fShowDefragmentationInfo2$fShowAllocationInfo$fShowPoolStats$fShowPoolCreateInfo$fShowAllocationCreateInfo $fShowBudget $fShowStats$fShowStatInfo$fShowAllocatorInfo$fShowAllocatorCreateInfo$fShowRecordSettings$fShowVulkanFunctions$fShowDeviceMemoryCallbacks