Sax's Contraptions.

[Sax]

I use 2 vector thrusters, one in front if a positive thrust and one at the back with negative thrust. You need a beacon sensor outputting world_xyz and a GPS that is close the negative vector thruster. It's a very simple expression I use,

N@Turret/missile
I@GPSX GPSY GPSZ X Y Z ZInput
O@TX TY TZ
TX = (GPSX - X)
TY = (GPSY - Y)
TZ = (GPSZ - Z)+ZInput

I think you will get the rest. But the ZInput is to add height where it's aiming. Oh right I forgot, the mul input on the vector thruster does not go anything in the expression make a button or something. And the TX TY TZ is for the vector thrusters XYZ inputs.

[moogle_man]

Thanks man, that really helps, now I can use this technique in loads of things.

[Sax]

No problem, the plane in the video even uses this.

[Sax]

And if you want/can, you can join my server. And we can have some fun .

[screama]

I just tryed to adjust the vectors on my turret (thrust/weight) and it seems to work much more accurate

But: Why is it necessary to put the GPS near the negative thruster? Wouldn't it be more accurate it the GPS is exactly between the 2 thrusters?

[Sax]

I don't know, for me it seems to work the best if it's near the negative thruster.

[herbert spatula]

I've tried this but it just seems to spin around in circles when it finds a target. I've been told to use a vector thruster turret to build a mouse-tracking turret, as I can never seem to get aiming along the Z axis right. Any suggestions?