Performing a Render Stage Trace
Updated: Oct 27, 2026
This topic describes how to use RenderDoc Meta Fork to perform a render stage trace, as well as how to read the Tile Timeline.
To look at render stage profiling data, load a capture, go to the
Event Browser, which can be opened by going to
Window on the menu, and click the

icon to perform a render stage trace. The headset proximity sensor will be briefly disabled so the trace can be performed without the need to cover it.
Ensure that you connect to the device via the
profiling mode. If you use normal replay mode/context, the Meta button for render stage trace will be grayed out.
After a few seconds, the render stage data appears in the Tile Timeline window. If the Tile Timeline window is not present, it can be found under the Window menu.
This timeline comes from the default
Low-overhead RenderStage Trace, which shows each workload as one block. To see the bin rows and per-bin stages that the Bin Information and Stage Information sections describe, use a detailed trace mode. See
Trace Modes and Per-Stage Metrics.
The Tile Timeline presents a lot of information in a compressed space. Zooming functionality is available with the mouse scrolling wheel to zoom in and out of areas of the timeline.
The top row of the timeline shows each of the surfaces rendered to in succession during the frame. Each block on the first row represents a surface and displays the following information:
- Surface ID
- Dimensions of the surface
- MSAA status
- Bit color and bit depth
- Dimensions of the individual tiles that make up the surface
- Total number of tiles for the surface
In a detailed trace, the second row of the timeline shows the active bin. To be precise, Render/StoreColor/LoadColor/StoreDS/LoadDS can belong to a bin and will have an additional bin row above them if the surface is rendering with binning mode enabled.
In a detailed trace, the third row of the timeline lists all the render stages for each tile on a given surface. This provides accurate timings (in microseconds) for each render stage, with a color key and label indicating the specific render stage. Common render stages include the following:
- Binning - The Meta VR device’s GPU uses a tiled architecture where all draw calls for a frame are executed in two stages. The first stage is the binning phase. Triangle vertex positions for all draw calls are calculated and assigned to bins. The bins correspond to a partition of the drawing surface. A simplified version of vertex shaders are executed during binning to find a triangle’s position.
- Render -This is the second stage of the draw call execution that began with binning. One chunk of this represents the total cost of all vertex and fragment operations for one bin. The full version of the vertex shaders are executed to compute the interpolants used by the fragment shader.
- LoadColor - Loads the color from slow memory into fast memory. This can happen when starting to render into a surface without clearing it.
- StoreColor - After an entire bin of pixel and fragment operations are done executing, the calculated color value is copied to slow memory. The copy comes from fast memory, which is dedicated to the bin’s rendering operations.
- LoadDS and StoreDS - These serve the same purpose as LoadColor and StoreColor, but for depth reads and writes to the surface.
- Blit - This stage indicates copying between slow memory regions. This can happen for various operations, such as mipmap generation and when clearing a surface without rendering anything.
- Preempt - The compositor is an OS-level service that executes at regular intervals to present the image submitted by the application to the screen. To deliver the image at the proper cadence, the GPU will preempt the application’s workload so that the compositor can complete its work on time.
Other render stages include the following:
- GLAsyncCompute - For the OpenGL compute shader
- GLWorkload - For the OpenGL workload stage
- VKQueue - For the Vulkan arbitrary start/stop within a queue stage
- VKRenderClear - For the Vulkan render pass clear stage
- VKWorkload - For the Vulkan workload (subpass) stage
- VKAsyncCompute - For the Vulkan compute shader dispatch pass stage
- VKLoadInput - For the Vulkan GMEM input attachment load stage
Trace Modes and Per-Stage Metrics
RenderDoc Meta Fork offers three trace modes. The Detailed + Per-stage Metrics mode adds a strip of per-stage values to the Tile Timeline for each metric you select.
Click the arrow next to the trace button in the Event Browser to open a menu of up to three trace modes. The trace button is the Meta icon button described at the start of this page. A check mark shows the selected mode, and you can select one mode at a time:
- Low-overhead RenderStage Trace - the mode RenderDoc Meta Fork selects each time you launch it; shows each workload as one block, without bin rows or per-bin stages
- Detailed RenderStage Trace - adds the bin rows and per-bin stages, without metric values
- Detailed + Per-stage Metrics - captures per-stage values for the metrics you select (shown only when the device reports per-stage metrics)
To capture metrics:
- Click the arrow next to the trace button.
- Click Detailed + Per-stage Metrics. This selects the mode and opens its submenu.
- Check the metrics to capture.
- Click the trace button itself, the Meta icon button described at the start of this page.
Checking a metric does not select the mode.
The submenu lists a Select All button, a separator, and one checkbox for each metric the device reports. Each checkbox is labeled with the metric name. Select All checks every metric. When every metric is checked, the button reads Deselect All and clears them all.
Hover over a metric name to see a tooltip with the description the device reports, if it provides one. Use it to learn what the metric means.
- Surface Write Ratio is checked by default, if the device lists it, until you change your selection.
- RenderDoc Meta Fork remembers your metric selection between launches, but the trace mode returns to Low-overhead each time you launch it.
- If no metric is checked, the trace runs as a Detailed RenderStage Trace with no metric values.
Read Metrics in the Tile Timeline
Under the surface, bin, and stage rows, each selected metric has its own strip.
Each strip shows one metric:
- Label - the metric name, then
max= and the largest value of that metric in the trace - Bars - one bar per render stage, with height relative to the largest value of that metric in the trace; heights cannot be compared between traces
- Color - every bar in a strip has the same color, and color does not change with value
- Empty stages - a stage with a value of zero, or no value, has no bar
- Details - hover over or click a bar to see the metric name, the value, the stage index, the stage type, and the duration in microseconds
To find the stage with the highest value of a metric, look for the tallest bar in that metric’s strip, then hover over it for the exact value.
Left click on a surface time slice to see detailed information regarding the execution of the replay:
- surface id
- start timestamp - in microseconds
- end timestamp - in microseconds
- duration - in microseconds
- width - width of the framebuffer
- height - height of the framebuffer
- msaa - multi-sampling anti-aliasing level
- multiple rendertargets - Count of the render targets (MRT) for the surface
- render mode
- color bits per pixel
- depth bits per pixel
- stencil bits per pixel
- color attachment attributes - Flags set for the color attachment
- depth attachment attributes - Flags set for the depth attachment
- stencil attachment attributes - Flags set for the stencil attachment
- bin count - Number of bins this surface is divided into
- bin width - Width of a single non-merged bin
- bin height - Height of a single non-merged bin
- new frame surface - This will be 1 if the surface is the first surface in a frame. This is used to delimit one frame from another.
- num rendered bins - Number of items in row 2 minus Binning, Blit or Compute
- num surface stages - Number of items in row 3 plus Binning, Blit or Compute
- compute only
Left click on a bin to see additional information on its execution.
# bins contained X/Y - If you’ve enabled Fixed Foveated Rendering, bins near the edge of the render texture will be combined. These values will be greater than 1 if this bin maps to multiple bins in the final render texture.- Fov Scale Factor X/Y [
#] - If this bin maps to multiple bins in the final render texture, these values will indicate the FOV adjustments so the edges of this bin align with neighboring bins.
Left click on a render time slice to see the stage index, type, start and end timestamps, and duration. The panel also lists the value of each metric captured in the trace.
Due to hardware differences between the VR devices, a render stage capture can appear different on an OpenGL app using multiview. The following timeline is from Meta Quest 1:
Note the two surfaces with the same ID. They are referring to the left eye and right eye slice of a 2D texture array. The same OpenGL app running on Meta Quest 2 will have only one single surface, but double the number of tiles:
Similar to OpenGL, a render stage capture can appear different on a Vulkan app using multiview. The following timeline is from Meta Quest 1:
Note the single surface with two binning stages (the yellow time slice). The same Vulkan app running on Meta Quest 2 will have only one single surface and one single binning stage due to hardware multiview:
On Meta Quest 3, a Vulkan multiview render pass appears as a single surface covering both views. For that surface, the multiple rendertargets field reads 2, one per view, and each bin carries a separate foveation scale factor per view.
Meta Quest 3 and Meta Quest 3S both use the Adreno 740v3 GPU (Snapdragon XR2 Gen 2). This GPU supports two Qualcomm-specific Vulkan extensions: VK_QCOM_multiview_per_view_viewports and VK_QCOM_multiview_per_view_render_areas. These extensions are not available on Meta Quest 2 (Adreno 650).
The Tile Browser tab shows your rendered frame broken up by each rendered bin, with a heatmap overlay that indicates which bins took longer than others. You can click on a bin to select it in the Tile Timeline. Both the Tile Browser and the Tile Timeline UI can be accessed under Window on the menu.