Help me discovery why my game is so HEAVY!

cocos2d for iPhone » Programming » physics

Help me discovery why my game is so HEAVY!

(6 posts) (5 voices)

Started 2 years ago by badawe
Latest reply from PhilM

Tags:

badawe
Member

I need some help of you guys!
Its my first game ever, and my first game with cocos2d and iphone, i come from Flash (Actionscript 3) and its my third week working on this project. I never work with Object-c, C or C-whatever before, so i need some advices if i'm doing things wrong ok?
Its a simple drop box game, and i can't understand how this project on my device its so heavy, so i want share with you guys my project to see if any of you guys give some advices of what I'm doing wrong at this one. And i have some other questions:

- I really need keep my fps at 60? Because box2d at 30 FPS seems miss many many steps, or something drop fps really hard at the point of the box2d can't calculate precisely.

- I have some textures by now just to test, so i have 3 big textures i think is (1024x1024) with 12 frames. and this animations, this is bad?

- How i can check my texture memory? I try follow some tutorial to do this with instruments, but i'm running Snow Leopard with 3.0 OS and i don't have the same options.

Thank all of you guys and i hope some good soul can help me on that.

Link to the Projetct:
http://rapidshare.com/files/287383945/Hibernate_Clear.zip.html

Posted 2 years ago #
andre.p
Member

I haven't looked at the project code, but 1024x1024 textures are huge! Especially if you have 12 of them! That would likely cause a large chunk of your performance problems by itself.

Why do you need the textures so large? Couldn't you tile what you need, or generate it on the fly?

Posted 2 years ago #
Steve Oldmeadow
Administrator

I don't have time to look in depth but some things I noticed quickly:

1) Only measure performance with debug drawing turned off.
2) Only measure performance with a release build. I couldn't get any of your release builds to compile so I assume you are testing against the debug build.

Even so the debug build ran well on a 3GS when I turned off debug drawing.

@andre.p - he only has 3 1024x1024 textures not 12.

Posted 2 years ago #
Clain
Member

Your sprite sheets are 880x390. This is bad because they will be loaded in memory as 1024x512, which wastes a lot of space. Your textures for the legs could be repacked because there's also a lot of space wasted in them. I can see why you organized your textures like this, because you calculate the frame rect once and then you fetch all the parts of your character (the bug) in the different textures but with the same frame. In your body texture, you waste space for the legs, in the legs textures, you waste space for the body. With a little extra work when creating the AtlasSprites and the AtlasAnimations (ie calculate 3 frames for your different sprites/animations), you could easily put all your current textures into a single 1024x1024 one.

Regarding your question about FPS, maybe this thread can help you : Fixed time step

Posted 2 years ago #
badawe
Member
Guys i really wanna thank all of you.. all the advices, make the diference, thanks again, and i have more few questions:

- Grouped all my animations in only one atlas sprite. Of size: 828 × 559 but is only one.
- Fixed my FPS to 30 fps;
- When i run in the debug mode, i get some slow downs yet, but lot less than previous versions, when i run in release version is perfect THANKS a lot!
- I can't understand if I'm doing right on time step by now i left this way:
```
-(void) doStep:(ccTime)dt
{
	int32 velocityIterations = 8;
	int32 positionIterations = 1;
	_world->Step(dt, velocityIterations, positionIterations);
}
```
It is the best way?
- What is the best way to do one animation of background? I make then in After Effects and export png sequence, i get 30 frames, so if i do one AtlasSprite it is gonna stay bigger than 1024x1024. So if i load a png sequence, its a problem?
Posted 2 years ago #
PhilM
Member

Hey badawe, the links seems to be dead now, but sounds like you got most issues resolved.

I'm also interested in the best way to handle the step with box2d.

For the background animation, as far as I know you'll have issues just loading anything that large. You might need to export your render components to a few different layers/textures, and try to recreate some of the animation within cocos2d by moving them around (if that works with your afx file). That way you might be able to get away with one, or possibly 2 extra large textures, but unfortunately at the loss of alot of potential effects you could do with afx.

Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.