False positive legacy command validation warning for vkGetPhysicalDeviceProperties() after only calling vkEnumeratePhysicalDevices()

[Teedacrafter]

Environment:

• OS: Windows 11 Version 25H2
• Driver version: with Vulkan 1.4.344 and Driver: AMD 2.0.388
• SDK version: 1.4.341.1
• Options enabled: legacy-gpdp2

The Issue

After calling vkEnumeratePhysicalDevices() while legacy-gpdp2 layer enabled I get the legacy warning

vkGetPhysicalDeviceProperties(): vkGetPhysicalDeviceProperties is a legacy command and this VkInstance was created with VK_VERSION_1_1 which contains vkGetPhysicalDeviceProperties2 that can be used instead.

with the MessageID 0xde900250.

The legacy warning still works if calling vkGetPhysicalDeviceProperties(). It just should not do the same as for the vkEnumeratePhysicalDevices() call.

[spencer-lunarg]

So this is most likely a layer, that is between your app and Validation, calling vkGetPhysicalDeviceProperties for you

VVL has zero way to know "where" the function is being called from

[Teedacrafter]

The layer callstack is not showing any additional layer that sits in between. Its just the validation layer as printed by the validation layer:

   <Application>
     ||
   <Loader>
     ||
   VK_LAYER_KHRONOS_validation
           Type: Explicit
           Enabled By: Loader Settings File (Vulkan Configurator)
           Manifest: C:\VulkanSDK\1.4.341.1\Bin\VkLayer_khronos_validation.json
           Library:  C:\VulkanSDK\1.4.341.1\Bin\VkLayer_khronos_validation.dll
     ||
   <Device>

[spencer-lunarg]

So I wrote this

#include <VkBootstrap.h>

int main() {
    vkb::InstanceBuilder instance_builder;
    auto instance_ret = instance_builder.use_default_debug_messenger()
                            .set_headless()
                            .build();
    vkb::Instance instance = instance_ret.value();

    vkb::InstanceDispatchTable inst_disp = instance.make_table();

    uint32_t count = 0;
    inst_disp.fp_vkEnumeratePhysicalDevices(instance, &count, nullptr);

    return 0;
}

and with just API Dump as a layer I see

vkCreateInstance()
vkCreateDebugUtilsMessengerEXT()
vkEnumeratePhysicalDevices()

and turning on VK_LAYER_LEGACY_DETECTION I see no false positive

---

The legacy detection layer code is "dump simple", it only calls on PreCallValidateGetPhysicalDeviceProperties so if someone is not calling vkGetPhysicalDeviceProperties it won't report an issue

Could you provide either

1. An API dump of what happens to see if there is a hidden vkGetPhysicalDeviceProperties being called somewhere
2. A simple program to reproduce

I will note, on Linux I know that the VK_LAYER_MESA_device_select will call vkGetPhysicalDeviceProperties for you

[Teedacrafter]

I found that the false positive will trigger (at least on my system) if the Legacy Detection is on and the Vulkan Configurator (mine is on version 3.4.2-20260203) Window is opened.

[spencer-lunarg]

I guess the only thing I could ask from here is to use Debug Break and see the callstack of who is hitting that

[Teedacrafter]

Yea so turning VK_LAYER_LEGACY_DETECTION on does nothing (can check that yourself if vkGetPhysicalDeviceProperties() triggers a warning) but even if i just enable this with the layer setting without the Configurator i still get the error message whiel enumerating physical devices.
The callstacks shows too that the validation layer is calling vkGetPhysicalDeviceProperties() probably to cache stuff for future validation checks and stuff like this but it gets conflicted with the legacy detection but I dont know for sure.

[spencer-lunarg]

The callstacks shows too that the validation layer is calling vkGetPhysicalDeviceProperties() probably to cache stuff for future validation checks and stuff like this but it gets conflicted with the legacy detection but I dont know for sure.

Can you provide the call stack, the internal calls of Validation Layers should not be going through the "PreCallValidate" calls (we don't currently validate internal calls)

[Teedacrafter]

Yes. This is the callstack:

VkLayer_khronos_validation.dll!MessengerBreakCallback(VkDebugUtilsMessageSeverityFlagBitsEXT message_severity, unsigned int message_type, const VkDebugUtilsMessengerCallbackDataEXT * callback_data, void * user_data) Line 727
VkLayer_khronos_validation.dll!DebugReport::LogMessage(unsigned int msg_flags, std::basic_string_view<char,std::char_traits<char>> vuid_text, const LogObjectList & objects, const Location & loc, const std::string & main_message) Line 239
[Inline Frame] VkLayer_khronos_validation.dll!DebugReport::LogMessageVaList(unsigned int) Line 713
VkLayer_khronos_validation.dll!Logger::LogWarning(std::basic_string_view<char,std::char_traits<char>> vuid_text, const LogObjectList & objlist, const Location & loc, const char * format, ...) Line 308
VkLayer_khronos_validation.dll!legacy::Instance::PreCallValidateGetPhysicalDeviceProperties(VkPhysicalDevice_T * physicalDevice, VkPhysicalDeviceProperties * pProperties, const ErrorObject & error_obj) Line 113
VkLayer_khronos_validation.dll!vulkan_layer_chassis::GetPhysicalDeviceProperties(VkPhysicalDevice_T * physicalDevice, VkPhysicalDeviceProperties * pProperties) Line 292
[External Code]
app.exe!main() Line 18

[spencer-lunarg]

So this is showing vulkan_layer_chassis::GetPhysicalDeviceProperties which is our entry point for vkGetPhysicalDeviceProperties ... like this is the hook into the validation layer itself

so this is showing that someone (likely the [External Code]) is calling vkGetPhysicalDeviceProperties

[Teedacrafter]

The only trace i see is the amdvlk64.dll where validation function is beeing called from

[spencer-lunarg]

I'm on linux, let me try my Windows AMD laptop with my example, see if I can reproduce it