orienting an object towards a point in bullet

Started by
2 comments, last by nonoptimalrobot 10 years, 8 months ago
In my game I need enemies to turn towards the object they are chasing. So I tried to make a function to turn their rigid body towards the point their going to by applying a rotational impulse proportional to the dot product between the way they're facing and the direction they need to do to. Here is my code:

void lookAtPoint(btVector3 point, btRigidBody* body)
{
	btVector3 pos = body->getCenterOfMassPosition();

	btVector3 dir = (point - pos);
	dir.setY(0.0); //restrict to two dimentsions
	dir.normalize();

	btTransform t;

	body->getMotionState()->getWorldTransform(t);
	btVector3 forwards(t.getBasis()[2]);

	forwards.normalize();

	body->applyTorqueImpulse(btVector3(0.0f, forwards.dot(dir), 0.0f));
}
The problem is that the object seems to turn in the direction opposite to where it's supposed to even if I reverse the direction of the impulse. For example if the object is to their right they will turn left. Is their any problem with my approach or am I making a simple stupid mistake with my code?
Advertisement
Yes, there is a problem with what you are doing: The dot product won't do the job here.

If (x1,y1) is a unit vector and you want it to point towards another unit vector (x2,y2), you can do so by applying a rotation by an angle whose cosine is (x1*x2+y1*y2) and whose sine is (x1*y2-x2*y1). So you can compute the angle as asin(x1*y2-x2*y1). Since the function asin looks like the identity around the origin, you can probably get away with making the impulse be proportional to (x1*y2-x2*y1).

[Disclaimer: I'm not 100% sure I didn't make any mistakes in the formulas, and I don't have the time to check now.]

[EDIT: I changed the sign. But I'm still not 100% sure, so just try it both ways. ;)]

In my game I need enemies to turn towards the object they are chasing. So I tried to make a function to turn their rigid body towards the point their going to by applying a rotational impulse proportional to the dot product between the way they're facing and the direction they need to do to. Here is my code:


void lookAtPoint(btVector3 point, btRigidBody* body)
{
	btVector3 pos = body->getCenterOfMassPosition();

	btVector3 dir = (point - pos);
	dir.setY(0.0); //restrict to two dimentsions
	dir.normalize();

	btTransform t;

	body->getMotionState()->getWorldTransform(t);
	btVector3 forwards(t.getBasis()[2]);

	forwards.normalize();

	body->applyTorqueImpulse(btVector3(0.0f, forwards.dot(dir), 0.0f));
}
The problem is that the object seems to turn in the direction opposite to where it's supposed to even if I reverse the direction of the impulse. For example if the object is to their right they will turn left. Is their any problem with my approach or am I making a simple stupid mistake with my code?

The dot product is going to approach it's maximum value (1.0 in this case) as 'forward' and 'dir' approach the same direction. This means that your rotational speed increases as you orient towards the target. You could try,

body->applyTorqueImpulse(forwards.cross(dir))

although I am uncertain about the correct sign here.

-Josh

--www.physicaluncertainty.com
--linkedin
--irc.freenode.net#gdnet

Taking the dot product between your current look vector and your desired look vector (this is what you are doing) doesn't tell you which direction (left or right) you need to get them to match. To figure out which direction you need to turn and by how much use the cross product instead. If you have two unit length vectors u and v then:

omega = u cross v

where the direction of omega specified the axis of rotation and the magnitude of omega is equal to the sine of the angle between u an v. You seem to be restricting yourself to 2 dimensions here so it's actual a bit easier. Here is some pseudo code....



float GetTopDownTurnDirection(const vector3& a_vCurrentLook,
                              const vector3& a_vDesiredLook)
{
    vector3 vOmega  = vector3::Cross(a_vCurrentLook, a_vDesiredLook);

    return vOmega.y
}
    

This topic is closed to new replies.

Advertisement