Update VulkanMemoryAllocator to 3.1.0 #12821
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Is the glslang test file necessary? |
|
This version of VulkanMemoryAllocator contains fix 362 which fixes Vulkan backend hardware support in Raspberry Pi 5, potentially also for Raspberry Pi 4. |
I'm going to close this commit because I did something wrong. Make a commit but in addition to updating VMA, you will update Vulkan Headers (just delete the vulkan folder and copy the new files). The link: https://github.com/KhronosGroup/Vulkan-Headers |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I updated VulkanMemoryAllocator to version 3.1.0 released a few days ago.
With this new version I also had to update Vulkan.
I don't know if I should do this but I updated glslang.