We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have a feeling that even on vulkan >= 1.1, sometimes
vkGetPhysicalDeviceMemoryProperties2KHR is not found by the loader, unless the VK_KHR_get_physical_device_properties2 is enabled.
maybe could be a good idea to fallback to the "non"-khr version if the pointer is not found?
I'm using vma with #define VMA_STATIC_VULKAN_FUNCTIONS 0 #define VMA_DYNAMIC_VULKAN_FUNCTIONS 1
I pass instance and device pointers that I obtain from the vulkan-hpp dynamic dispatcher.
The text was updated successfully, but these errors were encountered:
Sorry, I think this might be a duplicate of #410
I think the underlying cause is a bug in the Nvidia driver implementation for linux.
Sorry, something went wrong.
No branches or pull requests
I have a feeling that even on vulkan >= 1.1, sometimes
vkGetPhysicalDeviceMemoryProperties2KHR is not found by the loader, unless the VK_KHR_get_physical_device_properties2 is enabled.
maybe could be a good idea to fallback to the "non"-khr version if the pointer is not found?
I'm using vma with
#define VMA_STATIC_VULKAN_FUNCTIONS 0
#define VMA_DYNAMIC_VULKAN_FUNCTIONS 1
I pass instance and device pointers that I obtain from the vulkan-hpp dynamic dispatcher.
The text was updated successfully, but these errors were encountered: