You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was able to get the validation layer hooked up. I've attached the output vulkan.log
VUID-vkCmdBindPipeline-commandBuffer-recording(ERROR / SPEC): msgNum: -365328357 - Validation Error: [ VUID-vkCmdBindPipeline-commandBuffer-recording ] Object 0: handle = 0x7f6c90da52b0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0xea39881b | You must call vkBeginCommandBuffer() before this call to vkCmdBindPipeline(). The Vulkan spec states: commandBuffer must be in the recording state (https://vulkan.lunarg.com/doc/view/1.2.148.0/linux/1.2-extensions/vkspec.html#VUID-vkCmdBindPipeline-commandBuffer-recording)
So it seems the command buffers aren't activated when they should be. Not sure if more concurrency control is needed? Maybe merging mainline dolphin's CommandBufferManager would fix it?
I also found that this was the latest commit on CommandBufferManager.cpp and it says vulkan is broken because post processing is not finished yet. Am I wasting my time trying to debug this or is that statement outdated? @Tinob
program aborts ~1sec after entering full screen while using vulkan backend
running pop os 20.04 with nvidia-450 vulkan 1.2.148 on a gtx 970m
stack trace:
The full stack trace is attached here.
I tried to link the vulkan sdk to get more info, but wasn't able to manage it. Is there a guide for that?
Let me know if I can provide more info or if there's any methodology for debugging I could try. Thanks!
The text was updated successfully, but these errors were encountered: