cocos2d for iPhone

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

1. 

   fg1921
   Member

   Hi All

   I've been playing around with cocos2d for a day now and all was great with my examples when trying 'attachInView: window' where the code was attaching cocos2d to the main window. However in my app I need to use cocos2d in a UIViewcontroller (one of the UITabViewController tabs) and so I attached Cocos2d to the main blank UIView that's in my nib file (which has nothing else).

   However the app becomes extremely slow, unresponsive almost. All other views (from the tab) no longer accept touch events and only the cocos2d view seems to receive touch. Moreover, when the tabbar button for the cocos2d view is tapped, it takes more than 2 seconds on a 3GS to load a simple view with three images (one bg image and two other which are appox 280x280 pixels each). Rotation Animations are also slow.

   Any idea what I'm doing wrong?

   Posted 1 year ago #
2. 

   fg1921
   Member

   Okay it seems if I do the following all seems well:

   - (void) viewDidDisappear:(BOOL)animated {
   if ([[CCDirector sharedDirector] openGLView] != nil) {
   [[CCDirector sharedDirector] end];
   }
   }

   The app becomes responsive again in all other views. And the in viewDidAppear I re-attach to a new scene. Is this normal?

   Posted 1 year ago #
3. 

   fg1921
   Member

   Any insight would be really appreciated. The weird jitter is driving me nuts (a simple repeat 360 rotation of a sprite). The above code make the app responsive in other views but the open gl view now has this jerkiness during rotation. When I run instruments over it, I found it's doing spending CPU time doing EAGLView swapBuffers and I see a usleep in the stack view.

   Posted 1 year ago #
4. 

   fg1921
   Member

   Please, please help.

   I've got everything working fine however each time I leave the view, the rest of the UIView stuff becomes unresponsive. As mentioned earlier, I have the following working in 'viewDidDisappear':

   [[CCDirector sharedDirector] end];

   and then in 'viewDidAppear' I re-create the scene, the layer and re-run the newly attached scene. This works but now entering the cocos2d view is slow (as it needs to load the sprites each time) and loses previous state/animations etc as everything is re-set. The following (as proposed by someone else in another post) does NOT work:

   [[CCDirector sharedDirector] pause];

   If I do this, the app still is unresponsive. The only thing that works is calling 'end' but that's drastic and kills everything. PLEASE help.

   Posted 1 year ago #
5. 

   zacware
   Member

   I'm having the same problem. I can use pause and resume but it causes the non-cocos2d portions of the app to be slower. Using end works but when I return to the view it won't respond to my runWithScene request

   Posted 1 year ago #
6. 

   zacware
   Member

   I solved it! (at least for me). After doing [[CCDirector sharedDirector] end] I needed to do a [[CCDirector sharedDirector] release]. Then I needed to move my setup code out of viewDidLoad and into viewWillAppear. Now everything works very fast.

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.