vkOcclusionTest VS Vulkan-ValidationLayers

Holy S**T I feel like such an idiot. This fixes it for me. Turns out I understood vulkan just fine, but I did not understand C++.. Commit with the fix: here

If this works then it might actually be a game bug and the game I guess passes invalid shaders when the cache exists... but it seems to work fine on windows vulkan drivers. You could try to run the game with https://github.com/KhronosGroup/Vulkan-ValidationLayers

For debugging these kinds of issues, I would recommend enabling the synchronization validation layer.

I would use the debugger to produce a stack trace and look into the validation layers source code. https://github.com/KhronosGroup/Vulkan-ValidationLayers Then I would either file an issue or make a PR there.

Currently validation layers might generate false-positive errors: https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/3450

A'rightey... I was able to reproduce this issue with Sascha Willems basic triangle example, so I am fairly certain, that this is a bug. I've opened an issue.

I am really at loss here, I found this issue but it doesn't really help me (I am starting to doubt it's even possible, maybe I'm a clown and doing it wrong...)

Can you post a reproduction case at https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues so we can take a look at it.

Which is why a GPU debugger with frame tracing is so much better option.

By the way, there are actually ways to expose a print function on shader code, provided there is driver support.

https://github.com/KhronosGroup/Vulkan-ValidationLayers/blob...

Huh yeah. Looking through the header the function you want works with c but there are others using c++ features. The reason given is understandable.