Google I/O 2009 - Writing Real-Time Games for Android

Google I/O 2009 - Writing Real-Time Games for Android

Chris Pruett

Do vertex arrays keep you up at night? Do you have nightmares involving framerates and event loops? If so, this session might have the cure for your condition. Chris Pruett will discuss the game engine that he developed, using it as a case study to explain the common pitfalls and best practices for building graphics-intensive applications. You'll learn how to properly pipeline game and rendering code, manage drawing surfaces, and incorporate 2D and 3D graphics cleanly.

For presentation slides and all I/O sessions, please go to: code.google.com/events/io/sessions.html

Category:

Science & Technology

Tags:

• googleio2009
• google
• Google I/O
• developer conference
• Android
• mobile
• java

[Virginityrocks]

Wow. This guy is my hero. He's wearing a dork sweater, has pale skin and greasy hair. You know this guy is legit.

[calvino123456]

this guy talks EXACTLY like Tony Stark... Robert Downey Jr.'s illegitimate son much?

[jellyfaceification]

So all of these oop principles gonna slow you down... great

[penna420]

wtf happened to the sound? yesterday it was fine =/

[zzgarbu]

nice sound ;)

[thomasmaagaard]

jkvjku,b, what are you saying, i know it is something awsome, i just don't understand it

[unruheGER]

watched this awesome talk at least ten times in the last couple of months. game programming is pain!

[bboysil]

Check out one of my first 3D application I wrote on my channel or use this: /watch?v=DLplItqq9YA

Tell me what you think. Thanks :)

[burraak1]

Who wants to be a gay for host?

[Speedomon]

00:00:46 you know that you audience consists of a bunch of nerds if they laugh about THAT joke (if it was even meant to be a joke).

wait a second, I probably would too...

[ncr100]

Respond to this video...  * Touch events come in floods - try sleeping for 16ms in the onTouch callback to slow that down

* Take time to polish your game - appeal to picky users with higher quality stuff.

[ncr100]

@ncr100 * Use TraceView - the android sdk's profiling tool.

* Use SpriteMethodTest sample app to try out the canvas verus opengl speed. opengl draw_texture 2d can be 3x faster than using canvas. most devices today support opengl 1.1+. VBO can be useful too since you can use UV's to build your scene and use fewer draw jni calls. ATITC texture compression can help improve performance on devices that support it.