cocos2d for iPhone

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

1. 

   Smauky
   Member

   Hello, and thanks in advance.

   Sorry for my english, im not a english speaker, hope you understand me :)

   I make a custom atlasSpriteManager superclass that i use for all my "monsters" of my future game, why directly an atlasspritemanager instead of a normal node with an added spritemanager? cause i notice a boost in speed. Ok since here no problem.

   The problem began when i started to create ASM with more than 1 atlas sprite sheet, one of them uses 3 PNGs files with all the animations, the animation runned depends on the state of my "monster", one state for each PNG file, so when i change the state i change the file using:

   [self setTexture:[[Texture sharedTextureMgr] addImage:@"monsterXstateX.png"]];

   of course, all my image files are preloaded on before the game starts.

   But when i first change the texture of the ASM, the game freezes 1 second, i checked all and finally noticed that the freeze its because the texture change in runtime. But the best part its that that freeze only happens the first time the change happens, i mean, if i have 3 monsters of the same type in the screen, the freeze only happens when i hit the first one, but the 2nd, 3rd, and all the rest of them, dont freeze, just the first time in all the application. Its like it needs to preload anyway.

   Anyone knows how can i preload that change before it happens when the game its started?
   Using the [[Texture sharedTextureMgr] addImage:@"monsterXstateX.png"] as all my other images, dosent work.

   I know that i can use 2 ASM each one for each file, but then i need to change ALL the other monsters than dont use more than 1 file, and the game performance will be lot lower, cause i need another extra node that keeps the ASMs and kills some of the performance. Im searching a good way to continue using only a ASM and the game dont freeze the first time i change the file.

   Posted 2 years ago #
2. 

   PhilM
   Member

   I noticed the same thing the other day, although I didn't try to see if it re-occurred after the first switch. I presumed it was the texture size or something, and ended up just having 2 different atlas sprites that were set visible/hidden to simulate the switch.

   But that animation only had to run once when a screen loaded, so I didn't mind that work-around/hack.

   I'm just about to try having a character sprite with multiple sprite sheets this week, so will see if I come across the issue again.

   As a temp work around, when you load the game/level, could you get a dummy sprite to load each texture off the screen, that way when you add your actual sprites, they shouldn't have the issue? Just a thought...

   Posted 2 years ago #
3. 

   riq
   Key Master

   you can change the texture at any time, and the delay you noticed is because the texture was not generated.
   so, as you said, you need to preload it.

   The cache should work, so probably you are preloading the image, but perhaps you are removing unused images.

   search for:
   removeUnusedTextures or removeAllTextures in your code.

   To prevent removeUnusedTextures to remove it, just retain it. Don't forget to release later.

   Posted 2 years ago #
4. 

   PhilM
   Member

   In my case, the textures were preloaded first, and run using 2 atlas animations strung together in a sequence with a CallFunc in the middle to flip the texture (so it visually appears as one animation).

   Thinking about it, I only probably got a blip in the animation, and not a whole second delay like Smauky, so it might just of been the fact it was 2 1024x1024 textures being flipped. I'm pretty sure it was still in memory, and no other images were loaded at all. I'll hopefully find out if its an issue this week when I attempt it properly in another project.

   Posted 2 years ago #
5. 

   Smauky
   Member

   I tryed to use a dummy sprite to reproduce the animation before the game really starts, but nothing occurs, it stills freezes the first time it occurs at the screen when the game is running.

   I checked for any removeUnusedTextures, but no, i dont use it, i will try with the retain option, but if nothing works, probably i will make 2 new objects, one for each status, cause the animations are "death animations" so i dont need the sprite anymore, i will removechild the one with the walking animation and add a new one in its position with the correct atlasspritesheet.

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.