WalnutAppTemplate
WalnutAppTemplate copied to clipboard
[vulkan] Debug report from ObjectType: 5
I keep getting a lot of console output, mostly this one repeating over and over again:
[vulkan] Debug report from ObjectType: 5 Message: Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01779 ] Object 0: handle = 0x967dd1000000000e, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x5717e75b | vkAcquireNextImageKHR(): Semaphore must not have any pending operations. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending (https://vulkan.lunarg.com/doc/view/1.3.275.0/windows/1.3-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01779)
Same problem.
I got the problem as well
I get two handles swapping each other each frame,
frame 1 has this handle: 0x967dd1000000000e
frame 2 has this handle: 0xdcc8fd0000000012
for the rest the entire message is the same a quick google for this debug error got me to this thread from dear ImGui which might be the issue, although, the place where the error takes place only uses the imgui vulkan window implementation (line which causes the error) also, the error specificly states
The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must not have any uncompleted signal or wait operations pending
and the line which causes the error uses VK_NULL_HANDLE. there are only things stated when it is not VK_NULL_HANDLE
I think this is either an issue with dear ImGui, or vulkan where walnut needs to find a workaround for, as this is a Walnut issue, and not a WalnutAppTemplate issue
Im gonna open a post there and link to this one, as it should be fixed there
Don't know if anyone is still having issues with this, but here is a quick fix for anyone dealing with issues regarding some [vulkan] Debug report from ObjectType: 5 related errors. There are multiple ways to handle this but if your just download an older sdk of Vulkan it should solve you problems. I personally just went back and used sdk version 1.3.126.0. If you prefer to use the most recent version of Vulkan this should fix your issue as well https://github.com/ocornut/imgui/issues/7236.
So you want to say that this is newer versions of vulkan that cause problem? Because i'm using right now version 1.4.304 and i've got the same problem. And no, it's not ImGui's fault, it's definitely vulkan itself related, because i removed ImGui from my project completely - error persisted
Btw it means that this problem is at least 3 years old, so we can only hope that this is gonna get fixed