Repository navigation
Fix Vulkan header selection in fresh demo installs - #22
Merged
Merged
Conversation
This was referenced Oct 7, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fresh installations can select an older Vulkan SDK header before the headers bundled with
antono2.vulkan, producing unknown extension types. Let the binding supply its matching headers and Volk loader. Also use the same mutable Window parameter convention as the backend, avoiding an extra indirection under V3.Validated on Linux with the published Vulkan v3.2.0 and GLFW v2.0.0 modules, ImGui master, and GCC: compatibility compilation and five-frame rendering through Xvfb/Lavapipe pass. Current V3 compilation passes but rendering still crashes later in swapchain creation; this change does not claim full V3 runtime support. Cross-platform checks run in CI.