A fast, easy to use, free, and community supported 2D game engine
thesmileman
Member
If you can't fit them in one AtlasSprite just put them in several. Maybe I am missing something with your problem but I don't know if putting them in one or even many AtlasSprite objects is what you really want to do but it seemed like the logical answer to your question.
I think you'll have problems running full size images at a good fps. At least I did when I last tried, and ended up having to break my images down into their component parts, and simulate alot of the animation in code.
Have you tested your initial single AtlasSprite animation on a device? I'd be interested if you have any more luck than I did.
thesmileman
Member
I haven't had problems running even larger than full size images a perfectly acceptable speed. Despite this if you are trying to switch them out as frames I don't think you are going to get good speed as you are working with a lot of data and probably would probably need to handle that by working directly with the images and prefecting them and getting them aligned correctly rather than having cocos2d do it for you. I am not saying it isn't possible just my thoughts.
Can you provide a screenshot of what you are talking about with the animation being "broken" or at least describe it further?
Interesting. So are you just updating the atlas sprites rect directly to animate it? Rather than creating an animation action based on frames (the default cocos2d way)? I didn't get round to trying that.
For the project I did this on, it consisted of a characters head, around a 3rd the size of the screen. Instead of animating head/eye/mouth movements based on full frames of the head being updated, we imported the head, hair, mouths, eyes all separately and recreated the animations within cocos2d, or in some cases ran atlas based animations just on these smaller AtlasSprites.
That approach may or may not work for you depending on how complex the sequences are.
The other main reason we opted for this method was due to the very large number of animations we required, we quickly started to get a large number of textures needing to be loaded, & so the app size, and texture memory requirements were ballooning quickly.
We were also about to run into the issue you've got, of requiring multiple atlas managers to be used on a single animation, and so would have needed to write something to handle that.
But we had a very particular requirement (& a want to keep under the 10MB 3G download restriction). You may be better off writing some sort of wrapper to toggle between different atlas managers in your case.
I think user @LongJonnyE posted an article about using several AtlasSpriteManager objects for 1 animation.
I think he mentioned in this forum, but if you can't find it, it's on his blog:
http://johnehartzog.com/2009/05/using-cocos2d-atlasspritemanager/
You must log in to post.
