Vulkan flickering for small meshes [closed] - c++

Question

Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 3 years ago.
Improve this question
I am rendering different models. Big models (more than a thousand triangles) are rendered without issue, however small models(a single triangle, or 12 triangles) flicker.
The way I am currently rendering involves 2 passes, so I assume the flickering comes from an absence of proper barriers.
The execution goes:
start to render pass,
render to texture (image attachment of FB),
stop pass.
start pass,
render to main display
end pass.
There is only a single global graphics queue. Following the vulkan tutorial, I have a command buffer for every image in my swapchain, and I record commands to each buffer in that list, like so:
for(auto &cmd : cmd_buffers)
{
std::array<vk::ClearValue, 2> clears = {};
clears[0].color = vk::ClearColorValue(array<float, 4>({0,0,0,0}));
clears[1].depthStencil = vk::ClearDepthStencilValue(1.0f, 0.0f);
vk::RenderPassBeginInfo render_pass_info(
*render_pass, *(framebuffers[index]), {{0,0}, extent},
clears.size(), clears.data()
);
cmd.beginRenderPass(&render_pass_info, vk::SubpassContents::eInline);
index++;
}
/* submit more instructions to the command buffers later */
For the off screen target (FB) I only record a single command buffer.
I call my first render pass as described above, and then, immediately before calling the second render pass, I try waiting on an image barrier:
void RenderTarget::WaitForImage(VulkanImage* image)
{
vk::ImageMemoryBarrier barrier = {};
// TODO(undecided): maybe this isn't always true
barrier.oldLayout = vk::ImageLayout::eShaderReadOnlyOptimal;
barrier.newLayout = vk::ImageLayout::eShaderReadOnlyOptimal;
barrier.srcAccessMask = vk::AccessFlagBits::eShaderWrite;
barrier.dstAccessMask = vk::AccessFlagBits::eShaderRead;
barrier.srcQueueFamilyIndex = VK_QUEUE_FAMILY_IGNORED;
barrier.dstQueueFamilyIndex = VK_QUEUE_FAMILY_IGNORED;
barrier.image = image->GetImage();
barrier.subresourceRange =
vk::ImageSubresourceRange(vk::ImageAspectFlagBits::eColor, 0, 1, 0, 1);
vk::CommandBuffer command_buffer = h_interface->BeginSingleTimeCommands();
command_buffer.pipelineBarrier(vk::PipelineStageFlagBits::eAllGraphics,
vk::PipelineStageFlagBits::eFragmentShader, {}, 0, nullptr, 0,
nullptr, 1, &barrier);
h_interface->EndSingleTimeCommands(command_buffer);
}
And then somewhere else in the code I call it:
display_target.WaitForImage(&image);
active_target_id = 0;
display_target.StartFrame();
render_presentation.AddDrawData(quad_buffer, {uniform_data},
{{&image, 1}});
display_target.EndFrame();
Based on the behaviour I have seen, I assume my issue is a synchronization problem, however, the image barrier code doesn't seem to solve the flickering.
Am I using the barrier wrong? Should I look into other possible sources of error (and if so, which)?