vulkan-guide
VulkanMemoryAllocator
Our great sponsors
vulkan-guide | VulkanMemoryAllocator | |
---|---|---|
67 | 11 | |
806 | 2,373 | |
- | 2.5% | |
9.0 | 8.3 | |
about 12 hours ago | 23 days ago | |
SCSS | C | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vulkan-guide
-
NVK is now ready for prime time
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.
- LearnD3D11, a guide aimed at anyone trying to learn Direct3D11
-
Struggling to Update Vertex Buffer via Staging Buffer
Also, use https://vkguide.dev/ rather than vulkan-tutorial.
-
What are the best textbooks/resources for learning graphics programming practically in 2023?
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. :)
- Where do I start learning graphics programming?
-
Yuzu Ea 3608 is out!
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/
-
Theory on structuring graphics projects, building interfaces, and designing abstractions?
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.
-
"reportedly Apple just got absolutely everything they asked for and WebGPU really looks a lot like Metal. But Metal was always reportedly the nicest of the three modern graphics APIs to use, so that's… good?"
https://vkguide.dev/ This is my favorite.
- Extension VK_KHR_swapchain not found in list of known instance extensions
- Resources to build a game engine from scratch?
VulkanMemoryAllocator
-
Why do I need to load VMA vulkan functions dynamically?
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.
-
Managing Vertex Buffers
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
-
[Part 7] Update of my Vulkan renderer: LODs, Multiple different meshes, Memory Allocator, Render architecture and more
Integrated Vulkan Memory Allocator, making all GPU memory allocations much easier to work with.
-
Is it a good idea to use VMA for memory management for production?
Seems like it was initially added more than 2 years ago, they really should release more often :P
-
Vulkan 1.3 released
Use VMA, originally created by AMD, never worry about device memory and device memory alignment again.
-
Low bandwidth using memcpy
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.
-
Need advices over OpenGL/Vulkan abstraction
Repo for Vulkan Memory mangement (AMD): https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator
-
Deleting staging buffer after copying to image causes weird artifacts in texture mapping
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.
-
Allocating multi-layered images with a huge amount of layers
Alternatively, you could just use an existing allocator library, a popular choice is VMA: https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator
-
Memory management doubts
Personally, I'd recommend (VMA)[https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator] if you don't want to deal with all of this yourself.
What are some alternatives?
vk-bootstrap - Vulkan Bootstrapping Iibrary
volk - Meta loader for Vulkan API
raylib - A simple and easy-to-use library to enjoy videogames programming
buddy_alloc - A single header buddy memory allocator for C & C++
bgfx - Cross-platform, graphics API agnostic, "Bring Your Own Engine/Framework" style rendering library.
doon-vk - Personal exploration of the Vulkan API
Vulkan - Examples and demos for the new Vulkan API
bdwgc - The Boehm-Demers-Weiser conservative C/C++ Garbage Collector (bdwgc, also known as bdw-gc, boehm-gc, libgc)
SDL - Simple Directmedia Layer
SPP
SPIRV-Reflect - SPIRV-Reflect is a lightweight library that provides a C/C++ reflection API for SPIR-V shader bytecode in Vulkan applications.
OCRA - Overly Complicated Rendering Abstraction