2d trajectory planning of a spaceship with physics.
Posted
by egarcia
on Stack Overflow
See other posts from Stack Overflow
or by egarcia
Published on 2010-04-01T13:52:11Z
Indexed on
2010/04/01
14:33 UTC
Read the original article
Hit count: 710
I'm implementing a 2D game with ships in space.
In order to do it, I'm using LÖVE, which wraps Box2D with Lua. But I believe that my question can be answered by anyone with a greater understanding of physics than myself - so pseudo code is accepted as a response.
My problem is that I don't know how to move my spaceships properly on a 2D physics-enabled world. More concretely:
A ship of mass m
is located at an initial position {x, y}
. It has an initial velocity vector of {vx, vy}
(can be {0,0}
).
The objective is a point in {xo,yo}
. The ship has to reach the objective having a velocity of {vxo, vyo}
(or near it), following the shortest trajectory.
There's a function called update(dt)
that is called frequently (i.e. 30 times per second). On this function, the ship can modify its position and trajectory, by applying "impulses" to itself. The magnitude of the impulses is binary: you can either apply it in a given direction, or not to apply it at all). In code, it looks like this:
def Ship:update(dt)
m = self:getMass()
x,y = self:getPosition()
vx,vy = self.getLinearVelocity()
xo,yo = self:getTargetPosition()
vxo,vyo = self:getTargetVelocity()
thrust = self:getThrust()
if(???)
angle = ???
self:applyImpulse(math.sin(angle)*thrust, math.cos(angle)*thrust))
end
end
The first ???
is there to indicate that in some occasions (I guess) it would be better to "not to impulse" and leave the ship "drift". The second ???
part consists on how to calculate the impulse angle on a given dt.
We are in space, so we can ignore things like air friction.
Although it would be very nice, I'm not looking for someone to code this for me; I put the code there so my problem is clearly understood.
What I need is an strategy - a way of attacking this. I know some basic physics, but I'm no expert. For example, does this problem have a name? That sort of thing.
Thanks a lot.
© Stack Overflow or respective owner