cocos2d for iPhone

A fast, easy to use, free, and community supported 2D game engine

1. 

   SpLogic
   Member

   I am new to cocos2d and this is my first post.

   Inside my game scene init I have code creating 600 sprites. I used a sprite sheet (CCSpriteFrameCache) and the created sprites are added into two CCSpriteBatchNode's. The actual images used to create the 600 sprites are 19 (they are all on the sprite sheet). A lot of the sprites are created out of the same image. This initializaiton drops my frame rate down to 30 in my iphone simulator. Commenting out this initializaiton raised the frame rate back to 59~60. I thought the initialization is a one time shot and once the sprites are cached (in the CCSpriteFrameCache) rendering is fast. But apparently this is not the case or I missed anything? The reason that I have so many different sprites is because I'd like to mix match of different sprites to creat variations. If there is no solution to the performance problem I'll have to combine them together into just a few sprites and loss the flexibility to create variation.

   Thanks for your attention and help.

   Posted 1 year ago #
2. 

   alexasha
   Member

   Never test on the simulator.

   Posted 1 year ago #
3. 

   SpLogic
   Member

   I thought the simulator is normally faster because the machine CPU is faster than the devices. So we could not trust the simulator as far as performance is concerned?

   Posted 1 year ago #
4. 

   ruben301
   Member

   You could have searched on this forum, the simulators performance differs from the real device because the app itself runs on the computers hardware. As alex said above me just don't test performance on the simulator, however it could be great to test graphical aspects of your game etc. but not for testing performance or physics.

   Posted 1 year ago #
5. 

   SpLogic
   Member

   I googled before I posted on this forum. I probably should search this forum first. So there is nothing wrong creating 600 sprites in theory, right?

   Posted 1 year ago #
6. 

   Birkemose
   Moderator

   From your post, it is unclear how many sprites you actually render.
   If you render none, creating 600 spires should have no impact on frame rate.
   If you render 600 sprites, frame rate will drop. How much depends primarily on how many pixels are rendered, ie 600 sprites, each filling the entire screen, will drop the frame rate to 0.0012.

   Posted 1 year ago #
7. 

   SpLogic
   Member

   For now I only have the init method (and of course dealloc). There is no scheduled update or anything. The 600 sprites tiles a 320x320 region of the screen. Sorry for the ignorance. But I am not sure I understand rendering here. After adding them to the sprite batch node, they are displayed on the screen.

   Posted 1 year ago #
8. 

   Birkemose
   Moderator

   Default, sprites are visible, and placed at 0,0 ( lower left corner ). So you might have 600 sprites on top of each other ;)

   Posted 1 year ago #
9. 

   Dragyn
   Member

   The simulator is not necessarily faster than a device. For example, on a 1st gen MacBook Air, the simulator for me was generally 10 to 20 FPS slower than even a 1st gen iPod Touch. Remember, even though a Mac has a faster CPU, you've also got the overhead of XCode, OSX itself, the simulator, network connections, etc.

   600 is quite a few sprites, to be honest. Make sure that you are adding the batch node to the layer, and the sprites themselves are all added as children of the spritesheet, NOT "self". If you do that, you lose all draw performance gains from using the batch node.

   Posted 1 year ago #
10. 

    SpLogic
    Member

    For future reference of this thread I tested my program on a 2nd generation ipod touch and the frame rate is 60. Thanks everybody for your help. Lesson learned: test performance on device, not simulator.

    Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.