Okay... found a workaround for my problem.

I was loading my models from Blender, as a resource file. Then copying the relevant nodes from the resource file, adding them to the world, and the lighting was broken for textured objects.

If, before copying the relevant nodes, you _add_ the resource file contents to the world (but hide them offscreen somewhere) it all works fine.

Weird! My suspicion is that because I wasn't adding the source nodes to the world, a bunch of materials etc. weren't properly available to the world or something, but I don't really know what's going on under Cocos3D's hood in terms of resource handling. Still, that solves my problem, although it doesn't seem ideal in the long run!

Cheers,
Ian

@NOG:
Since cocos2d v2.0-beta, you could reposition the FPS by defining the following macro:

#define CC_DIRECTOR_FPS_POSITION ccp(0,0)

Yeah, but I'm sure it's been done many times. It's even more important with parallax backgrounds because my maps are connected, and it uses the sliding transitions between them. Otherwise it would be really complicated to fix it by changing the z order and how they are connected.

That is an interesting idea.
You mean, ex switching scene with a kewl flippa-thing, while having a static layer on top of it all?

Well ok, maybe I should try something different. Just studying the code to see different ways I can display things outside of a scene. Reason being, that some of my layers are affected by scene transition effects.

I have heard - from high places - that it should be IMPOSSIBLE, to change the position of the FPS label.

I would look at the code where the FPSLabel is updated.

Actually it still doesn't seem to set the position. i.e. tried 200,200

Ahh.. didn't know it should be using ccp.

Thanks! =)

FPSLabel is defined in CCDirector.m in setGLDefaultValues. Just add a position somewhere in there.

-(void) setGLDefaultValues
{
	// This method SHOULD be called only after openGLView_ was initialized
	NSAssert( openGLView_, @"openGLView_ must be initialized");

	[self setAlphaBlending: YES];
	[self setDepthTest: YES];
	[self setProjection: projection_];

	// set other opengl default values
	glClearColor(0.0f, 0.0f, 0.0f, 1.0f);

#if CC_DIRECTOR_FAST_FPS
    if (!FPSLabel_) {
		CCTexture2DPixelFormat currentFormat = [CCTexture2D defaultAlphaPixelFormat];
		[CCTexture2D setDefaultAlphaPixelFormat:kCCTexture2DPixelFormat_RGBA4444];
		FPSLabel_ = [[CCLabelAtlas labelWithString:@"00.0" charMapFile:@"fps_images.png" itemWidth:16 itemHeight:24 startCharMap:'.'] retain];
		FPSLabel_.position = ccp(0, 0); // <-- position here
		[CCTexture2D setDefaultAlphaPixelFormat:currentFormat];
	}
#endif	// CC_DIRECTOR_FAST_FPS
}

I'm interested in having labels and parallax backgrounds displayed outside of a scene, and currently checking out CCDirector to see how the frames per second are displayed. Can anyone tell me where the label is positioned and added? Thanks

Thanks Gray - I guess I'm hoping someone else has seen the same symptom in the past, and has worked out what caused it. Or that Bill has an insight. :-)

Cheers,
Ian

I don't know what to tell you, but if it's just a test and not too much code, I'd recommend just creating a new project and re-writing the code to see if that fixes it... it's happened to me before when I'm just getting used to new code API's and whatnot and like you said screw up a retain or something like that somewhere.

Gray

Can anyone think of a reason why applying a texture to a shape would stop dynamic lighting working? i.e. a plain, simply convex poly which shades correctly as it spins has a textured material applied, and suddenly the lighting is acting as if it's baked on - the model has lighter/darker sides but they're fixed with respect to the model as it spins, looking baked on to the model.

Application of texture:

mesh.material=[CC3Material material];
CC3Texture* tex= [CC3Texture textureFromFile:@"test.png"];
[mesh.material addTexture:tex];

It's not bump-mapped or anything, shouldUseLighting is true, the PNG is a simple 512x512 texture with no alpha. I have had lighting on textures working properly in this project, but after a bit of reorganising it seems to have stopped and I can't figure out why.

The light isn't moving with the model.

Multiple models suffer from the same problem.

I'm vaguely wondering whether I'm missing a retain somewhere, or I'm sharing a material that I shouldn't... not sure.

I've tried this with parametric models, and with models imported via Blender / Collada2POD. I'm obviously hitting some sort of config/boundary condition somewhere, just not sure where to look!

Dear All:

I am in the process of developing a new space shooter and am noticing that the frame rate drops from initially 60 to 20 after adding and removing a larger number of shapes (>1000). I certainly do not have a memory leak as I have used the profiler to check my memory usage. Using the Time Profiler I discovered that the processes that are using more and more time are the calls to 'cpvdot'.

By printing out

NSLog(@"SIZe %d", space->activeShapes->handleSet->size);

i realized that the the number of the active shapes grows until 193 at which the fps slows down significantly. To remove shapes i'm doing the following

////these are my variables
CCSprite *SystemSprite;
cpSpace *World
cpShape *DynamicShape
cpBody *DynamicBody;

////here's the code for removing the shapes

[ParentBatchNode removeChild:SystemSprite cleanup:true];
cpSpaceRemoveBody(World, DynamicBody);
cpSpaceRemoveShape(World, DynamicShape);
cpShapeFree(DynamicShape);

Could anybody let me know why the number of the objects is increasing even though i am removing them?

Thanks everyone

Tim

I implemented this solutoin:

init of scene:
==============
mBeginTime = 0;

game_loop:
==========
double lSleep = (1.0 / 50.0f) - ((double)CFAbsoluteTimeGetCurrent() - mBeginTime);

if (lSleep > 0.0)
{
[NSThread sleepForTimeInterval:lSleep];
}

mBeginTime = (double)CFAbsoluteTimeGetCurrent();

---

Seems to be a bit choppy at first look.

Happy Xmas! colleagues,

I have searched the forum and found many topics about fps performance issues. In my case I want to force 50 fps but as far as I understand cocos2d and finally CADisplayLink only supports 30 or 60 fps (correct me if I am wrong).

So, I am searching a good way to delay the game loop call to reach stable 50 fps. At the moment my game is running at full 60 fps.

For some examples I would be really thankful.

Kind regards,
Stefan

Hi!

My code:

///////////////////////////////// nandu.h /////////////////////////////////////////

@interface nandu : CCLayer
{
CCSprite *fondo;
//CCParticleRain *lluvialenguad;
}

+(CCScene *) scene;

@end

///////////////////////////////********************/////////////////////////
///////////////////////////////********************/////////////////////////
///////////////////////////////********************/////////////////////////
///////////////////////////////********************/////////////////////////
///////////////////////////////********************/////////////////////////

///////////////////////////////// nandu.m /////////////////////////////////////////

#import "nandu.h"

@implementation nandu

+(CCScene *) scene
{
// 'scene' is an autorelease object.
CCScene *scene = [CCScene node];

// 'layer' is an autorelease object.
nandu *layer = [nandu node];

// add layer as a child to scene
[scene addChild: layer];

// return the scene
return scene;
}

-(void)starButtonTapped{

[[bookmanager sharedbookmanager] runSceneWithID:kcuruscene];

}

// on "init" you need to initialize your instance
-(id) init
{
// always call "super" init
// Apple recommends to re-assign "self" with the "super" return value
if( (self=[super init])) {

isTouchEnabled_=YES;

[[CCSpriteFrameCache sharedSpriteFrameCache] addSpriteFramesWithFile:@"curunandu.plist"];

fondo =[CCSprite spriteWithFile:@"fondonandu.png"];
fondo.position=ccp(384,514);

[self addChild:fondo z:-2];

CCSprite *nandiu=[CCSprite spriteWithSpriteFrameName:@"nandusinfondo.png"];
//lenguado.anchorPoint=ccp(0,0);
nandiu.position= ccp(391, 637);
nandiu.tag=100;
[self addChild:nandiu];

CCMenuItem *adelante = [CCMenuItemImage
itemFromNormalImage:@"1.png" selectedImage:@"1.png"
target:self selector:@selector(starButtonTapped)];
adelante.position = ccp(640, 60);

CCMenuItem *atras = [CCMenuItemImage
itemFromNormalImage:@"3.png" selectedImage:@"3.png"
target:self selector:@selector(starButtonTapped)];
atras.position = ccp(130, 60);

CCMenuItem *indice = [CCMenuItemImage
itemFromNormalImage:@"2.png" selectedImage:@"2.png"
target:self selector:@selector(starButtonTapped)];
indice.position = ccp(388, 100);

CCMenuItem *ficha = [CCMenuItemImage
itemFromNormalImage:@"botonfichatransparente.png" selectedImage:@"botonfichatransparente.png"
target:self selector:@selector(starButtonTapped)];
ficha.position = ccp(189, 254);

CCMenuItem *texto = [CCMenuItemImage
itemFromNormalImage:@"botontransparentetexto.png" selectedImage:@"botontransparentetexto.png"
target:self selector:@selector(starButtonTapped)];
texto.position = ccp(583, 305);

CCMenu *starMenu = [CCMenu menuWithItems:adelante,atras,indice,ficha,texto, nil];
starMenu.position = CGPointZero;
[self addChild:starMenu];
}
return self;
}

////Is this OK? mmmmm, I think maybe not, but work///////

-(void) ccTouchesBegan :(NSSet *) touches withEvent :(UIEvent *)event
{
UITouch *touch =[touches anyObject];
CGPoint location= [touch locationInView:[touch view]];
location=[[CCDirector sharedDirector]convertToGL:location];

CCSprite *nandusinfondo=(CCSprite *)[self getChildByTag:100];

id effect = [CCWaves actionWithWaves:10 amplitude:10 horizontal:YES vertical:YES grid:ccg(10, 10) duration:3];
[nandusinfondo runAction:effect];

}

- (void) dealloc
{
[[CCSpriteFrameCache sharedSpriteFrameCache] removeUnusedSpriteFrames];

// don't forget to call "super dealloc"
[super dealloc];
}

@end

///////////////////////////////********************/////////////////////////
///////////////////////////////********************/////////////////////////
///////////////////////////////********************/////////////////////////
///////////////////////////////********************/////////////////////////
///////////////////////////////********************/////////////////////////
My code works at 15 fps

And I have a BookManager and constant

My questions:

-How i can change my code for better performance? Any Ideas? :)
-I have 65 page to do; Is this the best way?
-15 fps on device is ok? or crash all the time?
-is this the best way for sprites load?
-All my art work is in .png; I have to change to .pvr?

i'm new on cocos2d and I almost finished my work and i need from the experience voice

and a study a lot before ask

sorry for my english i´m from Argentina like Riq!

best regards

Thanks for the reply. Yes, I've used the QEMU powered Android emulator, it's horrid. Compared to that the iPhone Simulator is superb. I guess I'll stick to getting > 30 FPS on simulator and hope to reach 60 on the device. Cheers!

Performance on the simulator is usually not very good. Never use the simulator as a performance indicator, that goes for all platforms (ever developed for Android? The Android emulator will make you want to throw up, that's how slow it is). After all, the device has a dedicated gfx processor.

Who knows if the simulator even uses your gfx card for opengl rendering (I don't anyway, but my guess it that it doesn't). Either way I'm pretty sure it's not optimized, and I wouldn't really see the reason for optimizing an emulator too much since it is solely meant for development, after all you are targeting the device, not the emulator :)

So don't worry too much about it, if it runs well on the device, mission completed :)

Running it on my phone gives 60 FPS, but 30 FPS on the simulator. I figured my nVidia m330gt > ARM built in... It's probably not that simple, but I imagine there is some tweaking in the simulator and also in some of the foundation code for cocos2d.

I used a single batch node and a single png...

I guess it all depends on how your implementation looks like, and how you use the batchnode(s).

Do you use one batchnode or a separate one for the ground, hills and clouds?

I've written a bunch of classes for creating a parallax effect background which contains the ground, hills and clouds. Each object is duplicated once and this allows me to create an infinite loop with the ground etc. Problem is, using CCSpriteBatchNode and 12 x PNG 32bit textures with approx. size 600 x 200px slows down my FPS to around 30. I have read that using CCSpriteBatchNode shows big improvements in performance, but I can't seem to replicate them.

http://www.learn-cocos2d.com/2011/09/cocos2d-spritebatch-performance-test/

How can I speed things up?

Hello everyone o/
I didn't know where to post first, so picked this general sticky thread.

I started programming in Obj-C (had a Java/Scala background mostly) relatively recently, and am already involved in making of a game here at my work. 3D included, ofc.
So, after implementing server-side logic and all sorta things, I had to make a pick and decide on a 3D engine.

My first pick was iSGL3D (since stack overflow provided me with it firsthand). It was kind of an introduction to 3D programming in general for me. Then I began to learn cocos2d (just for myself, really, no work involved) and stumbled upon cocos3d. And, well, here I am =)

I am really excited about using cocos3d - which will begin the day after tomorrow, to be honest.
Thanks the development team for making it.

You need to get the delta-time in order to calculate the correct FPS. All update methods([self scheduleUpdate]) gets ccTime dt as a parameter. You can set the string inside the update, or pass it on to [self showFPS:dt].

-(void) update:(ccTime)dt {
    [FPSLabel setString: [NSString stringWithFormat:@"%0.1f", 1.f/dt] ];
}

Although that's quite the workaround as the CCDirector can do this by default.
[[CCDirector sharedDirector] showFPS:YES];
or something quite similar will make it appear.

Heya folks, I am playing around with Nat's game kit, and trying to figure out how to enable the actual FPS Count.

So I typed in the App.h file this:

-(void) showFPS;

And then going into App.m and typing

-(void) showFPS

{

[FPSLabel setString:@"60.0"];
[FPSLabel draw];
}

Frankly, I'm not sure what I am doing, but I am trying to tell the program to display the Frame Count, whatever it is. So that FPSLabel (which wasn't defined and so caused a Build Failure) was an incorrect approach anyway.

But am I on the right track?

Also, try to use 16-bit textures or lower whenever possible.
http://www.cocos2d-iphone.org/wiki/doku.php/prog_guide:best_practices#textures

Also look at any invisible elements that you have in your game. Menu's that you are not displaying. You should create menu items when you need them.

In your app delegate most likely you have this line :
if( ! [CCDirector setDirectorType:kCCDirectorTypeDisplayLink] )
This sets the Cocos Director tu run as kCCDirectorTypeDisplayLink. This means if you read there that you will either have 60 fps or 30 fps or 15 fps.
Due to the fact that your device can't handle what you have on your screen the fps dropped from 60 to 30.