cocos2d for iPhone

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

1. 

   jj0b
   Member

   I have an app that has been in the store for almost four months. Yesterday I opened the project in Xcode 3.2.3 with SDK 4.01 for the first time. When I build and run the app on my 3G phone running iOS 3.1.3 everything works perfectly as it always has. When I build and run on my other 3G phone running iOS 4.01 something very strange happens.

   In the app there is a scheduler to spawn balloons. I placed an NSLog at the start of the spawnBalloon method that is called by the scheduler. The scheduler is set at 1.2 seconds and it does wait that long before calling the method the first time, but after that the method gets called so extremely fast that the method never gets to execute. If I put two NSLogs at the start of the method it has time to print both of those but never makes it further. I have attached a small section of the console log that shows how insanely fast the method is being called.

   2010-07-29 18:14:41.403 TQG[2252:307] start spawnBalloon
   2010-07-29 18:14:41.418 TQG[2252:307] start spawnBalloon
   2010-07-29 18:14:41.431 TQG[2252:307] start spawnBalloon
   2010-07-29 18:14:41.447 TQG[2252:307] start spawnBalloon
   2010-07-29 18:14:41.463 TQG[2252:307] start spawnBalloon

   Instead of the method being called every 1.2 seconds it is being called somewhere around every 15 milli seconds which doesn't give enough time for the method to execute.

   I cannot understand why this would happen only on my phone running IOS 4.01.

   EDIT: I should also mention that the version in the store that was built using an older version of Xcode runs perfectly fine on ALL iOS versions. Also in Xcode 3.2.3 I am using iOS 4 as the Base SDK and building against iOS 3.

   Posted 1 year ago #
2. 

   chrisco
   Member

   Can you post the post the code where you call the schedule and the scheduled method as well?

   Posted 1 year ago #
3. 

   michaelm
   Member

   Do you happen to schedule the timer multiple times. I ran into something like that, scheduling a timer in touch check, unschedule in cancel. But the schedule was getting called multiple times in touch which then speeded everything up. It ran faster and faster. That was a tough one to find.

   I know you built it and it worked in 3.1 but possibly a small thing got changed in between?

   Posted 1 year ago #
4. 

   Clain
   Member

   What version of cocos are you using ? When you compile older versions of cocos with the base SDK set as 4.0, it does compile but there are several warnings. Some of them cause the interval actions not to work properly (e.G. transitions do not transition and jump straight to the next scene, same thing with MoveTo actions, etc). And there's one warning regarding the use of the usleep function. Could it be that your problem is related to this? (either the usleep or the interval actions not working)

   Also, your time interval of 15 milliseconds seems to be 1/60. Are you using the DisplayLink director at 60 fps? If so, that would make sense with the above.

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.