diff --git a/.gitignore b/.gitignore index 875c4e4..cff4adc 100644 --- a/.gitignore +++ b/.gitignore @@ -1,5 +1,6 @@ /bin/* /build/* !/bin/VmaSample_Release_vs2019.exe +!/bin/VmaSample_Release_vs2022.exe !/bin/Shader*.spv .vscode/ diff --git a/CHANGELOG.md b/CHANGELOG.md index 0c438d6..5bd6460 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,4 +1,4 @@ -# 3.1.0 (TBD) +# 3.1.0 (2024-05-27) This release gathers fixes and improvements made during many months of continuous development on the main branch, mostly based on issues and pull requests on GitHub. diff --git a/README.md b/README.md index 805a0c4..c8997c8 100644 --- a/README.md +++ b/README.md @@ -146,7 +146,7 @@ The VulkanMemoryAllocator port in vcpkg is kept up to date by Microsoft team mem # Binaries -The release comes with precompiled binary executable for "VulkanSample" application which contains test suite. It is compiled using Visual Studio 2019, so it requires appropriate libraries to work, including "MSVCP140.dll", "VCRUNTIME140.dll", "VCRUNTIME140_1.dll". If the launch fails with error message telling about those files missing, please download and install [Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019](https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads), "x64" version. +The release comes with precompiled binary executable for "VulkanSample" application which contains test suite. It is compiled using Visual Studio 2022, so it requires appropriate libraries to work, including "MSVCP140.dll", "VCRUNTIME140.dll", "VCRUNTIME140_1.dll". If the launch fails with error message telling about those files missing, please download and install [Microsoft Visual C++ Redistributable](https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads), "X64" version. # Read more diff --git a/bin/VmaSample_Release_vs2019.exe b/bin/VmaSample_Release_vs2019.exe deleted file mode 100644 index f986fc8..0000000 Binary files a/bin/VmaSample_Release_vs2019.exe and /dev/null differ diff --git a/bin/VmaSample_Release_vs2022.exe b/bin/VmaSample_Release_vs2022.exe new file mode 100644 index 0000000..7e86cd2 Binary files /dev/null and b/bin/VmaSample_Release_vs2022.exe differ diff --git a/docs/html/custom_memory_pools.html b/docs/html/custom_memory_pools.html index d4a052c..805f019 100644 --- a/docs/html/custom_memory_pools.html +++ b/docs/html/custom_memory_pools.html @@ -182,7 +182,7 @@ When not to use custom pools
Many of the common concerns can be addressed in a different way than using custom pools:
bufferImageGranularity
limit automatically.nonCoherentAtomSize
limit automatically. It also maps only those VkDeviceMemory
blocks that need to map any allocation. It even tries to keep mappable and non-mappable allocations in separate blocks to minimize the amount of mapped memory.
- Vulkan Memory Allocator
-
- |
-
VK_WHOLE_SIZE
for all allocations.VK_WHOLE_SIZE
for all allocations.Version 3.1.0-development
+Version 3.1.0
Copyright (c) 2017-2024 Advanced Micro Devices, Inc. All rights reserved.
License: MIT
See also: product page on GPUOpen, repository on GitHub
VMA can automatically use following Vulkan extensions. If you found them availeble on the selected physical device and you enabled them while creating VkInstance
/ VkDevice
object, inform VMA about their availability by setting appropriate flags in VmaAllocatorCreateInfo::flags.
VMA can automatically use following Vulkan extensions. If you found them available on the selected physical device and you enabled them while creating VkInstance
/ VkDevice
object, inform VMA about their availability by setting appropriate flags in VmaAllocatorCreateInfo::flags.
Vulkan extension | VMA flag |
---|