cocos2d for iPhone

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

1. 

   jonathan0382
   Member

   Hi all,

   I am having problems with a non-responsive accelerometer. At least it is non-responsive some of the time.

   Last week my game was simply a menuscene with two buttons. The first would take you straight to a gamescene, with a child gamelayer, in which you used accelerometer controls to move a sprite. Very simple.
   Just so that it did something I made the second button do exactly the same.

   This week I added a level-select scene between the menuscene and the gamescene. The levelscene has a levellayer which handles the touch controls, and then the gameScene uses an initWith to change variables depending upon the level selected. Again, very very simple stuff. The second button on the menuscene still takes the user directly to the gamescene, bypassing the levelscene.

   Q: when I click on the second button, my accelerometer controls work fine. But when I go to the gamescene via the levelscene, my controls do not. The gamescene is subclassed, so the same thing is called each time, so I've got no idea what to even look for. Am I missing something here?

   Has anyone experienced this, or have any suggestions?

   to clarify:
   menuscene button1 --> levelscene --> levellayer --> gamescene --> gamelayer with WORKING accel controls
   vs.
   menuscene button2 --> gamescene --> gamelayer with NON-WORKING accel controls

   Posted 2 years ago #
2. 

   jonathan0382
   Member

   Well, I found out what was causing the problem and it was the transition I was using to enter the gameScene.

   Upon this the accelerometer responded for about a second, and then stopped:

   [[Director sharedDirector] replaceScene:[FlipXTransition transitionWithDuration:1 scene:gs]];

   Whereas upon this the accelerometer functions correctly within the scene:

   [[Director sharedDirector] replaceScene:gs];

   I am using cocos2d iphone 0.8 beta, and read somewhere about the transitions now waiting to finish before init'ing the next scene. Is this causing my problem? I would love to use the transition, so does anyone have any suggestions?

   I noticed a second problem (bug?), again caused by the FlipXTransition. My project is in landscape, and when I run a FlipXTransition it transitions as it should, but then goes to portrait mode for about a second, before returning back to landscape mode. Any suggestions?

   Posted 2 years ago #
3. 

   Clain
   Member

   Does your level scene (the one being replaced) use accelerometer as well ?

   For the FlipXTransition : do you mean the simulator goes to portrait or the rendering on screen goes to portrait ?

   Posted 2 years ago #
4. 

   jonathan0382
   Member

   The levelScene being replaced does not use the accelerometer. If it did would that make a difference?

   The simulator stays in landscape, but the rendered screen goes to portrait and then back again.

   (p.s. how did you get the custom avatar? I looked in the profile edit screen but didn't see an option to change it)

   Posted 2 years ago #
5. 

   Clain
   Member

   I have no idea what's causing your problem. If your level scene used accelerometer, theoretically it wouldn't make any difference. But I was thinking maybe when the level scene is deallocated and dismisses the accelerometer, that could affect the accelerometer on the game scene for some odd reason. But your scene doesn't use accelerometer so...

   It's still weird that the accelerometer works fine when you don't use any transition between your scene. Did you try with another transition like FadeTransition for instance ? You first need to determine if that comes from one particular transition or from using a transition.

   (for custom avatar, read this thread)

   Posted 2 years ago #
6. 

   jonathan0382
   Member

   Good thinking. I'll try it with different transitions and see if there are any patterns.

   (thanks for the link).

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.