You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, when updating a Buffer/Image, a transfer command is recorded in the current frame's transfer command buffer, and a memory barrier (or queue ownership transfer) is recorded. This consider synchronization of the memory usage for this specific frame.
But this approach does not consider that the Buffer/Image might be in use in a previously recorded frame that is still being rendered by the GPU.
Think of an approach to fix this, making sure that when the Buffer/Image is updated, it is not being used by the GPU.
Options:
Double (or Triple) buffering. Creating multiple copies of the same resource, such that each frame uses its own version of the Buffer/Image.
Store latest frame used by the Buffer/Image. Only execute current frame if latest frame already have finished (using Semaphore or Fence, need to think).
Create a new Buffer/Image with new data that replaces the current Buffer/Image. Put the current Buffer/Image in deletion list.
The text was updated successfully, but these errors were encountered:
Now, when updating a Buffer/Image, a transfer command is recorded in the current frame's transfer command buffer, and a memory barrier (or queue ownership transfer) is recorded. This consider synchronization of the memory usage for this specific frame.
But this approach does not consider that the Buffer/Image might be in use in a previously recorded frame that is still being rendered by the GPU.
Think of an approach to fix this, making sure that when the Buffer/Image is updated, it is not being used by the GPU.
Options:
The text was updated successfully, but these errors were encountered: