tuket
New Member
Hello,
I'm a software developer and I'm using Vulkan to make an application.
A few days ago, I noticed a weird problem with validation layers: I started getting some weird validation errors that didn't make sense. I tested some of my old sample applications that used to be totally clean of validation errors - the errors were also present on them.
I started debugging and found out that, even though I was creating a Vulkan instance with API version 1.0, the validation layer callback was receiving version 1.1! This creates a lot of issues because the validation layers think they are allowed to call 1.1 functions, and that leads to undefined behaviour.
This issue started happening (I think) after updating my Nvidia drivers. That made me think it was a new driver issue, so I reported the bug to Nvidia. After interchanging messages with a nice engineer from Nvidia for a few days, we realized that VK_LAYER_OBS_HOOK was the culprit. Disabling that layer fixes the issue.
I'm a software developer and I'm using Vulkan to make an application.
A few days ago, I noticed a weird problem with validation layers: I started getting some weird validation errors that didn't make sense. I tested some of my old sample applications that used to be totally clean of validation errors - the errors were also present on them.
I started debugging and found out that, even though I was creating a Vulkan instance with API version 1.0, the validation layer callback was receiving version 1.1! This creates a lot of issues because the validation layers think they are allowed to call 1.1 functions, and that leads to undefined behaviour.
This issue started happening (I think) after updating my Nvidia drivers. That made me think it was a new driver issue, so I reported the bug to Nvidia. After interchanging messages with a nice engineer from Nvidia for a few days, we realized that VK_LAYER_OBS_HOOK was the culprit. Disabling that layer fixes the issue.