Hi,

Could you, please, make either a video of, or example ships and put on the workshop, using the minimal amount of everything needed to work? I'm struggling to make a "flying seat" small ship work on a planet, and I think it would explain better than a lot of text, if people could see the config of something already working.

Edit: I finally got it working. I might make a video, soon-ish™.

I would suggest you to change the following, so the script can be easier to use:

- Variable names: Why have GimbalZMinus, GimbalZPlus, GimbalYPlus, GimbalYMinus, GimbalXMinus, GimbalXPlus when you can have GimbalForward (GimbalW), GimbalBackwards (GimbalS), GimbalLeft (GimbalA), GimbalRight(GimbalD), GimbalUp (GimbalSPACE), GimbalDown (GimbalC). This way, people won't have to visit this page EVERY TIME they want to use the script on a new ship, or change a ship.

- Add support for dampening. Currently, a ship won't stay in place, with this script, so one has to have thrusters in every direction, instead of needing enough thrusters for every direction.

- Make a easy-to-follow guide, both in text format, and as a recording, to this page. Here, have an example:

1. Have Whip's Rotor Thruster Manager script installed (requires 1 programmable block and 1 timer)
2. Have Wico Gimbal Rotors script installed (requires another 1 programmable block and another 1 timer) [You could use the same timer for both, but is not recommended]
3. Have the timer used to activate the Wico Gimbal Rotors script have the actions (a) Timer -
Start, (b) Programmable Block - Run
4. Add [GIMBAL] to the name of the Timer used to run Wico Gimbal Rotors script
5. Add to the control block(s) (Remote Control, Control Station, Cockpit, etc.) the name Gimbal Control
6. Add to the rotor's name or custom data, or both, [GIMBAL]
7. Add to the rotor's custom data the angles the rotor has to take to move in each direction it can (X is left-right, Y is up-down, Z is forwards-backwards, Minus is for before the -, Plus is for after the -, so XMinus is left and ZPlus is backwards; I know, those variable names make no sense whatsoever!)
8. Compile the Wico Gimbal Rotors script.
9. Save the game, or make a backup, if you can; if something can go wrong, it's better to be safe, than sorry.

7.Example for a thruster in relation with the Reference:
7.a On top, thruster(s) facing forwards: