Time Based Movement?

#1 Yeah you could get the vector from point A to point B and divide components by the time you want it to take to get there, then set the linear velocities accordingly, and stop it when you arrive at point B. Real easy. :)

#2 ... just make sure you've got damping set to zero so you don't get any deceleration.

Something along these lines...

%startPos = "0 0";  // Start Position,
%endPos = "30 20";  // End Position.
%speed = 5;  // World-units / sec.

// Calculate linear velocity over time.
%velocity = vectorScale2D( vectorSub2D(%endPos , %startPos ), 1 / %speed );

// Set Linear Velocity.
%obj.setLinearVelocity( %velocity );

- Melv.

#3 Great, that was what I was looking for. I'll give that a try and see how it works out. Thanks!

#4 I use a slightly more adaptive method that's a bit more ugly, but it WILL get the object to point X/Y, and better, it'll handle any random impulses you might throw at the object along the way... (That's how the boss in Cloudburst returns to his waypoints even when you knock him back.)

function fxAnimatedSprite2D::moveto (%obj, %goal, %accel) {
  %dist = vectorlength2D (vectorsub2d (%obj.getposition(), %goal)) ;
  if (%dist > 30) {
    %turnangle = getangle2d (%obj.getposition(), %goal) ;
    %obj.setlinearvelocitypolar (%turnangle, %accel) ;
    if (iseventpending (%obj.movetosched))
      cancel (%obj.movetosched) ;
    %obj.movetosched = %obj.schedule (150, moveto, %goal, %accel) ;
  } else {
    %obj.setdamping (20) ;
  }
}

You invoke it as such:

object.moveto ("300 300", 100) ;

Where first argument is position in world units, and the second is driving force.

Note that you could make this a bit smarter by taking the linear velocity and then scaling it against the distance check, so there's no possible chance of bounce-back. I just used "30" because it fits my needs. Also, you need to make sure damping is set to something low that will let the object move. I use a damping of 20 at the end to make the object skid to a halt at just the right distance. If you don't, the object will jerk towards its goal, since a high damping doesn't let it get very far per moveto iteration.

Man, I sure hope schedules really don't take that much CPU, my script is absolutely brimming with 'em. :)

PS: I re-typed that function from my code, as what I had was a lot more specific to my game, so it might contain errors.