@contrasthall is right. You can us the magnitude function. You will have to constrain both the actors' positions to global real attributes, or juat access their positions through unlocked prototypes.

then actor (B) destroy

For example. I have a background. When ever I touch it it should make me lose. But I have an actor on top of the background. I have to press that actor as many times as i can to win, but when ever I c

(Quote)

Maneuver your plane by tilting your phone left and right and destroy the Fuzbats as they come at you from every direction while trying to collect coins and power ups. You then have the option for upgr

Congrats man! - Will send a post out for you on "List your top iPhone Game" later.. I'll make sure all of our 800 likes see this (Image)

I tried changing the layer order @socks and for me it was the same with external attributes vs scene link. Also when exporting to device the lag goes away that does show on GS preview.

I don't think It's a question of layer because i good placed them in the editor and when i click to test the application, the background is in the correct position, and i can only see the half of one

More often than not when a user has a problem positioning actors in one of our templates its because they placed them on the wrong layer.

Scene linking has a noticeable lag when compared to simply changing the layer order in my example. Scene linking might be better than referencing a global attribute, but ordering the layers seems to h

2.- Create actor, can move just to 960 and more w/o problems, you have to move +100 size scene to be destroyed.

Hey! Your site looks great! It looks professional! I checked it out on my iPhone, and it looks great! The only thing I would change is that I would make the links at the top a bigger than they are now

What I want to achieve is that my actors get numbered between 1 and 18 with none of the numbers getting used twice, so the players are able to start with 1 and destroy the actors by pressing them in n

Unfortunately even if the numbers are correct and it is genuinely low, GS are going to get some stick, we need real time records - iAD style or we're always going to think someone is skimming the top

I need to hire a professional GameSalad developer that is on par with well known top GS developer, T-shirt Booth. As we all know, he is busy running his new, well, virtual T-shirt booth.

destroy either tiger1,2,3,4,5 or 6 and add +1 to game.score

got it. 'Spawn actor [actor 3] in front of layer' should be on top and [actor 1] on the bottom in the second example - correct?

@ddagul Beautiful illustrations; top notch! :-)

When actor is > 1500 is destroyed! (project resized from 480 with gamesx style)

That works fine, but on ipad mode, when the camera is near scene size width - (screen size/2) the camera is destroyed.