Hey Gang, The project I'm working on uses a mouse cursor's position to determine the direction to fire a bullet. Think FPS controls in a 2D game. Here's the problem. I want my projectiles to rotate to face the direction they are being shot in. I'm doing this by getting the Dot Product between the missle's direction and the missle's direction with no rotation. I've already realized that radians do not account for rotation over 180 degrees, but I was able to get passed that by checking the direction of the missle, and flipping it if needed. That all seems to work fine, except when the angle of the missle approaches 0 and 180 degrees. It seems to have a sort of 'dead-zone' where it stops incrementing the angle between the vectors. Here are the macro functions I'm using to convert between radians and degrees (incase the problem is there):

#define DEG2RAD(x) (x * (D3DX_PI / 180.0f)) // Converts degrees to radians
#define RAD2DEG(x) (x * (180.0f / D3DX_PI)) // Converts radians to degrees

Has anyone run into this, or have a possible solution for me? Thanks again all! Matt Hughson

Whats wrong with 2pi radians? that equals 360 degrees. Radians are not capped.

The dot product of orthogonal, or parallel vectors, will be 0. You must watch out for this.

Quote:Original post by davidx9
The dot product of orthogonal, or parallel vectors, will be 0. You must watch out for this.

That's not the problem. Its not that it suddenly jumps back to a rotation of 0 when the vectors are parallel. Its that for about 20 degrees surrounding straight up and straight down the angle stops getting larger or smaller. It just seems to lock.

Matt Hughson

The Dot Product is not your angle - it's the cosine of your angle. That's why it only handles 180 degrees before wrapping. If you take the arcosine and take sidedness into account you can get the angle. If that's working, then look at your rotation code.

Hope that helps.

Tom

Quote:Original post by Axiverse
There is another way where you have a castian (?) cordinate ( x, y, z ) and you can simply convert that into sphereical cordinates and maybe make a quaternion from that.

cartesian coordinate

Quote:Original post by ParadigmShift
The Dot Product is not your angle - it's the cosine of your angle. That's why it only handles 180 degrees before wrapping. If you take the arcosine and take sidedness into account you can get the angle. If that's working, then look at your rotation code.

Hope that helps.

Tom

Awesome dude! Thanks for the help dude. I'll give that a try in the morning.

Matt Hughson