Using Xcode OpenGL ES Frame Capture



Using Xcode OpenGL ES Frame Capture

November 20, 2012

tweet

Having used Microsoft Visual Studio a while ago, I think that the real difference with Xcode is that Xcode comes with a full suite of performance tools for free. Instruments is the most obvious one, but since version 4.5, Xcode includes a facility for capturing and analysing OpenGL ES frames. This tool, called OpenGL ES Frame Capture, is really simple and powerful: you can log all the OpenGL calls for a frame, inspects the content of OpenGL buffers, sees your OpenGL ES 2.0 shaders (even the “hidden” ones used by GLKBaseEffect). This is a quick review about how to use it in your app.

To follow this review and test a sample code, you can use one of the excellent Ray Wenderlich OpenGL/GLKit tutorials like OpenGL ES 2.0 for iPhone Tutorial or How To Create A Simple 2D iPhone Game with OpenGL ES 2.0 and GLKit.

Disclaimer: I’m a completely OpenGL rookie so I might employ not the right terminology in the following post. That’s said, let’s go!

1. How to setup OpenGL ES Frame Capture

There is a short Apple documentation about OpenGL ES Frame Capture. To capture OpenGL frames, you’ll need to use, at least, Xcode 4.5. The capture can only be done on a real device, running at minimum iOS 5, and connected to your Mac.

If you’re already including GLKit or OpenGL framework in your code, your project is already set up for OpenGL frames capturing. Anyway, you can check it by going to Product > Manage Schemes…, double-click you app scheme, click on Edit….

Tap on the Run scheme, then Options tab and check that ’OpenGL ES Frame Capture’ is set to Automatically Enabled or Enabled.

2. Capturing a Frame

You can capture a frame while you’re debugging your app. Launch the app in Debug mode (Product > Run or ⌘R). Once the app is launched, display the Debug Navigator (View > Navigators > Show Debug Navigator), and click on the FPS section of the Debug Navigator.

You can watch the FPS updated while playing with your app and test different use cases. Your mission, if you accept it, is to maintain a good 60 FPS. On my app sample, I’m currently running at 36 FPS so I will need to find where the performance bottleneck is.

36 fps is not good, I would like to have 60 fps!

In the editor, you can see the time spent in the CPU and the GPU. If you want to achieve 60 FPS, you basically have 16 ms to update and render each frame. In my app, I’m spending 27 ms in the CPU and only 5 ms in the GPU.

Given this number, I can already see that my problems are not on the GPU side, but maybe simply in my code. Let’s capture a trace to have a better view of what’s happening at each frame rendering. Just above the Debug console, tap on the Camera icon to capture an entire frame:

After clicking on the Capture frame icon (the capture take a few secons), you will have access in the Debug Navigator to the OpenGL frames:

On the device, you can see that the captured frame is displayed and paused. In the Debug Navigator, if you expand the rendering icon , you will see all the OpenGL calls for the frame you’ve just captured. The Debug Navigator has a list of every draw call and state call associated with that frame (and your code call stack). The buffers associated with the frame are shown in the editor pane, and the state information is shown in the debug pane.

If you don’t see the OpenGL objects pane (the blue one), just click on the assistant icon, and select in the power bar, for instance, All GL Objects:

You can right click in the Buffer pane and select Show Draw Call Highlight to see a cute green triangle on the triangle drawn by the call:

3. Inspecting OpenGL objects

In the assistant, you have access to the OpenGL objects like the Vertex buffers, the Index buffers, the binded (or not binded) texture, the shaders programs:

Click on the Index buffer will give you acces to the content of the buffer:

Click on the Programs will show you the corresponding shaders source code:

It’s a super simple and convenient way to get the source code of the shaders ”hidden” by GLKBaseEffect!

4. Improving performances

Just watching at the OpenGL capture frame, one can see that there is a huge obvious performance improvement to be done. In my current app, I draw 200 planes sprites with their shadow. Each plane has it own texture so the pseudo code for this captured OpenGL frame is:

glBindTexture( texture-plane-type-0) // texture for the plane of type 0glDrawArrays(GL_TRIANGLE_FAN, 0, 4) // draw 2 triangles (= 4 vertices in fan mode) for the sprite glBindTexture( texture-plane-type-6)glDrawArrays(GL_TRIANGLE_FAN, 0, 4) …………glBindTexture( texture-plane-type-2)glDrawArrays(GL_TRIANGLE_FAN, 0, 4) 

In the captured frame, there is practicality one render call for each sprite, resulting for more than 6000 OpenGL calls per frame! A very first optimisation is to have as few OpenGL calls as possible. In this case, instead of binding and rendering each planes one by one, I can use a Texture atlas and sprite batching to just bind one texture and only one draw call for all the planes. The resulted pseudo code will be:

glBindTexture( texture-atlas-for-planes) // texture for the plane of type 0glDrawElements(GL_TRIANGLE_FAN, 0, 200 * 3 * 2) // draw 200 * 6 vertices for all sprites 

After having modified the code and recaptured the frame, one can see that all the planes are rendered in only one call (the green boxes show the triangle rendered by the selected OpenGL code):

The app is now at a good 60 FPS ! Xcode gives you also some advices: in that case, there is still room to add more effect and quality:

5. Saving and sharing captured frames

One final thing: you can export and save your captured OpenGL frame. You can even share it with someones that don’t have your source code, if you want an OpenGL expert to analyse your calls.

Doing this is a bit awkward, I’ve not found a better way to do this, but it works. Select an OpenGL call in the Debug Navigator, then right click on the Xcode title bar where you can see the frame capture file name (*.gputrace):

You can see where Xcode temporally store the .gputrace file; you can then save this file in your Documents. If you want to reopen or share this file with someone, just connect a device on your Mac, double-click on thegputrace file and you will see this dialog box:

Click on Replay trace and Xcode will launch in a self-contained mode with just this file. Very convenient!

How to Use Xcode Frame Capture Debug Option

Issam Posted on Wednesday, October 3, 2012 at 04:10PM

One of the newest features in Xcode is the frame capture debug option for OpenGL ES. I used it a lot recently trying to figure out what Unity was doing rendering-wise on iOS, and I was thinking that other developers might not know about this and find it useful.

The only problem is that it seems to use a lot of memory, so it will only work on small Unity scenes (it crashes on bigger ones). You may have to create a new small test scene to use it. (I did not try it on an iPhone 4s or 5, I think they should have enough memory for bigger scenes.)

Once you run your application on the device, in the debug area there is a camera icon that you can use to capture a frame.

For example, I had a test scene running on the iPod touch:

(You can click on the following images to make them bigger)

Doing a frame capture gave the following results in Xcode:

On the left side you get all the OpenGL calls, the middle view shows the content of the currently set render buffers of the current OpenGL call selected. The other views allow you to get more details about all loaded OpenGL objects and the current OpenGL context.

The glDrawElements(...) calls on the left side are when a mesh is rendered on the current bound buffers. For example the following image shows what happens when we select the first mesh rendered: 

On the farther right view, you can see the currently bound OpenGL objects for this call. For example we can see that a call to glUseProgram(16) happened before the glDrawElements, that's why we have program 16 as a currently bound object. 

The bottom right view gives more details about objects. Right now the view is set to show all OpenGL objects, and we can see details about program 16.

On the top right view, you can double-click on the objects to get even more details about them. For example double-clicking on the texture object allows you to see all the mipmap levels of the texture and some info about it:

Double-clicking on the program allows you to see the vertex and fragment shader GLSL code (I guess an advantage of runtime compilation :)) 

Finally the bottom left view shows the current OpenGL context:

Also for those not familiar with Xcode, to navigate back you need to use the navigation bar at the top of each view (Took me a while to figure that out :)):