cocos2d for iPhone

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

1. 

   MMorpheus
   Member

   Hello everyone!

   First of all I would like to thank anyone that has ever poster in this forum. It is an awesome resource to fix most of the problems anyone gets when using cocos.

   I am getting a huge delay between when I tap the screen and when the ccTouchesBegan function is called. Sometimes almost a second.
   I have read that it might happen when there is a high CPU load but I have 60 FPS with slight drops (but never too intense).
   And it seems like it is degrading as I play more and more. The delay is increasing the more I play.

   Can anyone help me here? Has anyone stumbled into a similar problem?

   Thanks for any help you can give me.

   Posted 1 year ago #
2. 

   MMorpheus
   Member

   BUMP!
   I still have this nasty issue.
   I get a large delay between the time I tap the screen and the time the ccTouchesBegan method is called.

   Can you help me?

   Posted 1 year ago #
3. 

   skyhawk
   Member

   stick a breakpoint in your cctouchesbegan.
   touch the screen. does it break immediately or 1s later?

   Other debugging ideas:
   what's going on in your main loop at the time of click?
   when you click, do you have a sleep(1000)? =P

   Posted 1 year ago #
4. 

   lordbritishix
   Member

   I have exactly the same problem but I didn't get any reply from my question. My frame rate cruises around 55-60 but each time I touch and drag my fingers around the screen, my hero, which is controlled by the accelerometer, starts to get some input lag despite the fact that my frame rate is not getting affected by touch. I am guessing that the touches are being queued internally so it introduces many touches that needs to be processed. Tried disabling the touch for all of my layers but I still get the same problem :|

   Posted 1 year ago #
5. 

   araker
   Moderator

   Take a look at this topic.

   Posted 1 year ago #
6. 

   sabshire
   Member

   One other thing to note: I had a similar issue in my game when I updated to iOS4. For me, I was able to resolve the issue by switching to using CCSpriteBatchNode and CCSpriteFrameCache for creating my sprites, instead of [CCSprite spriteWithFile:]

   Until I did that, I had sporadic results but without fail it would eventually lag on touches.

   Posted 1 year ago #
7. 

   lordbritishix
   Member

   thanks for the help guys. Finally figured out how to fix the little bugger :) had to move the setting of the player position outside of the accelerometer callback and had to lower the accelerometer callback frequency from 1/60 to 1/30. This has been haunting me for weeks and I finally squashed it! :)

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.