-
Notifications
You must be signed in to change notification settings - Fork 385
Insights: GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator
Overview
-
- 4 Merged pull requests
- 0 Open pull requests
- 8 Closed issues
- 1 New issue
Could not load contribution data
Please try again later
1 Release published by 1 person
-
v3.3.0
published
May 12, 2025
4 Pull requests merged by 1 person
-
Small improvement of 'advanced data uploading' exampe in docs
#494 merged
May 22, 2025 -
Small improvements of tests
#496 merged
May 22, 2025 -
Use a cache instead of downloading Vulkan SDK with every CI run
#491 merged
May 12, 2025 -
Use a clang-tidy configuration file
#488 merged
May 9, 2025
8 Issues closed by 2 people
-
Question: Is the documentation section "Allocation algorithm" still up to date?
#492 closed
May 12, 2025 -
Cache Vulkan SDK in GitHub workflow
#490 closed
May 12, 2025 -
Add some warnings from clang-tidy to ignore list
#484 closed
May 9, 2025 -
Problem with ProcessDefragmentationPass on AMD Ryzen™ 9 7950X
#339 closed
May 9, 2025 -
fallback to dedicated allocation can skip budget/maxMemoryAllocationCount checks?
#278 closed
May 7, 2025 -
Not compiling when VMA_EXTERNAL_MEMORY_WIN32 disabled.
#448 closed
May 6, 2025 -
Use GitHub actions for continuous integration
#467 closed
May 6, 2025
1 Issue opened by 1 person
-
Resizable VmaVirtualBlocks
#495 opened
May 19, 2025
2 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Improve section "Recommended usage patterns" in docs
#475 commented on
May 9, 2025 • 0 new comments -
do not create a dummy buffer and destroy when call vmaFindMemoryTypeIndexForBufferInfo
#419 commented on
May 17, 2025 • 0 new comments