From 21383ef2596e4464312caa7f3765bbf93b0b071d Mon Sep 17 00:00:00 2001
From: Codotaku <88196711+CodesOtakuYT@users.noreply.github.com>
Date: Sat, 3 Jun 2023 23:46:05 +0100
Subject: [PATCH] load the instance proc addr from vkb instead of the loader

Am honestly not sure if this is objectively better, but I can imagine that it's cleaner to rely on GLFW proc only to load the vkb. then rely on the vkb for everything else after that.
Feedback is appreciated!
---
 examples/graphics_context.zig | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/examples/graphics_context.zig b/examples/graphics_context.zig
index 0da4db7..0021e6f 100644
--- a/examples/graphics_context.zig
+++ b/examples/graphics_context.zig
@@ -7,6 +7,7 @@ const required_device_extensions = [_][*:0]const u8{vk.extension_info.khr_swapch
 
 const BaseDispatch = vk.BaseWrapper(.{
     .createInstance = true,
+    .getInstanceProcAddr = true,
 });
 
 const InstanceDispatch = vk.InstanceWrapper(.{
@@ -114,7 +115,7 @@ pub const GraphicsContext = struct {
             .pp_enabled_extension_names = @ptrCast([*]const [*:0]const u8, glfw_exts),
         }, null);
 
-        self.vki = try InstanceDispatch.load(self.instance, c.glfwGetInstanceProcAddress);
+        self.vki = try InstanceDispatch.load(self.instance, self.vkb.dispatch.vkGetInstanceProcAddr);
         errdefer self.vki.destroyInstance(self.instance, null);
 
         self.surface = try createSurface(self.instance, window);