Unless (through an attribute) you trigger an actor on another layer to spawn - so a collision on a scrollable layer could spawn (via > attribute > spawner on the target layer) an actor o

The problem is that you're constraining the size of the bullets as well as the position of the player. You can remove this problem in two ways.

You can only spawn to the layer the spawning actor is on. What layer is the spawning actor on?

the layer under is scrollable and the layer on top is unscrollable and instead of it moving as if its on a scrollable layer it always comes as unscrollable... is anyone else having this same problem

you see...you can destroy the opponent, but you does not destroy yourself by enemy´s bullets...

The game performs well on a desktop supported platform, but right now, on mobile, aside from the 12 second load time for the actual game{menus load quick, due to minimal rules.} There is a strange &am

But another game that doesn't load for me is http://arcade.gamesalad.com/games/126387 which was featured on the top of GameSalad arcade...so I'd think it would work. Or this one either, http://arcade.

Let me name a couple off the top of my head.

. The page can move when I click, but then It won't stop and don't react on my mouse.

(Quote)

[Visible] = True" type rule on top of the mouse-inside and mouse-down rules for every button, and then finishing each instruction set by making the current menu object's Visible = False and

slef position x < 30 (this is your second x position where your second actor stop - 1. so your second scene position must be 29 or 30 not sure)

What kind of game is this ? If you are asking its easy just something fall from top and you try to hit and destroy them. You have magic power (yeah that black thing (Image)

I took out the 2 second delay (which was intended to allow time for everything to happen before destroying)

no movements are being called. If when at the top of the ladder you need to be sure the actor returns to a default idle standing position once off the ladder. Remember logic is a series of events so

@Icebox1910 create a smaller actor (with alpha 0 and circle collision type) and use that actor as collision detector instead (so your other actor will spawn the hidden collision actor on top of itself

Great that you are so on top of this @adent42 ... responding very quickly to any issues with the platform. Nice!

Maybe something like a isolate a layer from all scene and camera movement

So I have an app i'm making that has a map on it, you can scroll on it and zoom in and out. The menu button stays with the screen when scrolling. But when you zoom in, the menu button enlarges and sli

hud actors, even though it appears they are moving down the scene, code wise they are not. so an actor set on say an iPad layout in horizontal will only see a range on the X axis of 0-1024 pixels peri