Replies: 1 comment
-
|
It's probably not necessary to enable these extensions that have been promoted to core. However, the Vulkan features from these extensions (storageBuffer16BitAccess, shaderFloat16) are not required to be supported in a Vulkan 1.2 implementation, so we still need to check for their support and enable them. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I’m new to Vulkan and I had a small question while running with validation layers enabled.
I noticed that Vulkan validation prints warnings about enabling extensions like
VK_KHR_shader_float16_int8 / VK_KHR_16bit_storage,
mentioning that they have already been promoted to core (Vulkan 1.2 / 1.1).
Validation Warning: [ BestPractices-deprecated-extension ] | MessageID = 0xda8260ba
vkCreateDevice(): Attempting to enable deprecated extension VK_KHR_16bit_storage, but this extension has been promoted t
o 1.1.0 (0x00401000).
Objects: 1
[0] VkInstance 0x28d88f8cca0
Validation Warning: [ BestPractices-deprecated-extension ] | MessageID = 0xda8260ba
vkCreateDevice(): Attempting to enable deprecated extension VK_KHR_shader_float16_int8, but this extension has been prom
oted to 1.2.0 (0x00402000).
Objects: 1
[0] VkInstance 0x28d88f8cca0
Since the project seems to require Vulkan 1.2+ anyway,
I was wondering if there is a specific reason these KHR extensions are still explicitly enabled.
Is it for backward compatibility, driver quirks, or just leftover code that hasn’t been cleaned up yet.
Sorry if this is a basic question
just trying to understand the design choices better.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions