Rendering performance depends on the order of rendering object. Less spritebatches and render target switches is always better. Therefore, the engine should have an ability to reorder object graph for rendering.
Here's an example scene graph:
Naive rendering order causes many render target switches:
RT = 0
RT = 1
Render 1
Render 2
RT = 0
Render RT 1
RT = 2
Render 3
Render 4
RT = 3
Render 5
Render 6
RT = 2
Render RT 3
Render 7
RT = 0
Render RT 2
Render 8
The optimal order would be:
RT = 1
Render 1
Render 2
RT = 3
Render 5
Render 6
RT = 2
Render 3
Render 4
Render RT 3
Render 7
RT = 0
Render RT 1
Render RT 2
Render 8
Benefits: each 4 RT switches instead of one. Each RT is used exactly once, which means default RenderTargetUsage can be used instead of the slow RenderTargetUsage.PreserveContents.
Rendering performance depends on the order of rendering object. Less spritebatches and render target switches is always better. Therefore, the engine should have an ability to reorder object graph for rendering.
Here's an example scene graph:
Naive rendering order causes many render target switches:
The optimal order would be:
Benefits: each 4 RT switches instead of one. Each RT is used exactly once, which means default
RenderTargetUsage
can be used instead of the slowRenderTargetUsage.PreserveContents
.