Vulkan Abstraction - Change from VkWaitIdle to VkFence

[SpinnerX]

Overview

Currently our vulkan abstraction layer uses vkQueueWaitIdle. Might be better for using VkFence for various reasons from what I've learned. This is something that I would eventually want to look into.

Reasons

• Wait on completion of work without having to wait on work submission after the work you are waiting on.
• VkFence allows other threads to push command buffers to queue without interfering with wait.
• Flexibility on how command buffers get submitted to the render pass when dealing with multiple threads to the renderer thread.

Stack Overflow - Here is the link for more information https://stackoverflow.com/questions/39537176/in-what-situations-is-vkfence-better-than-vkqueuewaitidle-for-vkqueuesubmit

[SpinnerX]

For right now im closing this because it has already been added as part of synchronization integrations into the Vulkan abstraction layer/

VkFence is a much finer grained solution then vkQueueWaitIdle. Since VkFence allows to wait on tasks without having them needing to be submitted first.

Allowing flexibility in how we wait for specific threads to finish with tasks. Which can also allow your CPU to be open for doing other tasks while finishing it's current task prior to submission.