Frame Analysis

Use Graphics Frame Analyzer to understand exactly what is happening within your game on a frame-by-frame basis, as well as to identify, locate, and analyze rendering issues in your OpenGL/OpenGL ES* application:

  • Check the compatibility of your game code on multiple devices.
  • Identify the most expensive draw calls in the frame by exploring a variety of metrics.
  • Analyze all resources used by the selected API calls: programs, geometry, textures, states, render targets.
  • Experiment with shaders, states, and uniform variables.
  • Locate misplaced objects and solve issues with shadowing, lighting, or color schemes.

The typical workflow to perform frame analysis for your application is as follows:

1.

Set up your host and target systems for analysis

  1. For OpenGL ES apps: Set up Android Debug Bridge (adb) USB connection and connect your device to the analysis system with a USB cable.
  2. Run the Graphics Frame Analyzer from the Ubuntu application launcher, or execute frame-analyzer-ogl from Terminal. By default, this script is located in /opt/intel/FrameAnalyzerOGL.

2.

Load the frame capture file

  1. Capture a frame using Graphics Frame Analyzer or System Analyzer.
  2. Open frame capture file for analysis.

3.

Analyze a specific frame
  1. Ensure all API extensions used in the frame are supported by your target system (Ubuntu system or Android* device): preview the frame with the device player to see the list of unsupported extensions, if any.
  2. Locate API errors in the frame.
  3. For OpenGL ES apps:
    1. Find performance bottlenecks by analyzing metrics values.
    2. Depending on the metrics values received, use one or more of the following capabilities of the Graphics Frame Analyzer:

See Also

System Analysis for OpenGL/OpenGL ES Applications
Platform Analysis for OpenGL/OpenGL ES* Applications

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