Added rover set up info and general checklist to the description.

It is highly recommended to be ran with APck. Some implementations probably still work stand-alone (iirc merge-mag drive and maybe VTOL), but I haven't tested that lately.
APck would configure this script automatically so you don't need any commands.

is their a list of commands for this script anywhere or does it have to be ran with apck?

1.0.225
Rover provider:
- steering fixes
- back wheels steering inversion (behind grid bounding box center as CoM is not accessible from a script)
- wheels that have Steering property off are now ignored

Thank you!

Sure. If you don't issue any specific tasks to AutoPillock, it behaves as a normal grid with a dampening, and also you get a benefit of using "hybrid-thrust" - you can have fixed normal thrusters and "VTOL" thrusters simultaneously.

can i control autopilock with a cockpit then also i have tried other scripts like "Vector Thrust OS" and Thrust provider is significantly more responsive than it

If you use it through AutoPillock, it dampens by default.

hello is there any way to enable some kind of dampening? for cockpit controlled mode

Thanks. What I'm doing is testing the VTOL script on a sort of hover bike to see how it works before doing the drone. The drone will be part of a drop pod as an area denial system. Upon landing the pod will grind off the protective cover and the drone would launch and patrol a predifined area around the pod. The drone would returnnto reload, refuel and/or recharge.

Ah, I see, you want just player controlled grid? I assumed you want full capability with AutoPillock script since you originally mentioned AI VTOL drones. The video shows process of making fully functional drone which requires two scripts. I recommend doing that - although this script can be used as stand-alone for manual flight, I can't remember exactly how to make it run on its' own. You can try this:
- make sure cockpit is in the script blocks group and that required blocks are named correctly
- run PB with argument "command:set-mode:Vtol" (or add the same to PB CustomData)

Sorry about all this. I am just finding this a little bit confusing.

The video shows setting up a drone and the instructions above don't seem to be clear about setting up a vtol craft that is piloted by the player other than mentioning a control seat/cockpit. Do I need the other script whether the craft is a drone or not?

You don't put anything inside the cockpit Custom Data. So what you are doing wrong is essentially trying to make things work without reading the instructions.

Saddle cockpit

And what is "the saddle"?

Command you mentioned is incorrect, maybe some other issues. You said "PB" and refer to it in singular, but you need two PBs.
Did you watch the set up process video above? It shows step by step how to make simple VTOL drone, just follow it.

I installed this script on a test vehicle that includes saddle, gyro, PB, remote and four thrusters each on there own rotor but I seem to be doing something wrong. I put all of those blocks into a group named VTOL Group. The pb just has a "run count" and "processed in". I put the command:thrust:delegation:Vtol in the custom data of the saddle but I can't seem to get it to work. Any ideas what I am doing wrong

Thank for repsonding. I think I can still work with that.

VTOL implementation here works only with rotors, and one axis per VTOL unit (no rotor on top of rotor stuff). I don't think I would add hinge support in the near future as hinges just limit the range compared to rotors.

I am planning to make a quad A.I. drone that only uses 4 atmos on rotor+hinge assemblies. Will this script work with that setup?

Thanks! I'm really glad you sorted it out! I'll try to do more detailed video guides later. I just have a lot of planned work so it's just a matter of priority: I want to cover everything in a compact way so people at least have some chance of figuring it out, instead of investing a lot of time on covering specific feature and completely bypassing everything else.

hey thanks for the quick reply,
your script is running fine after three hours of trying around.
I am aware that it is a special kind of vtol script.
To my knowledge the only one that has an autopilot with remote control functionality.
But you have several scripts working together like in a construction kit and you might want to handle/explain them individually.
My tip: a video with spoken explanations is always better than text subtitles !
Your scripts are exceptionally good but most wouldn't use them because the setup seems too complicated (it isn't once you know how to do it,
but your video was a bit too fast at the important points and too long overall split it up better on Vtol setup commands etc.. and
automation autopilot remote control setup
so your skripts can get to page one were they should be.
greetings

Maybe if you are new to rotor-bound thruster design you'd better start with more mainstream scripts that are well-known, like Vector Thrust or something. There are tons of guides and videos. This script main advantage is that it can be non-human controlled.

What part of the video do you have troubles with? Any particular question?
I'm sorry but I'm very short on time at the moment. Later I may consider making a more verbose video on how to build a more usable VTOL ship. I tried to keep it as simple as possible and honestly just don't know how to explain it better. I'm writing walls of texts and making guide videos for the 3rd day non stop at the moment so hearing it's not enough detailed is just a bit tough :D

I don't really know anything about programming but I'm looking for a script to control my rotor and hinge bound ship thruster's and to be honest this one looks like it might fit but the setup explanation is a bit incomprehensible and/or not detailed enough for me.
Maybe you could revise your video a bit and also explain a bit what is important for which application?
If your script really does what you say it should be on the first page with 5 stars.
greetings