A fast, easy to use, free, and community supported 2D game engine
BigPapoo
Member
Hi,
I'm wondering what is best practice (if any) between using [CCSprite runAction:bla bla..] and updating my sprite from within each call to Update()/Draw() pair ? Which one is better/worse regarding perfs ? Any link to comparison charts would also be appreciated.
--G.
The Cocos2D actions are there for you so you don't have to manually calculate each sprite's position and manually move them each frame. The only time I manually move a sprite is my player's spaceship. Also, if you are using a physics engine like Box2D or Chipmunk then you would let the physics engine move the sprite instead of using actions.
Why make so much more work for yourself if you don't have to. There are a lot of different types of actions at your disposal.
chrisco
Member
I agree with David. I'm sure that some people would be able to squeeze better performance out of their game by updating their sprites themselves, but I for one would most likely completely destroy the performance of my game :P I find the actions really useful and with clever use of CCSequence, CCCallFuncN, etc, really flexible.
I haven't had to worry about performance yet with over 150 animated sprites all running actions against a full background image on an iPad (60fps) so I personally won't be looking for an alternative until i need it.
You must log in to post.
