Access violation in volkInitialize about volk HOT 2 CLOSED

Something like this can happen due to symbol conflicts if your final executable includes a dependency on libvulkan1.dll (which is both redundant and prohibited when volk is used). It's possible that the presence or absence of some code in your executable causes a change in linking order somehow which makes this issue dependent on seemingly unrelated code. The libvulkan1.dll dependency could come directly from CMake settings or possibly from a dependency?

I would also recommend updating to latest volk; I think you're using 1.3.256, and there was a possibly related issue in volk's own CMakeLists.txt that could manifest depending on the configuration, which was fixed in 3f3e0cb (1.3.261 and later)

from volk.

Good call! I updated to the latest volk and the issue stopped. Thanks for the help!

from volk.