Quake3e VS volk

```The Quake3e source port (https://github.com/ec-/Quake3e) is included.

Quake3e

you need a source port, like quake3e

It's there : https://github.com/ec-/Quake3e/releases

quake3e is vastly superior to ioq3

Im learning Vulkan in attempt to create a renderer for a video game I plan on making. Following the spec https://registry.khronos.org/vulkan/specs/1.0/html/vkspec.html, I've reached the point to where I can create and destroy the VkInstance. I'm using GLFW for the windowing and was originally using for the Vulkan stuff, but turned to Volk https://github.com/zeux/volk to load Vulkan in the end. Reflecting that change, I replace the vulkan.h includes with volk.h, defined the platform macro for my platform, and unlinked Vulkan in my Makefile.

Do you link libVulkan-1.so statically in your project? On Android, only Vulkan 1.0 functions are exposed via this lib. Performance wise and to use any Vulkan functions above 1.0 you need to load all your Vulkan functions by yourself or (even better) use a loader library like volk

no problem! This library might help you too https://github.com/zeux/volk

You also should not link to Vulkan directly (-lvulkan) but retrieve the function pointers to the Vulkan functions by yourself or using a loder library like volk.

You can't statically link vulkan, you need to load vulkan-1.dll from the driver installation. You can use something like volk for this https://github.com/zeux/volk

Use a Vulkan loader like Volk. https://github.com/zeux/volk

For developing with Vulkan all you need are the Vulkan Headers and some kind of static loader to link against or you use a dynamic loader like volk.

I am using VMA as well in my renderer and I am not having any issues with it. As I am using Volk (https://github.com/zeux/volk) to locate and load all Vulkan function pointers. Thats why I need to tell VMA to not load any functions statically: