It sounds like "Interpolate" is more of what I had in mind, but I wouldn't mind learning how I would use the "constrain" as well... Could you possibly go into a mor

Constrain doesn't have a speed setting. I think you are using the 'move to' behaviour and not the 'constrain attribute'. With constrain attribute it will appear instantly wherever you click. If you wa

constrain the x and y to touch1x and touch1y

Change Attribute Self.Size.Width to Self.Size.Width*2

I'm pretty sure I saw a constrain/move block demo in the templates if you search.

make an attribute (i.e. self.startX) or something and in the rule with interpolate add (before the interpolate) change attribute self.startX to self.position.X. Then interpolate self.position.X to sel

(move right, move left) that set global boolean attributes (and then unset them). The non-visible camera controlling actor listens to the two global attributes and moves 1024 pixels to the right or l

as i said before.. constrain self.rotation, no need to use rotate to angle.

Would this be a Constrain Attribute, or a Rotate To Angle?

How do I make the actors collide realistically right now there is a gap between were they collide and the actually image and also on a triangle it just collides on the outside of the triangle it does…

change attribute self.touchx = mouse.x

Also an issue I ran into while using ORBZ method is that it uses constrain attribute. This means that I can not move my crosshair. This is a fault in using this method that I am trying to find a work

Think you just want to constrain actor's x,y to touch1 x,y (use expression--touch is in Devices)

I'm assuming the only way for one actor to set an attribute for another is to communicate through global attributes. But I just want to make sure I haven't missed some way for me to have one actor tel

I thought of using constrain attribute to constrain the x position of the camera controlling actor to a global attribute I set when i press previous or next, however, that doesn't get me my scrolling

try having the actor you control as the smaller collision actor and constrain the image actor to it's location, rather than the other way round. if you constrain the collision actor to the image actor

Also, if you constrain an actor to specific xy coordinates that will overrride any bouncy physics you might be expecting.

How did you handle the curves and collisions?

There is a demo for hit area or zone. Basically you have a second actor that follows yourmain actor the second actor is the hit actor. Your main actor needs to change an attribute x and y position eve

Constrain actor B's rotation to always point towards A