Note:

This view is only available in the OpenGL ES + EGL perspective by default.

The different types of dependencies it can detect are:

• If a render pass reads from a texture that was written to in a different render pass without being cleared. For example, render pass 0 draws to texture 1 and render pass 1 then reads from texture 1:

  

• If a render pass has the same depth or stencil buffer bound as another render pass without being cleared, assuming that depth or stencil testing is enabled. For example, both render pass 0 and render pass 1 have render buffer 1 attached to their depth target:

  

• If a render pass does a glBlitFramebuffer call on a different framebuffer. For example, render pass 0 draws to framebuffer 1 and render pass 1 blits framebuffer 1 into framebuffer 2:

  

The Render Pass Dependencies view shows render pass dependencies for the selected frame. To generate a list of dependencies, select a frame in the Trace Outline view and press the Generate button in the Render Pass Dependencies view. Any render pass in the selected frame that depends on another render pass is shown in the tree. Expanding the render pass tells you:

• Which render pass it depends on.
• Which frame that render pass is in.
• Why Graphics Analyzer considers it a dependency.

The dependency analysis stops at the first dependency for each render pass. To find out the next dependency in the chain, if there is one, select the frame with the earlier render pass in it and run the analysis again.

For example, in the following screenshot, two of the render passes in Frame 1, namely Render Pass 1 and Render Pass 4, have dependencies on previous render passes. Render Pass 1 depends on Render Pass 26 in the previous frame (Frame 0). Render Pass 4 depends on Render Pass 3 in the current frame (Frame 1). In both cases, there are dependencies because Texture 18 is attached to the active framebuffer for the render passes:

Figure 5-11 Render Pass Dependencies view showing dependencies