A fast, easy to use, free, and community supported 2D game engine
pravin
Member
Hello Everyone,
We are developing the game using cocos-2d 0.8.
Game has 80 levels and following are some characteristics.
1. Player movement is on accelerometer (Sensitivity).
2. We are playing sound effect and animations for each event.
3. Rewards generation after killing the enemy.
The game is playing good on 3GS and 3G. I have problem with 2G.
The game is slow on 2G as compared to 3G and 3GS.
Please advice how to improve the performance on 2G?
Thanks,
Pravin.
Hi Pravin,
Your post is very generic. Its like I'd say, "Hi Pravin, I have a car, it has wheels, makes sounds, and has breaks. How can I make it go faster?". Without exact details, code, and things you've tried already noone will be able to give you any good answer. What exactly are you doing, are you using atlassprites, are you using pvrtc textures, are you preloading your sound effects?
So, heres the generic answer:
- Try to upgrade to cocos 0.99, which is faster in some scenarios
- Read http://www.cocos2d-iphone.org/wiki/doku.php/prog_guide:best_practices
- Read http://www.cocos2d-iphone.org/wiki/doku.php/prog_guide:best_practices again.
You need to find where the bottlenecks are before you'll get anything other than speculation. Try dropping out the audio on a version, then any particle effects, then cutting down the number of sprites until you find whats causing the slowdown.
As @hactar mentioned above it may be a texture issue, try dumping your textures down to RGBA4444 or lower. They may look nasty but at the moment you just need to find the cause of the slowdown.
If your performance is degrading over time, it could be memory leaks as well. Use clain static analyzer to look for leaks. Also, make sure all your scenes are deallocated when you go to the next one. If they are not, you are retaining something you don't need to.
As the previous posters mention, find where you suspect you are losing performance. If you need help post about those areas and we can assist.
pravin
Member
Thanks for follow up.
I am using Atlas sprite for creation of enemies and there moving animation.
The sparking , blast effects are shown using Particle system.
The sound files are in .Caf format and played using CocosDenshion audio class.
About the speed :
1. On 3GS : The speed is constant form i.e first (1 wave) to last (80 waves) waves.
2. On 3G : the speed is constant and little bit down consider (10 - 20 %) down.
3. On 2G : The movement on acclerometer object looks jerky. rest of speed is good.
Here is what I was using for mine. YMMV.
#define kFilteringFactor 0.5
#define kAccelMultiple 250.0
-(void)accelerometer:(UIAccelerometer*)accelerometer didAccelerate:(UIAcceleration*)acceleration
{
float moveX = (acceleration.x * kFilteringFactor) + (lastAngleX * (1.0 - kFilteringFactor));
float moveY = (acceleration.y * kFilteringFactor) + (lastAngleY * (1.0 - kFilteringFactor));
lastAngleY = moveX;
lastAngleX = moveY;
moveX *= -kAccelMultiple;
moveY *= kAccelMultiple;
[self moveBGPostion:moveX y:moveY];
}Just making sure but you are testing this in release mode and not debug?
pravin
Member
Thanks JD and abitofcode,
in testing what I found that , the main reason for jerking is CollisionPairFunction.
Since I have 6 - 8 collision pair function to detect the collision between two bodies.
If I comment all collision pair functions the could not jerk on 2G.
so how I can overcome this situation? Please advise.
MrMojo
Member
i wonder how hard it would be to create a cocos specific function that when run, would analyze the current app for typical performance gotchas, and generate a report, containing things like:
- is COCOS2D_DEBUG on ?
- is app compiled for Thumb?
- Amount of texture memory in use over time (high/avg/low)
- Type of textures being used, and graphics mode being used (ie are 8 bit pngs's being used with a 32 bit graphics mode?)
- etc?
At the very least, a report generated by this function could be a useful starting point when trying to help people debug performance issues.
pravin
Member
Thanks MrMojo ,
Will you guide me how to check the following things:
1. is COCOS2D_DEBUG on ? How to enable COCOS2D_DEBUG
2. is app compiled for Thumb? - I am not getting this point.
3. Amount of texture memory in use over time (high/avg/low) - How to find out?
4. Type of textures being used ? we are using RGBA8888 texture format.(.png)
As in my game after killing the enemy we are generating rewards at run time.
As number of rewards (object of cpBody) added into space the movement depends on the accelerometer object looks jerky. (Note : In each level minimum 35 rewards are generated.
MrMojo
Member
Here's some info on what I was talking about. I'm thinking it'd be super useful to have this in a report that averages some of this over time, and gives simple beginner / best practices comments that point to urls in the wiki talking about each subject.
that having been said, this is all without trying to compile it:
+(BOOL) is_cocos2d_debug
{
#if COCOS2D_DEBUG
return true;
#else
return false;
#endif
}for thumb support, i'm not sure of how to check it at runtime, but you can check it at dev time like so:
http://www.cocos2d-iphone.org/forum/topic/94#post-389
and for memory usage (not texture, just memory) these 3 posts talk about how to do it (they all refer to the same code, but point out some issues you may have using it too)
http://www.cocos2d-iphone.org/forum/topic/3209#post-19966
http://developers.enormego.com/view/iphone_sdk_available_memory
http://www.cocos2d-iphone.org/forum/topic/3079/page/2#post-20780
pravin
Member
The game is jerking on only 2G. The work on fine on 3G and 3GS.
The other game objects are not looks jerky except the player object which is moving on accelerometer.
I have one more doubt looking iPhone configuration i.e. 2G , 3G and 3GS.
Is it possible to maintain the same speed on all devices?
Is it definitely the accelerometer? Have you tried controlling its movement with a repeating action and removing accelerometer control to check?
Are you creating and removing the rewards each time i.e is there a dealloc happening?
If so consider building a pool of rewards, each one having a flag indicating whether it is currently in service or not. When you need a new one look for the first reward in the pool that is available and when you've finished with it reset its flag. This way you avoid the expensive init/dealloc during gameplay and instead move it to somewhere you can cover it up.
pravin
Member
Thanks zenkimoto ane abitofcode for follow up.
We are displaying minimum 32 number of enemy on screen, using AylasSprite sheet.
Almost we have 25 types of different rewards and generated depending on enemy type.
So we are generating (allocating) rewards when the enemy was killed.
Also we have set a flag indicating whether reward is currently in service or not.
As reward is created using cpBody and cpShape instances because to show the bouncing effect, so we are not creating any pool.
We are removing (deallocating ) the rewards after the completion of each level.
You must log in to post.
