So question is:
Do I really need for each image in a swapchain its own descriptorSet and corresponding buffers if they are modified each frame and I didn’t wait at the end of draw loop?
This question arise from tutorials what I see around internet.
In most popular tutorial from here https://github.com/Overv/VulkanTutorial/blob/master/code/22_descriptor_sets.cpp author uses multiple descriptorSets.
But for tutorial from nvidia or intel, it seams they aren’t multiply that objects by swapchain image count, and aquire-submit-present loop looks also like in the example above, without waiting at the end of loop for work done. And generally I can’t find any other examples of vulkan code where descriptorSets created for each swapchain image or frame in flight.
So I’m a little bit confusing. Also in my experiments with FIFO mode just one descriptorSet modified each frame seems work fine, even if I start modified underlying buffer and record next cb without waiting for present.