when i try to make a new layer and lock items to it , as seen on many videos. My actors always sit behind the background and so never show up on when i run the program.

WOW, I was running the game in the IOS simulator while recording with both Camtisia and Screen Capture tool at the same time for the video at the top, All on my Mac Air and the FPS was pretty small...

I'm now in the top ten in the gamecenter list (Image)

when the game starts the player can touch any of the actors to destroy them..the player will have to eventually destroy all the actors by touching them...when the first actor is destroyed..a timer sta

I'm trying to make an 8-bit style top view game, and getting the diagonal movement right is screwing me.

a draggable actor that is a box and I touch the top right corner, I could drag him from that corner without him just snapping to his center.

I think there are still a few more promo codes (at the top) that are still available if anyone wants them.

I know you don't want to pay but for only 99p we have an endless runner that gets harder and harder with a top score save system.

Hmm, the only one I would really make use of is the ability to hide layers, that would make editing levels a whole lot easier and being able to re-order attributes would be a fine thing to. Aside from

Best practice would be not to spawn them but rather to hide and then reveal them (e.g. with self.color.Alpha=0 or 1). That way you don't have to spawn and destroy them. You can control their visibil

These tutorials have inspired me to spend a few hours with Inkscape and also ink pad for iPad, top job as always m8.

You need to unlock the actor and go into scene/layers or you could simply make a game attribute real and then constrain that to the heros x position in your hero actor.

You could use code like jump through so the hero will only collide when he's on top of the actor but this requires coding in the platform actors or unlocking the hero...

If they had said "after reconsidering the investment in the lua engine, we decided to change it to pro only so that we can fund new features and get them out sooner" and/or offered s

In layer 11, there was a rule where I Change Attribute self.Position.X to 835.412

That means there is something on your eleventh layer that is breaking the code (see above post)

GameSalad also loads all the rules in reverse order (relative to layers). It loads the things on the lowest layers first, ending with the top layer. That's why when you move the layering around differ

What seems to have an effect however is when I change the Layer layout. Maybe I have too many layers in my scene? Is there a limit? I have 18 layers in my scene. If I move layers to the back or ne

cant you just destroy them when they collide? or do you need them to stay on the scene?

In short, each time a texture change is required we have to stop batching and tell the graphics hardware to draw what's ready now. The engine currently does very little batching because each image is