many thanks again, rob

#import Foundation/Foundation.h
#include math.h

Here’s my *.h file:

———————-
#import
#include

@interface Progression : NSObject {
float currentValue;
BOOL doesLoop;
float loopBegin;
float loopEnd;

}
@property (nonatomic)float currentValue;
@property (nonatomic)BOOL doesLoop;
@property (nonatomic)float loopBegin;
@property (nonatomic)float loopEnd;

-(id)initWithValue:(float)value doesLoop:(BOOL)loop loopBegin:(float)loopB loopEnd:(float)loopE;
-(void)progressBy:(float)value;

@end

———————–

and my *.m file:

———————–
#import “Progression.h”

@implementation Progression
@synthesize currentValue;
@synthesize doesLoop;
@synthesize loopBegin;
@synthesize loopEnd;

-(id)init {
self = [super init];
if(self != nil) {
currentValue = 0;
doesLoop = NO;
loopBegin = 0;
loopEnd = 1;
}
return self;
}

-(id)initWithValue:(float)value doesLoop:(BOOL)loop loopBegin:(float)loopB loopEnd:(float)loopE {
self = [super init];
if(self != nil) {
currentValue = value;
doesLoop = loop;
loopBegin = loopB;
loopEnd = loopE;
}
return self;
}

-(void)progressBy:(float)value {
currentValue = currentValue + value;
if(currentValue > loopEnd) {
currentValue = loopBegin + fmod(currentValue,loopEnd);
}
}

@end
——————–

Please help.

I’m having the same issue as Jason. And from what I can see, it is a binding issue. I think the reason is because in the Image renderAt method it is checking to see if the texture is already bound using your if statement:

And then we jump to the font rendering for rendering the font, which just binds without checking if the texture is already bound as so:

and then when it goes back to the animation it uses the image render code, and according to the appdelegate, that texture is already bound, so it skips the binding step, except that when we did the font rendering, it changed the binding without telling the app delegate.

What I can’t figure out, is how come the code downloaded from the tutorial works, cos it has that flaw in it :P Cos in my code which I’ve been changing as I follow the tutorial video it doesn’t work with that flaw in it…. so I’ve missed something somewhere.

Cheers,
Donna

Are you caching the texture number and checking to see if its changed maybe before changing it. It certainly sounds like a texture binding issue.

Let me know what you find. If you can’t see the problem and can send the project I’ll try to take a look.

Mike

Love the tutorials and am looking forward to buying your book!

I have taken the tutorial 5 code and made it so that glView is loaded by a glViewController that is loaded by a RootViewController that is loaded by the AppDelegate. The only thing I had to change in your code was the reference to the AppDelegate and the currentTexture variable which I put in my glViewController class. I call:

[glView performSelectorOnMainThread:@selector(mainGameLoop) withObject:nil waitUntilDone:NO];

from the glViewController.

When I run the app everything works great except that the animation is referencing the wrong sprite sheet. Instead of animating the explosion it is animating a small piece of the font texture the same size as the explosion.

What I have found is that if:

[font1 drawStringAt:CGPointMake(messageX, 200) text:message];

immediately precedes:

[anim renderAtPoint:CGPointMake(160, 200)];

Then I always have this problem. However if I put any other render call between the two, or if I call the font after the anim one then the problem goes away and the animation uses the correct sprite sheet.

I have built this app twice to make sure I wasn’t accidentally changing any of your code. I have no warnings and no errors.

Can you think of any reason for this strange behaviour?

Sometimes the answer to a question is so obvious that you miss it. Must be the alzheimers kicking in.

Just needed to check if the animation was running lmao now + feeling a little slow.