and hits the game performance to have to constrain 5 actors in each layer just to create the illusion of a change layer behavior. I Know you have many request, thats the only one i think is holding m

i think it will. but not wrap. try constrain to X. i was working on my project where i had a actor colliding with another and stopping there. thats what i wanted. but when i constrained it yo Y...the

The stars are colliding with an invisible actor about 1/3 across the screen and triggering the next set of stars by changing an attribute StarSetTrigger (Integer), when the stars go off screen they re

anything. the spawn is being triggered by an attribute.

(Quote)

Or you can unlock an actor to access scene attribute such as camera origin (Image)

instead of interpolate, you could use a timer with change attribute.

I HATE having to scroll down my list of attributes looking for the one I know is there, knowing the name of it, but having to scroll through the non-sizeable little expression editor drown down box, h

The problem here is the collide is setup to make and attribute =1 which when 1 is equaled... the actor up top is triggered to spawn a block. then i have a timer on it to switch back the attribute to 0

change velocity" attribute.

instead of using accelerate to jump use a change attribute like so:

Im using attribute triggers to detect the "terrain" so he's not jumping in mid air. I'm also using the "Accelerate" function for the actual jump.

however, as far as not loading, that points to a bad rule somewhere. the preview in the creator is very forgiving and will work with a bad rule. adhoc does not, and when you see scenes that load forev

Correct you should be subtracting the attribute separate from the interpolate behavior that is using the attribute to define the row or column you are trying to reference.

http://www.jamie-cross.net/?portfolio=gamesalad-recipe-003-enemy-collisions-detecting-a-head-jump-vs-a-side-collision

i see... subtract the attribute.. ok will try now thanks

So I am back at this since I have free time to mess with it again. So I got all the files and rules showing up by manually changing the actor.xml files. I had to replace the attribute on all the imag

Attribute game.gameover is set to true

-- Change Attribute: distanceToMouse To: magnitude(game.Mouse.Position.X-self.Position.X,game.Mouse.Position.Y-self.Position.Y )

the editor could I? Or do I say something like constrain the x and y values of actor A and then again for B. Then in the expression editor would I use an exponent to the second power to the x and y