Opening Frame Capture with Graphics Frame Analyzer

Pre-requisites:

If you are analyzing an OpenGL* ES application, the target system to test against must be connected to your host system. This is required to calculate metrics data. Metrics data is only available for devices based on the Intel® Processor Graphics.

To load a frame capture file with Graphics Frame Analyzer:

  1. Launch the Graphics Frame Analyzer on the host system.
    The Open Frame Capture File window opens, displaying all frame captures available on your host system, in alphabetical order.

    NOTE

    If you need to create new frame capture files, click the Add button. All new frames captured while Graphics Frame Analyzer is running appear on top of the list.

  2. Select the frame capture file you want to analyze by clicking one of the frame thumbnails. The currently selected frame capture is highlighted with blue borders and appears in the frame preview field listing high-level details of the frame, such as filename, resolution, OpenGL/OpenGL ES API used, GPU details, and the name of the device on which this frame was captured:

    If your frame uses any extensions unsupported by the selected player, you will see a corresponding warning . You can use Left and Right arrow keys to navigate between the captured frames.

  3. Make sure your target system is selected as the player to replay the captured frame.
  4. Click the Open button to load the frame capture and start profiling.

    TIP

    If you are opening your frame on a different system, its rendering context could differ from the context of the system where the frame was captured. If there is a difference in rendering contexts, it might affect the performance and metrics data. To understand any possible performance impact of the current rendering context, click the button. You can compare the original and current rendering contexts in the pop-up window.

Next Steps

See Also

Graphics Frame Analyzer Window: Open Frame Capture

For more complete information about compiler optimizations, see our Optimization Notice.