vulkanizer VS VulkanMemoryAllocator

You can find its implementation on my GitHub page and you can follow me on Twitter for more graphics related stuff.

You can follow my progress on Twitter and Git. You can find more screenshots and videos over there.

You can follow my journey on Twitter and GitHub.

Part 2 update of my new toy Vulkan renderer: Implemented Programmable Vertex Fetching, Vertex size is significantly smaller now (12 Bytes), Normals use only two 8 bit vector components where the third component gets reconstructed in the shader, Vertex positions and UVs are 2 Bytes in size, started using VK_KHR_push_descriptor which is much nicer to work with compared to traditional descriptor sets. Sebastian Aaltonen gave a very good explanation for Programmable Vertex Fetching. Normals use only two 8 bit vector components where the third component is reconstructed in the shader. You can follow my journey on Twitter and Git.

I recently started working on my toy Vulkan renderer. The plan is to implement many modern graphics and Vulkan features along the way. As a starting point I made a single mesh renderer and basic CPU/GPU profiler. You can follow my journey on Twitter and Git.

Hello - working on a Vulkan renderer and I ran into a topic I don't understand. I use the Vulkan Memory Allocator and upon updating my local targeted Vulkan SDK to 1.3.250 from 1.3.204, I receive exactly the same error as this user: https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator/issues/280 Error: The procedure entry point vkGetDeviceBufferMemoryRequirements could not be located in the DLL.

For problem 1 I would recommend looking into Vulkan Memory Allocator: https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator The general idea is to allocate large chunks of memory, then sub-allocate out of those when buffers are required. This is nice for several reasons: - Memory allocation can be slow and involve system calls. Sub-allocating does not require system calls - Your memory will be more cache-friendly as all your buffers will be relatively adjacent - There is a finite number of unique allocations you can have. Performing larger allocations keeps your usage lower

Integrated Vulkan Memory Allocator, making all GPU memory allocations much easier to work with.

Seems like it was initially added more than 2 years ago, they really should release more often :P

Use VMA, originally created by AMD, never worry about device memory and device memory alignment again.

I am using VMA for memory allocation with the VMA_MEMORY_USAGE_GPU_TO_CPU usage flag. That means that the flags VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT and VK_MEMORY_PROPERTY_HOST_CACHED_BIT are already set.

Repo for Vulkan Memory mangement (AMD): https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator

Since it's a header-only lib, you could always try cloning the latest from [GitHub](https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator) and see if the problem continues with that version.

Alternatively, you could just use an existing allocator library, a popular choice is VMA: https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator

Personally, I'd recommend (VMA)[https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator] if you don't want to deal with all of this yourself.