cocos2d for iPhone

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

1. 

   Hans Engel
   Member

   I recently started using cocos2d and have run several successful experiments. I recently started a new project, and for some extremely minute reason, everything is going wrong. Here's what happens when I run my app:

   iPhone simulator opens
   Cocos2D logo shows (as it should, for now)
   Logo is replaced by white screen

   And that's all there is. I've added a Sprite that is a background image in the GameScene class implementation, but it does not show UNTIL I close the application.

   When I press the Home key, for a half-second the white layer disappears and I can see the background sprite, shrinking along with the rest of the app.

   

   My code is quite regular and there's nothing really different when I compare it to my other experiments, except that I have subclassed Scene and made it into GameScene (but nothing irregular is performed there, either).

   I have pasted my code online: http://pastie.org/607897 .

   I have NO idea what I missed / what I am doing wrong. Any ideas?

   Posted 2 years ago #
2. 

   Frank84
   Member

   In our projects we do the makeKeyAndVisible before the runWithScene and attachInWindow instead of attachInView. That might fix it.

   [[Director sharedDirector] attachInWindow:window];
   
   [window makeKeyAndVisible];
   
   GameScene *gs = [GameScene node];
   [[Director sharedDirector] runWithScene:gs];

   Posted 2 years ago #
3. 

   Hans Engel
   Member

   Unfortunately that didn't fix it. :(

   Posted 2 years ago #
4. 

   jeffam112368
   Member

   Hey I had this same problem and found out the problem is that you must pass the interface name of your AppDelegate to the UIApplicationMain call. See below:

   #import <UIKit/UIKit.h>

   int main(int argc, char *argv[]) {

   NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init];
   int retVal = UIApplicationMain(argc, argv, nil, @"SheezAppDelegate");
   [pool release];
   return retVal;
   }

   NOTE: if you pass default instead of @"SheezAppDelegate" above, it will show the white window. Of course, in this example my AppDelegate subclass is called SheezAppDelegate, so make sure this corresponds to whatever you called it in your code.

   Give it a shot, lemme know.

   Posted 2 years ago #
5. 

   Hans Engel
   Member

   I know what you mean, but my case is a bit different. I had changed main.m already - I am sure my app delegate is being loaded, since I *can* see the sprite, but only during the exit process of the program when the white layer is deleted.

   I'm going to just try remaking the app for now, and hope that minute thing gets fixed on its own.

   Posted 2 years ago #
6. 

   Hans Engel
   Member

   Uh oh.

   I just remade this application (once using Core Data and once not using Core Data) and get the same results, even when following a Cocos2D "Hello World" tutorial that DID work when I first started testing Cocos2D.

   Could there be something wrong with the frameworks on my computer? That explanation doesn't make sense, because there are the earlier test applications using Cocos2D that still work perfectly.

   I used a fresh download of Cocos2D for source code / library inclusion, so I don't think that that could be the problem.

   Posted 2 years ago #
7. 

   Hans Engel
   Member

   I just copied the exact code from the working earlier test project into a new project, and it is not working. I'll try replacing the frameworks with the older ones next.

   Posted 2 years ago #
8. 

   Hans Engel
   Member

   Aha! I've found the problem. It seems that

   in a Cocos2D project, one must retain the automatically generated MainWindow.xib file, but delete the "Window" object inside the interface.

   Posted 2 years ago #
9. 

   Tim
   Member

   Thanks for sharing Hans cause I just started looking at Cocos2d and had the same problem.

   Posted 2 years ago #
10. 

    richardfu
    Member

    Hans, how you do that?
    Could you explain more specific.
    Thanks.

    Posted 2 years ago #
11. 

    Hans Engel
    Member

    Oh, sorry, I was not watching this thread - thank you to richardfu for alerting me :) Here's how:

    Open your MainWindow.xib file in Interface Builder. Switch to the Document window (the one which displays the principal elements of the interface) and delete the row which has the title "Window." Save and exit Interface Builder, and your problem is fixed!

    Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.