After you posted this video update, I started to try to mimic your director/actor setup and see if I could get my own up and running before you posted tutorial 10.

I’m not sure I’m going about it the right way, though. Could you offer up a little detail on your implementation? Unless of course you’re releasing the next video soon. Then I’ll just reference that.

Thanks,

MFerron

@anyone if you want to do this you can google making project templates in xcode (very simple to do)

For your renderManager, how are you going to handle drawing objects from different textures? Or are you just going to have all assets on one giant texture? I am not sure what the best way to do this is

found a some great little methods from cocos2d to rotate the device and the images. I decided to put them in the Singleton class and then add a sharedGameInstance to the app delegate so it can rotate your view from the begining. So this goes in the Singleton header file:

#define LANDSCAPE_LEFT 0 // 1 is left 0 is right
// Landscape mode
	BOOL landscape;
- (void) applyLandscape;
- (void) setLandscape: (BOOL) on;
- (BOOL) landscape;

make sure you put that in the right spots

creating a shared game instance in the delegate is pretty straight forward.

so here is the code in the Singleton.m:

- (BOOL) landscape
{
	return landscape;
}

- (void) setLandscape: (BOOL) on
{
	if( on != landscape ) {
		landscape = on;
		if( landscape )
#ifdef LANDSCAPE_LEFT
			[[UIApplication sharedApplication] setStatusBarOrientation: UIInterfaceOrientationLandscapeRight animated:NO];
#else
		[[UIApplication sharedApplication] setStatusBarOrientation: UIInterfaceOrientationLandscapeLeft animated:NO];
#endif
		else
			[[UIApplication sharedApplication] setStatusBarOrientation: UIInterfaceOrientationPortrait animated:NO];

	}
	return;
}

-  (void) applyLandscape
{
	if( landscape ) {
		glTranslatef(160,240,0);

#ifdef LANDSCAPE_LEFT
		glRotatef(-90,0,0,1);
		glTranslatef(-240,-160,0);
#else
		// rotate left
		glRotatef(90,0,0,1);
		glTranslatef(-240,-160,0);
#endif // LANDSCAPE_LEFT
	}
}

And that will rotate your device while keeping the images the same.

creating a shared game instance in the delegate is pretty straight forward.

so here is the code in the Singleton.m

And that will rotate your device while keeping the images the same.

Mike

I’m going to create a diagram which will hopefully explain what I’m doing. I think a picture will be easier than words, I hope :o)

I will also be releasing Tutorial 10 soon which will contain all my code for moving around the tilemap. Hopefully that will help as well.

As soon as I have my diagram done I’ll post a comment.

@kp3406, thanks for the info on your frame rates etc. You mentioned your getting 300-400fps. Are you running on the Sim? iPhone and iPod hardware has a max frame rate of 60fps which is why I ask.

I’ve been running some experiments with Tom who comments on the blog and its been really interesting seeing what has an impact. Calling glDraw___ too many times does up CPU usage a lot as all the API calls have overhead, so having all your geometry, texture and colour information in a single interleaved array seems to be the way to go. This is what the Anglecodefont class and Particle emitter classes do. I’m working on a design at the moment to create a RenderManager which will be able to provide that ability for all drawing, including what is draw from within the Image class.

There have been some great posts on the blog on this subject and I’m grateful to all those who have joined in. Its given me many more ideas on how to approach that problem and I’ll be posting info on the RenderManager once Tutorial 10 is done and I’ve got it coded up.

Mike

I know that using any NSLog statements in your update/render loop will cause a VERY significant slowdown, and quickly reduce your framerate to a halt. Also, I havent yet experimented with how many draw__ calls you can have before causing a slowdown, but I have 7 now in my render loop and it seems to be fine. Numbers I’ve seen thrown around on the internet are draw__ calls in the late tens to twenties can start to cause slowdown, don’t know if this is accurate though.