[heliumdream]

Originally Posted by Emp` for velocitybyaim, think of it as a 2d triangle for now, and that there is something you are looking at that is so far away (in this case it is iarg1 far away) from your origin, it subtracts the "thing"s origin, giving you the vector between you and the point (with the head of the vector at the "thing"). now pretend that you are floating in space looking at this thing, if you set the returned vector on yourself, you would be propelled towards the "thing". now just think of it as 3D.

Alrighty! I read that more than twenty times, and I still don't completely understand what your trying to tell me. Can you use paint, or photoshop, and make a dumb picture explaining that statement? Draw a triangle, and use the text tool to do some labeling. Please? I've got the feeling you know what you're trying to say although it's hard to put into words with out a diagram.

Thanks again, :-D
-heliumdream

ALL HAIL EMP!!!

[Emp`]

on a 2d scale...
[img]http://img148.**************/img148/2588/originvelocityexampleyo3.jpg[/img]

[heliumdream]

I get it now! I understood that all along! I'm still just plain missing a piece o mai pie I guess. I may just try and hardcode the vectors, instead of get the vectors from velocity by aim. This would enforce consistancy. Thats really all I want, consistancy in the way my hero is firing. I will do a diagram to 'splain.

As you can see from the pic, when you shoot east the front and back missiles get skewed, they get dramatically closer to you. The only reason I give a shit about velocity is because I am trying to control these four shots with greater precision and control.

[yang]

o.O emp` ur picture graph got pwn3d lol.

[heliumdream]

LOL