@qbojj, thank you for posting this issue, could you please provide more information according to your needs, I am still a little confused about this feature.

Essentially, Imgui_ImplVulkan normally links with a dynamic library (Vulkan loader) by default. However, there's an option called IMGUI_IMPL_VULKAN_NO_PROTOTYPES that makes it utilize dynamically loaded functions through the ImGui_ImplVulkan_LoadFunctions function, which is a standard practice for Vulkan libraries.

The issue arose when I was using SDL_Vulkan_GetVkGetInstanceProcAddr alongside a debugging tool that was injecting itself into the get-proc-addr. In this scenario, Imgui was utilizing a non-injected version of vulkan, causing some problems.

To address this, I would expect there to be a second port that also defines the IMGUI_IMPL_VULKAN_NO_PROTOTYPES , ensuring consistency and compatibility with the rest of the program.

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

.

Due to the nature of this feature being an "alternative" (features that cannot be installed at the same time) which causes the dependency tree to bifurcate in a conflicting way. It isn't possible to implement it in the curated registry. The best option for you would be to create overlay ports for vulkan-bindings and imgui that disable prototypes.