How to Make a Game Like Jetpack Joyride using LevelHelper and SpriteHelper [Cocos2D Edition] – Part 2

Bogdan Vladu

This is a post by special contributor Bogdan Vladu, an iOS application developer and aspiring game developer living in Bucharest, Romania.

Learn how to make a game like Jetpack Joyride with SpriteHelper and LevelHelper!

Learn how to make a game like Jetpack Joyride with SpriteHelper and LevelHelper!

Update 1/9/2013: This tutorial is now deprecated. We now have a newer, updated version of this tutorial, check it out!

Welcome back to our Jetpack Joyride tutorial series! In this tutorial series, we are making a game similar to Jetpack Joyride using Cocos2D and Box2D, and the LevelHelper and SpriteHelper tools.

So far, we’ve got a working level with background art that scrolls continuously. Check out how we did it in Part One.

By now, you should be pretty comfortable working with LevelHelper and SpriteHelper, at least when it comes to the basics like adding objects to the levels.

In this second part of the tutorial, we’ll focus on adding some movement and activity to the game. Lasers, coins, a flying player-character, the beginnings of collisions… it’s all coming up!

To follow along with this tutorial, you’ll need to have the RocketMouse project where we left off in part one. If you don’t have this already, you can grab a copy of the project so far here.

So let’s get that mouse flying!

Getting Started

The next step in creating our Jetpack Joyride game is to add some elements that the player will directly interact with: lasers and coins. Adding these elements is also a good way to begin learning how to implement animations and sensors using LevelHelper.

Since we want the lasers to go on and off, we need to make them animations. As for the coins, we want to know when the player collides with them, but we don’t want the player to bounce off them. To do this, we need to make them sensors.

Having grappled with the basics of animation and collision response, we’ll expand the concepts to other elements of our game, including the player. We’ll learn how to create tags to track collisions, then put it all together with some actual code!

Before we get started, you might want to open your current LevelHelper project and save the level as level03 (this way you’ll have the old level to look back on). If you do this, be sure to add the new Level into your Xcode project, and update the line that selects the level to choose level 3 like so:

lh = [[LevelHelperLoader alloc] initWithContentOfFile:@"level03"];

Working With Animations: Adding Lasers

How we’ll use the animations in gameplay is fairly simple. When the player makes contact with a laser, we’ll just test what frame the animation is on. If it’s the frame with the laser-off sprite, we’ll leave the player alone. If it’s the frame with the laser-on sprite, then we’ll kill the player.

To create an animation for our lasers, go to the available sprites list on the right panel in LevelHelper, and Control-Click (or right-click) on one of the laser sprites. Then choose “Open SpriteHelper scene” from the menu.

SpriteHelper will open with the correct scene. Navigate to the Animation section, click the + button to create a new animation, then double click on the animation name and call it “Laser.”

Now go in the sprites list and select the vertical laser. Go back to the animation section and click Add Frame. This will add the two sprites to the animation.

Arrange the frames in the correct order (off and then on, or laser1 and then laser2) by clicking the up and down arrows. Set the speed to 3 and make sure the Start At Launch and Loop Forever options are checked.

When you’re done, hit Command-S to save the scene.

Now let’s switch back to LevelHelper and work with the animation we just created. You’ll see that an Animations section has already been added for you in LevelHelper, as in the image below.

There are two ways to activate the animation. I will demonstrate both.

The first way is to drag the animation into the level just as we did with the sprites.

The second way is to attach the animation to a sprite that’s already in the level. In this case, I’m adding the animation to the laser sprite.

Go to the sprites section. We haven’t added the laser sprites to the level yet, so drag one of them (doesn’t matter which) from the list into the level, and make sure that sprite is selected. Then go to the General Properties section and select the Laser animation from the list.

Continue adding lasers to the level, until a satisfying amount of danger has been achieved. You can rotate and scale the lasers by using the handles that appear when you select a sprite.

My level now looks like this:

If you look at the laser shape you can see that the sprite is a full quad.

In our game we want the mouse to die only when it hits the actual laser in the sprite (the yellow part), so let’s make the shape smaller.

To do this we can define a shape like we did for the dog and cat, or we can modify the Shape Border property under the Physics menu using predefined values. Since you already know how to create a shape with points, let’s try it the second way.

Select the laser1 image from inside the Images section of LevelHelper. Right click on it and select Open SpriteHelper Scene.

Once the SpriteHelper scene is open, click on the “laser1” sprite. Because the laser is an animation, we need to modify the physics properties of the first frame of the animation – in this case the “laser1″ sprite. Animations have the physics properties of the first frame.

With laser1 selected, go to the Physics menu and enter 70 and 40 for the Shape Border values. This will make the shape of the sprite be equal to the sprite size, minus the values you enter here. You can see the visual representation in the view.

Back in LevelHelper, we can see that all lasers have been updated with the correct shape.

Now select all lasers and add them to our parallax. Enter 1 and 0 for the ratio.

Save the level, and if you build and run your game it will now have animating lasers!

Level with animating lasers

Working With Sensors: Adding Coins

Now for the coins. Remember, we want to make the coins sensors so that the mouse can pass straight through them without bouncing off, but still allow us to detect when there is a collision.

To make the coins sensors, select the coin sprite from the sprites list inside LevelHelper, right click (or Control-Click) and choose Open SpriteHelper Scene.

With the SpriteHelper scene opened, select the coin sprite and check the Is Sensor, Is Circle and Can Sleep options on the Physics menu. Then save the scene.

  • Is Sensor: makes the body trigger a collision, but not a collision response.
  • Is Circle: makes the shape of the body circle-based.
  • Can Sleep: speeds up simulation of the physics.

Now add the coin sprite to the level and place it as you see fit. Use the Clone Tool to easily clone the coin with the direction offset you prefer.

Now my level looks like this:

Add the coins to the parallax, set the ratio to 1 and 0 and save the level. Compile and run your project, and now you have coins!

Adding coins to the level

The project with all of our work up to this point can be downloaded here.

Adding the Player

Now that we have a good-looking level with all the basic components, let’s create the player and its accompanying animations.

Open SpriteHelper and go to File\New to create an empty sprite sheet. Then in Finder, navigate to the directory where you saved the art for this game. Once you’re there, select and drag onto the SpriteHelper window all the mouse sprites and the rocket flames.

We now need to create one single image with the art we just imported. This is an essential step before creating the animation. All engines supported by LevelHelper and SpriteHelper expect that frames in an animation are part of the same image file.

Switch to the Sheet Editor menu if you aren’t there already and deselect Crop, because we don’t want to trim the frames of the mouse animation. Click Pack Sprites to arrange all the sprites into the sprite sheet.

Next, switch to the Animation section of SpriteHelper. We’ll we’ll create all the animations we need here, exactly as we did for the laser.

Using the same technique you learned earlier, create five animations with the properties listed below.

If you forgot how to create animations, for each animation, click the + button, and double click to name it. Then select the required frames for that particular animation, set the speed, and make sure to check the Loop Forever option for the one that needs to loop.

1) Animation Name: mouseRun
Start At Launch: YES
Loop Forever: YES
Speed: 0.400 (default)
Repetition: 1.000 (default)
Frames: rocketmouse_1_run, rocketmouse_2_run, rocketmouse_3_run, rocketmouse_4_run

2) Animation Name: flame
Start At Launch: YES
Loop Forever: YES
Speed: 0.400 (default)
Repetition: 1.000 (default)
Frames: rocket_flame1, rocket_flame2

3) Animation Name: mouseFly
Start At Launch: YES
Loop Forever: YES
Speed: 0.400 (default)
Repetition: 1.000 (default)
Frames: rocketmouse_5_fly

4) Animation Name: mouseDie
Start At Launch: YES
Loop Forever: NO
Speed: 0.400 (default)
Repetition: 1.000 (default)
Frames: rocketmouse_7_die, rocketmouse_8_die

5) Animation Name: mouseFall
Start At Launch: YES
Loop Forever: NO
Speed: 0.400 (default)
Repetition: 1.000 (default)
Frames: rocketmouse_6_fall

Once you’re done, hit Command-S to save the scene. In the Save dialogue, navigate to the Images folder inside your Xcode project Resources folder, and save the scene as “mouse.”

Back in LevelHelper, we can find all of our new animations in the Animation section.

Drag the mouseRun animation onto the main screen (the one with a red border). Place it just to the left of the screen.

Then drag the flame sprite and place it right under the red tank on the back of the mouse.

The result should look something like this:

If you look closely, you’ll see that the flame sprite is on top of the red tank. Let’s put it behind the tank, so it looks more like the flame is coming out of the tank. Do this this, select the flame sprite and under General Properties, set Z Order to -1.

If you run the level at this point using Scene Tester (press Test Level button) you might or might not be able to see the mouse.

This is because the sprites are rendered using batch nodes (all the sprites at the same time). To make the mouse be on top of all the other sprites in the level, we need to change the Z Order of the batch node (the image file).

Inside LevelHelper go to the Images section and double click on the Z Order field for mouse.png. Enter a value of 4.

We want the player to always be on top of everything, and we’re going to add more images soon. That’s why we’re putting a larger value here.

Running the level now, you can see the mouse running on the scene, but it does not perform any collisions.

It actually is performing collisions with the dogs and cats, but because the mouse and other objects are all static, nothing happens.

Time to make the mouse and the flame sprites dynamic! Open the SpriteHelper scene for the mouse:

Then select all the sprites and make them dynamic. Because we don’t want the mouse to rotate when it collides with any other sprite, select the Fixed Rotation option also.

For the two rocket flame sprites, we also need to check the Is Sensor option. This is because later we’re going to be attaching the flame to the rocket tank.

Save the scene when you’re done!

Running Scene Tester again, we will see the mouse falling out of the screen. This is because the mouse is responding to gravity. Let’s make him stay on the screen.

Click the Physic Boundaries button.

From the Physic Boundaries window, click Create.

We’ve now created the boundary, but we want to edit it so that it’s right under the mouse in the middle of the floor, where the mouse will walk. Inside the Physic Boundaries window, click Edit.

You will now see four red handles on the corners of the physic boundary. Drag any of the bottom handles to move the boundary so that it’s under the mouse’s feet.

You should have something similar to this:

When you’re satisfied with your physic boundary, press the Editing button to stop the editing process.

Running the level in Scene Tester, you will see the mouse collides with the dogs and cats and stays on the screen, but, alas, there is yet another problem!

This time, the flame is falling off the screen. That’s because it’s a sensor and so it does not collide with any object and isn’t attached to the mouse’s body. But w can connect the flame to the mouse by creating a distance joint.

Go to the Joints section inside LevelHelper, select Distance Joint from the list and click the green + button.

Now let’s select the sprites we want the joint to connect.

Select the joint from the list (if not already selected), then on the Body A property, click and hold the circle icon. Then drag your mouse over the flame sprite. When the text says rocket_flame_1, release the mouse. (This is exactly the same process as connecting an outlet inside Interface Builder in Xcode.)

Now repeat the process for Body B, only this time select the mouse.

Now let’s put the joint’s anchor points closer together.

Select A in the joint property, drag the handle that shows the flame sprite, and put the anchor right on top of the tank.

Repeat the process for the other anchor point. Select anchor B, drag the handle and put the anchor point next to the other.

If you run the level in the Scene Tester, you’ll see the flame now stays attached to the mouse. w00t!

We now have almost everything we need in order to start coding the game!

Creating Tags to Perform Collisions

In order to perform collisions between our sprites, we need to have a way to register collisions between sprites of one type with sprites of other types.

We will need to separate our sprites into types using tags. So all dog sprites will have the tag “DOG” and all cat sprites will have the tag “CAT.”

To create the tags, inside LevelHelper click the Define Tags button.

In the Define Tags window, set the name for the new tag and click the Add button to create it. Create the following tags: DOG, CAT, LASER, COIN, PLAYER.

Now that we have the tags defined, we need to assign the tags to sprites.

Select all the dog sprites from the list of sprites on the left. Then under General Properties, assign the DOG tag to all of those sprites.

Repeat the process for all the sprites. Assign PLAYER to the mouse sprite, CAT to all the cat sprites, LASER to all the laser sprites, and COIN to all the coin sprites.

When you’re done, save the level with Command-S.

A project with all of our progress so far can be downloaded here.

Coding the Game Logic

We are now (finally) ready to start coding our game. So let’s move back to Xcode, open our project and start the real fun.

First let’s be sure to include the new art (mouse.png). At this point your resources folder should look something like the following:

In order control the movement of the parallax and allow the player to jump, we need to have a few variables that will point to the objects created by LevelHelper. Add these lines in HelloWorldScene.h inside the class definition.

LHParallaxNode* paralaxNode;
LHSprite*   player;
b2Body*     playerBody;
 
LHSprite*   rocketFlame;

Then outside the class definition, right before the @end and after +(id)scene;, add the following method signature:

-(void) retrieveRequiredObjects;

Inside HelloWorldScene.mm, define the new method wherever you see fit, but make sure it’s inside the class declaration. In my case, I placed it right after the init method.

-(void) retrieveRequiredObjects
{
    //Retrieve pointers to parallax node and player sprite.
    paralaxNode = [lh paralaxNodeWithUniqueName:@"Parallax_1"];
    NSAssert(paralaxNode!=nil, @"Couldn't find the parallax!");
 
    player = [lh spriteWithUniqueName:@"player"];
    NSAssert(player!=nil, @"Couldn't find the player!");
 
    playerBody = [player body];
    NSAssert(playerBody!=nil, @"Error taking the body from the player LHSprite.");
 
    rocketFlame = [lh spriteWithUniqueName:@"flame"];
    NSAssert(rocketFlame!=nil, @"Couldn't find flame sprite!");
 
    [rocketFlame setVisible:NO]; //You can do it in LH, but I do it here so you guys can see it in LH
}

Here we are taking pointers to the parallax by giving the unique name of the parallax assigned in LevelHelper.

Then we’re taking the pointer to the player sprite, also by giving the unique name. You might need to modify the unique name to read “player” as shown in the screenshot below if it isn’t set to that already.

Similarly, you should change the unique name of the flame to “flame” so it matches the code.

When you use spriteWithUniqueName to look up a sprite, you get a LHSprite* instance, which is a class derived from CCSprite. From this LHSprite* instance we take the pointer to the Box2d body of the player, because we will need to make the body jump later.

We then take the pointer to the flame sprite and make it invisible. We only need to see the flame when the player is flying. (We could also have done this inside LevelHelper by unchecking the Visible option in the General Properties section.)

Now that we have defined this new method, let’s call it (after we’ve loaded the level).

lh = [[LevelHelperLoader alloc] initWithContentOfFile:@"level03"]; // or level02 if you never changed it
 
[lh addObjectsToWorld:world cocos2dLayer:self];
 
if([lh hasPhysicBoundaries])
    [lh createPhysicBoundaries:world];
 
if(![lh isGravityZero])
    [lh createGravity:world];
 
// Add this
[self retrieveRequiredObjects]; // Retrieve all objects after we’ve loaded the level.

Compile and run the code, and if the flame is invisible when you run it, you know it’s working so far! :]

The flame is now invisible.

Making the Player Fly

Now that we have retrieved the player from the loaded level, let’s make him fly!

Add the following inside the HelloWorldScene.h class definition:

float  playerVelocity;
bool   playerWasFlying;
bool   playerShouldFly;

We will use this to make the mouse fly when the user touches the screen.

Now inside HelloWorldScene.mm, replace the touch functions with the following:

- (void)ccTouchesBegan:(NSSet *)touches withEvent:(UIEvent *)event 
{    
 
    playerVelocity = 0.5f;
    playerShouldFly = true;    
    [rocketFlame setVisible:YES];
    [player startAnimationNamed:@"mouseFly"];
}
////////////////////////////////////////////////////////////////////////////////
- (void)ccTouchesMoved:(NSSet *)touches withEvent:(UIEvent *)event
{
 
}
////////////////////////////////////////////////////////////////////////////////
-(void) cancelPlayerFly
{
    playerShouldFly = false;
    [rocketFlame setVisible:NO];
    playerWasFlying = true;
    playerVelocity = 0.0f;
}
- (void)ccTouchesEnded:(NSSet *)touches withEvent:(UIEvent *)event
{       
    [self cancelPlayerFly];
}
- (void)ccTouchesCancelled:(NSSet *)touches withEvent:(UIEvent *)event 
{
    [self cancelPlayerFly];
}

Inside the ccTouchesBegan method, we’re saying that when the user touches the screen, the player should start flying, the rocket flame should become visible and the flying animation should start on the player sprite.

Next we start the animation name “mouseFly” on the player LHSprite* instance that we retrieved in the retrieveRequiredObjects method.

When the player stops touching the screen, or the touch is canceled, we stop making the player fly by calling the new method “cancelPlayerFly.” We also hide the flame because the player is no longer flying.

But this isn’t enough. We set up when to show the player flying, but we haven’t implemented the actual flight. That requires adding the following at the end of the “tick” method:

if(playerShouldFly)
{
    playerBody->ApplyLinearImpulse(b2Vec2(0, playerVelocity), playerBody->GetWorldCenter());        
 
    playerVelocity += 0.01f;
 
    if(playerVelocity > 1.5f)
        playerVelocity = 1.5f;
}

Here, we check if the player should fly and if the test is true, we apply a linear impulse with a horizontal direction (on Y) on the mouse box2d body.

We then make the velocity bigger and bigger, so the player will look like they are taking off from the ground, gaining speed with time.

If the player’s velocity reaches a certain speed (1.5), we stop the speed from increasing further.

Compile and run the game, and now you can make the mouse fly by touching the screen!

A flying rocket mouse!

Where to Go From Here?

You can download the full project up to this point here.

Thanks for staying with me this far! We’ve made a huge amount of progress for one tutorial. And we’re only at the end of Part Two!

You won’t want to miss Part Three, where we’ll fully implement collisions, animate the player’s flight and landings, and add sounds. We’ll also make the player die when it touches the dogs, cats or lasers and add a restart screen.

Then in the fourth and final part, we’ll add bunnies that will run through the level to give the player more scoring opportunities, add a score display, and finally, create a scrolling background scene that will be visible through the windows.

Clearly our fun is just getting started. Keep your questions, comments and suggestions coming!


This is a post by special contributor Bogdan Vladu, an iOS application developer and aspiring game developer living in Bucharest, Romania.

User Comments

41 Comments

[ 1 , 2 , 3 ]
  • blaydelk wrote:I have been working on my coding skills but I have run into a problem:


    -(void) setupCollisionHandling
    {
    [loader useLevelHelperCollisionHandling];
    [loader registerBeginOrEndCollisionCallbackBetweenTagA:PLAYER andTagB:BUDDHA idListener:self selListener:@selector(mouseCoinCollision:)];
    }

    I have tagged the Player and Buddha in LevelHelper and have command s saved to Xcode but for some reason Xcode thinks "PLAYER" is undeclared. I have been going between part two and part three of the tutorial but I can't spot the problem.

    One other question, in this line of code:

    player = [loader spriteWithUniqueName:@"JimmRun"];
    NSAssert(player!=nil, @"Couldn't find the player!");

    Can I change the unique name "JimmRun" in LevelHelper when I set the tag?



    Hi!
    If you add new tag in LevelHelper, you mast generate new code.
    You can change the unique name, no problem!
    Sorry for my english=))
    ProJ0Ra
  • OK, I need to know something about generating new code (because this has caused multiple problems for me). If I generate new code in level helper, there are two options, manual and automatic. I have been choosing manual but this results in my needing to move files to trash in Xcode. Does the automatic option update both the code in my project folder on the desktop as well as the actual files in the xcode file?
    blaydelk
  • blaydelk wrote:OK, I need to know something about generating new code (because this has caused multiple problems for me). If I generate new code in level helper, there are two options, manual and automatic. I have been choosing manual but this results in my needing to move files to trash in Xcode. Does the automatic option update both the code in my project folder on the desktop as well as the actual files in the xcode file?


    I generate code manualy:
    1) You most delete(Move to Trash) LevelHelper folder from xCode.
    2) Delete LevelHelper folder from you project folder in Finder.
    3) Generate new code in level helper with manual option to you project folder.
    4) Add new LH folder in xCode.
    ProJ0Ra
  • Need the help again from this forum.

    I have a problem with this line:
    Code: Select all
    [player startAnimationNamed:@"mouseFly"];

    I get the following exception:
      2012-09-02 23:13:02.471 Rocket[42748:10a03] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[LHSprite startAnimationNamed:]: unrecognized selector sent to instance 0x8231e00'
      *** First throw call stack:
      (0x1985052 0x1b16d0a 0x1986ced 0x18ebf00 0x18ebce2 0xf40f3 0x1986ec9 0x8ef5e 0x8f5cf 0x91481 0x93893f 0x938c56 0x91f384 0x912aa9 0x287efa9 0x19591c5 0x18be022 0x18bc90a 0x18bbdb4 0x18bbccb 0x287d879 0x287d93e 0x910a9b 0xf2f3f 0x1f95)
      terminate called throwing an exception


    On the first page of the thread there is a person with the same problem. He solved this problem by updating the branch in LevelHelper. However I'm using the latests branch. Any ideas how to solve this?

    I'm using LevelHelper 1.4.951 with supporting code 1.4.9x revision 84 and SpriteHelper version 1.8.153

    Thank you for your help.
    bibtex
  • bibtex wrote:Need the help again from this forum.

    I have a problem with this line:
    Code: Select all
    [player startAnimationNamed:@"mouseFly"];

    I get the following exception:
      2012-09-02 23:13:02.471 Rocket[42748:10a03] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[LHSprite startAnimationNamed:]: unrecognized selector sent to instance 0x8231e00'
      *** First throw call stack:
      (0x1985052 0x1b16d0a 0x1986ced 0x18ebf00 0x18ebce2 0xf40f3 0x1986ec9 0x8ef5e 0x8f5cf 0x91481 0x93893f 0x938c56 0x91f384 0x912aa9 0x287efa9 0x19591c5 0x18be022 0x18bc90a 0x18bbdb4 0x18bbccb 0x287d879 0x287d93e 0x910a9b 0xf2f3f 0x1f95)
      terminate called throwing an exception


    On the first page of the thread there is a person with the same problem. He solved this problem by updating the branch in LevelHelper. However I'm using the latests branch. Any ideas how to solve this?

    I'm using LevelHelper 1.4.951 with supporting code 1.4.9x revision 84 and SpriteHelper version 1.8.153

    Thank you for your help.


    I also experience this problem.
    This is because LH only in the development stage.
    I used the alternate function:
    [sprite prepareAnimationNamed:@"animationName" fromSHScene:@""];
    [sprite playAnimation];
    This is not ideal, but for the tutorial approach.
    ProJ0Ra
  • Hi, I've followed the tutorial step by step but my player doesn't have any kind of physics :S
    I mean, I can't get it to work, its still at the same place. In the tutorial you said: "Now the player will fall off the screen", nothing happens to mine...

    I've been trying to fix this for a week and I still don't find which problem is...

    This is the SpriteHelper document:
    http://i.imgur.com/i320W.png


    And the LevelHelper document:
    http://i.imgur.com/txljQ.png

    THIS IS MY .m file, in case it helps:
    http://pastebin.com/LTJLJZqZ

    EDIT:

    Okey I finally fixed it, in case someone has the same error in a future is that I didn't have this at the tick method:

    Code: Select all
    //Iterate over the bodies in the physics world
        for (b2Body* b = world->GetBodyList(); b; b = b->GetNext())
        {
            if (b->GetUserData() != NULL)
            {
                //Synchronize the AtlasSprites position and rotation with the corresponding body
                CCSprite *myActor = (CCSprite*)b->GetUserData();
               
                if(myActor != 0)
                {
                    //THIS IS VERY IMPORTANT - GETTING THE POSITION FROM BOX2D TO COCOS2D
                    myActor.position = [LevelHelperLoader metersToPoints:b->GetPosition()];
                    myActor.rotation = -1 * CC_RADIANS_TO_DEGREES(b->GetAngle());
                }
               
            }
        }
    konedj
  • I added animating coins on the paralax, but it is causing a great FPS drop fro 60 to 1o which is making the game very jerky and game is not at all smooth. I am testing on Iphone 4, FPS is also dropping on simulator and IPad2. The game I am working is for Iphone. When I remove the animated coins from parallax it again starts working fine. Please suggest
    ScottCogniter
  • I'm using animation for the coins and it works fine (without low fps). They are 10 frames.
    konedj
  • This issue I believe was due to newer version of Spritehelper 1.8.218. I had created the coin animations using this version. Now I used my older sprite helper version 1.7.4 and it worked well. So for me this solution worked.
    ScottCogniter
  • Okay, I'm seriously confused.
    I followed the first tutorial and at no point were the lasers even added to the objects sprite sheet. Also, where the hell is this mysterious 'Available Sprites List' on the right panel?
    When I open the Sprite Helper and add the lasers to their own sheet, and try to animate them, my animation tab looks completely different, and their is no 'speed' setting. On top of this, my laser is cut off completely except for the tip of it in the animation.

    What is going on!?
    Infinity-James
  • Hi I have this problem


    2013-04-17 09:15:08.992 cas[18600:c07] -[LHSprite startAnimationNamed:]: unrecognized selector sent to instance 0xa0c2600
    2013-04-17 09:15:09.005 cas[18600:c07] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[LHSprite startAnimationNamed:]: unrecognized selector sent to instance 0xa0c2600'
    *** First throw call stack:
    (0x2513012 0x1ef0e7e 0x259e4bd 0x2502bbc 0x250294e 0x1043d2 0x1f04705 0xa88d3 0xa8f93 0xa636e 0xaf2b1d 0xaf2f02 0xad0d4a 0xac2698 0x321bdf9 0x321bad0 0x2488bf5 0x2488962 0x24b9bb6 0x24b8f44 0x24b8e1b 0x321a7e3 0x321a668 0xabfffc 0x102b16 0x2835 0x1)
    libc++abi.dylib: terminate called throwing an exception
    (lldb)

    I've updated the code with the R159 review

    please help
    jaljz
[ 1 , 2 , 3 ]

Other Items of Interest

Ray's Monthly Newsletter

Sign up to receive a monthly newsletter with my favorite dev links, and receive a free epic-length tutorial as a bonus!

Advertise with Us!

Hang Out With Us!

Every month, we have a free live Tech Talk - come hang out with us!


Coming up in May: Procedural Level Generation in Games with Kim Pedersen.

Sign Up - May

Coming up in June: WWDC Keynote - Podcasters React! with the podcasting team.

Sign Up - June

Vote For Our Next Book!

Help us choose the topic for our next book we write! (Choose up to three topics.)

    Loading ... Loading ...

Our Books

Our Team

Tutorial Team

... 55 total!

Editorial Team

... 22 total!

Code Team

  • Orta Therox

... 1 total!

Translation Team

  • Zihan Xu
  • Victor Grushevskiy
  • Myeong Hoon

... 38 total!

Subject Matter Experts

  • Richard Casey

... 4 total!