VulkanMemoryAllocator VS vulkan-guide

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.

I totally agree, and so do the people working on it as well as some of the volunteers who write tutorials.

There's an ongoing effort to create beginner friendly introductory material which was discussed in the recent Vulkanised conference. And an effort to make a better documentation site that's easier to browse than the specification.

On the volunteer front, there's a Vulkan 1.3 -based introductory tutorial (work in progress) over at https://vkguide.dev/

I think there should be a Vulkan tutorial that doesn't start with the boring stuff of initialization and window creation. It's stuff that you write once and forget about, and nothing particularly interesting happens in it.

Looking at my hobby project, excluding the boring stuff (which is reusable), a "hello compute" example is around 100 LOC and a "hello triangle" around 120 LOC. GLSL shader sources included.

Maybe someday I'll get around to writing a "learn Vulkan the hard way" blog post with examples.

Also, use https://vkguide.dev/ rather than vulkan-tutorial.

Once you're beyond the "introductory" phase, resources become more specialized based on what you'd like to learn -- there are Vulkan tutorials like https://vkguide.dev/ which will teach you the API and also give a bit more insight in how modern GPU hardware is structured, there are books like the "GPU Zen" series that do deep-dives on specific techniques, and there are tons of recorded GDC and SIGGRAPH talks on interesting new techniques. :)

Personally, I'm a hands on learner who actually wants to use this stuff in my career, so I'd recommend these tutorials: https://learnopengl.com/ https://vulkan-tutorial.com/Overview https://vkguide.dev/

vkguide teaches some good practices regarding code/renderer structure, but I'm afraid it doesn't go as deep as you'd like. It's certainly deeper than most other tutorials, though.

https://vkguide.dev/ This is my favorite.