cocos2d for iPhone

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

1. 

   ltby_sky
   Member

   I combine lot of magic effect frames into 2 big images (2048*2048), and taken more than 40M memory for loading them into memory by using CCSpriteFrameCache, anyone have this problem ?

   Or you can just simply try with it:

   [[CCSpriteFrameCache sharedSpriteFrameCache] addSpriteFramesWithFile: @"magicAtlas1.plist"];
   [[CCSpriteFrameCache sharedSpriteFrameCache] addSpriteFramesWithFile: @"magicAtlas2.plist"];

   magicAtlas1.plist:
   http://www.mediafire.com/?q5haj6zcy4aljnf
   magicAtlas1.png:
   http://www.mediafire.com/i/?d3al4ik74cx12mg

   magicAtlas2.plist:
   http://www.mediafire.com/?kho4jtdyuxixpt6
   magicAtlas2.png:
   http://www.mediafire.com/i/?9rrr67ewts4u5yn

   Posted 1 year ago #
2. 

   CJ
   Moderator

   One image at 2048x2048 RGBA8888 (32bits per pixel) will take 16MB of memory, so two will be 32MB.

   Posted 1 year ago #
3. 

   ltby_sky
   Member

   I found someone had the same problem, he said:
   originally I kept both image data and texture data, and now I release both after upload it to OpenGL.
   As a result I save 50+ MB system memory

   How do I release the data in Cocos2D as he said ?

   http://forums.indiegamer.com/showthread.php?9853-Texture-memory-usage-using-OpenGL

   Posted 1 year ago #
4. 

   araker
   Moderator

   Cocos already frees all buffers that are needed to create the texture. Take a look at the

   - (id) initWithImage:(UIImage *)uiImage resolutionType:(ccResolutionType)resolution method of CCTexture2D and you'll see that the buffers used are being freed as well.

   You can use the allocations instrument to see what takes up the 8 Mb you can't account for.

   Posted 1 year ago #
5. 

   riq
   Key Master

   Important: there is a bug on iOS 4 and iOS 5 (and possibly on iOS 3 and iOS 2) that allocates 33% more memory for the textures.

   So if you are creating two 2048x2048 32-bit textures, in theory it should allocate 32Mb, but in practice it will allocate 42Mb.

   Mipmap textures need 33% more memory, but iOS allocates 33% more memory whether or not the textures have mipmap information. This is a nasty bug.

   More info:
   https://devforums.apple.com/thread/113889?tstart=0

   This bug affects all OpenGL games (including cocos2d games)

   Posted 1 year ago #
6. 

   slembcke
   Administrator

   Huh. Never looked close enough at memory usage to notice that. I guess I might as well be enabling mipmapping all the time instead of trying to save memory. Heh.

   Posted 1 year ago #
7. 

   ltby_sky
   Member

   Thanks for reply, I have reduce the image size for free some memory.

   But I got another problem with releasing the animation frames image when they are no longer useful.

   I can see the memory free when I remove the texture created by CCSprite.initWithFile,
   CCTextureCache.removeTextureForKey

   But it wont work with the texture created by [[CCSpriteFrameCache sharedSpriteFrameCache] addSpriteFramesWithFile:@"xxx.plist"];

   Posted 1 year ago #
8. 

   Martin
   Member

   Since those are animations I think you'll get away with a lot less color information in the textures. Check out http://www.texturepacker.com/ and try to save your animations as RGBA4444 with dithering enabled.

   Also thanks @riq for pointing that bug out. Makes it a lot easier to plan my resources for textures.

   Posted 1 year ago #
9. 

   JC
   Member

   > But it wont work with the texture created by [[CCSpriteFrameCache sharedSpriteFrameCache] addSpriteFramesWithFile:@"xxx.plist"];

   it's normal, because the sprite frame cache keep handle to the texture.

   but you can remove all your sprite from the cache using [[CCSpriteFrameCache sharedSpriteFrameCache] removeSpriteFramesFromFile:@"xxx.plist"];
   and after remove the texture using [[CCTextureCache sharedTextureCache] removeTextureForKey:@"xxx.png"];

   Posted 1 year ago #
10. 

    Martin
    Member

    I have somewhat releated question: can I force bitmap font textures that are created with glyph designer into another texture format when loading them?
    E.g. when I set the default texture format to RGBA4444, and load the texture into the texturecache with:

    [[CCTextureCache sharedTextureCache] addImage:@"image-File-name.png"];

    (and then set the default texture format back to RGBA8888)
    When I then create a bitmap font label with a font file that uses this texture, will it automatically load the correct texture instead of creating a new one in RGBA8888 mode?

    Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.