Buffer and Submission Rework #1

cosmonaut · 2022-01-12T22:27:52Z

cosmonaut commented

2022-01-12 22:27:52 +00:00

We used to have monolithic uniform buffers on the VulkanRenderer object, but this was inefficient in the case of threaded usage.

Now, we have a pool of uniform buffers. A uniform buffer is selected from the pool when a pipeline is bound. The uniform buffers are rotated upon presentation.

Now pushing uniforms is now a concern of the command buffer instead of the pipeline. The pipeline should just always have been a static object anyway.

Additionally, we now do extra buffer record-keeping so that buffer data can be updated after a bind/draw.

Fence submission has also been restructured so that submissions don't cause unnecessary blocks. Now we assign one fence per submission, and we don't wait for fences until it's time to present.

We used to have monolithic uniform buffers on the VulkanRenderer object, but this was inefficient in the case of threaded usage. Now, we have a pool of uniform buffers. A uniform buffer is selected from the pool when a pipeline is bound. The uniform buffers are rotated upon presentation. Now pushing uniforms is now a concern of the command buffer instead of the pipeline. The pipeline should just always have been a static object anyway. Additionally, we now do extra buffer record-keeping so that buffer data can be updated after a bind/draw. Fence submission has also been restructured so that submissions don't cause unnecessary blocks. Now we assign one fence per submission, and we don't wait for fences until it's time to present.

cosmonaut added 3 commits 2022-01-12 22:27:54 +00:00