New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vulkan commandbuffer compliance issue on Mesa::RADV/ANV/AMDVLK #95
Comments
Looks like this is the result of 'running' variable in the CommandBuffer.cpp always being 0 allowing vkBeginCommandBuffer() to run no matter if the buffer shouldn't be available! Log::Out("Command buffer!", running,"\n"); Always drops 'Command buffer!0' no matter what |
Hi, is there some updates ? I'm currently having the same issue, and I am trying to figure how to fix it (unsuccessfully). |
Turned on VK_LAYER_LUNARG_standard_validation and got this in terminal on Linux machines:
Calling vkBeginCommandBuffer() on active VkCommandBuffer 0x559a114172d0[] before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state. (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
Interesting to note that RADV does it much more frequently than AMDVLK.
Is everything being fenced properly?
Hardware:
The text was updated successfully, but these errors were encountered: