Move To Behavior

specialist_3specialist_3 Member Posts: 121
edited November -1 in Working with GS (Mac)
Hi,

I refer to a couple of threads and also to the tutorial sections on Moving an actor to a Touched X,Y spot in the screen. Basically, global X,Y attributes are set to Device.Touches.Touch1.X or Y. And then the global attributes are set to the Move to behavior of the actor.

I tried another method where instead of having those extra global attributes and passing around values from one actor to another, I can directly enter Device.Touches.Touch1.X or Y into the Move To behavior or the actor. When I tested, they seem to yield same results...actor moves to area touched.

Is there a reason why the first method seems to be more popularly used than the second? Is there any drawback in directly entering the Touch1.X Y values into the move to behavior of the actor?

Also, regardless of what I choose, I noted that once the actor moves to the spot touched, it does not move to further touched locations anymore. Once it stops at the first location, thats it.
Meaning, if I i have,

Move to X = game.Touches.Touch 1.X (say 100)
Y = game.Touches.Touch 1.Y (say 100)
Speed = 100
Run to completion (doesn't seem to make a difference)

Once the actor reaches, 100,100 it stops moving. and after that if I touch any other area, it does not move.

Where am I going wrong?

Cheers!

Comments

  • specialist_3specialist_3 Member Posts: 121
    But if I used Accelerate To, it works but the actor never stops...rather "hovers" around the area last touched.
Sign In or Register to comment.