I tried my best to remove the animation methods/variables and to put mainGameLoop in didFinishLaunching (WithOptions) in the AppDelegate class but that didn’t do the trick. Should I worry about replacing the standard iPhone animation loop stuff with the while(true) loop you have set up in mainGameLoop, or do you think it’s fine the way the template presents it? I’m really stuck on this one.

Thank you,
Ilya

Does anyone have any suggestions about how to remove the timer/animation stuff when using Xcode 4? The animation/timer stuff is used in other methods and it’s hard to tell what is/isn’t needed when making these changes.

Thank you,
Ilya

That trick does indeed work for the most part, but the new template did make it a little confusing for me to implement correctly.

I think the tutorials are great, but the XCode 4 templates introduce a significant number of differences that can create a great deal of confusion.

For instance the runloop trick you spend a good chunk of time explaining is not usable with the new template (at least not without a significant amount of additional digging). Trying to implement the changes against an XCode 4 template results in renderScene updates occurring only when a user event occurs (this includes adding the performSelectorOnMainThread fix).

I realize the debate over using the templated timers vs. managing your main loop is ongoing, and will likely remain so, but if you could at least leave a note for those new to the tutorials to steer clear of that whole thing while following along, I think it would prevent many issues.

I wish I had more time to update then, but apart from the XCode template being different, everything else is just as valid as when I first created them and I’m pleased they are still proving to be useful.

Mike

A comment on getSpriteAtX, and best practices….

X and Y should really be reserved for pixel coordinates. To avoid confusion, a better naming would be:

getSpriteAtColumn(GLuint)column row:(GLuint)row;

Same thing with renderAt…

Cheers.