cocos2d for iPhone

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

1. 

   neurofluid
   Member

   Hi All,

   I've been beating my head against this problem for over a day now and either I'm not getting it or something's wrong.

   In my game I have a HomeScene, in which the user chooses 'Play Now', 'How To Play' or 'About'. I'm using AtlasSpriteManager and a Menu to display the buttons.

   If the user selects 'Play Now', Director is told to ReplaceScene to an intermediary scene called 'SelectPlayLevel', on which the user chooses 'Easy', 'Medium', 'Hard' which sets the level of difficulty. Pretty rudimentary stuff so far.

   Once the user has chosen their level, they go into the heart of the game (it's a card game) by Director being told to ReplaceScene with GamePlayScene. Once they've won, Director is told to ReplaceScene with a new one (YouWonScene) which shows a nice little animation, congratulations, etc, with another AtlasSpriteManager/Menu combo showing two options: 'Play Again' and 'Menu'.

   'Menu' tells Director to ReplaceScene with HomeScene (back to the main title screen). Selecting 'Play Again' tells Director to ReplaceScene with GamePlayScene, with the same settings etc, and this is where the problem lies: the user gets sent to the GamePlayScene and while not visible at all, the clickable areas where 'Play Again' and 'Menu' were displayed on the YouWonScene scene are still 'hot' and react to a touch. Instead of the playing card sprite being clicked, pressing that area will either send the user to the HomeScene, or restart the GamePlayScene (as if the 'Menu' or 'Play Again' button was pressed).

   I'm really pulling my hair out trying to figure this out, so I hope I've made it clear enough here and someone can give me some advice.

   I'm using Cocos2d 0.8.1, XCode 3.2, Simulator 3.1/iPod 3.1

   Thanks!

   Posted 2 years ago #
2. 

   neurofluid
   Member

   Figured out a solution: it turns out that I was issuing a pauseBackgroundMusic in the onExit method (I'm still not 100% if I understand overriding the onExit/onEnter methods yet). Once I moved that command somewhere else, the lingering hot spots disappeared.

   I've seen other mentions that the SimpleAudioEngine stuff is a bit buggy...

   Posted 2 years ago #
3. 

   Mitch Lindgren
   Member

   I'm not sure what the specific issue was in your case if moving pauseBackgroundMusic solved the problem. Were you remembering to call [super onExit] in your onExit method?

   Generally what causes issues like these is a scene or layer not being released when it should - a memory leak, in other words. If you retain, alloc or copy a scene/layer and then forget to release it later, when it's removed by the director it won't actually deallocate. That means that any elements like menus on it will no longer appear on screen, but will still be active and able to receive input. It also means your app will eventually run out of memory and crash.

   Scheduled selectors retain their targets, so if you have any selectors scheduled on your layers, make sure you unschedule them when you're done with the layer. (The onExit method is a good place for this.)

   Posted 2 years ago #
4. 

   Steve Oldmeadow
   Administrator

   "I've seen other mentions that the SimpleAudioEngine stuff is a bit buggy..."

   Where have you seen these "mentions"? If there are bugs report them and they will be fixed. I fail to see how pauseBackgroundMusic could have anything to do with your problem.

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.