some credits for the design would be appreciated

script itself is really heavy on performance, and useless on servers that use BpLimiter. any tips to make it more performance friendly?

This is why the script plays around with rotor speeds - to keep them in sync. If one of the rotors is at, say, 90 degrees, and another is at 107 degrees, that could throw off the timing for switching the merge blocks on and off (or at the very least make it more difficult to control), so the script keeps keeps track of the angle of the rotors and speeds them up or slows them down to get them back in sync with each other.

@MagboneD So to start with, the principle of operation of a merge-block drive is to take advantage of the fact that when two merge blocks get close together, the game "pulls" them together, almost like magnets, and when it does this, it accelerates the whole grid, in a predictable direction.

The script takes advantage of this by carefully turning on certain merge blocks when they are lined up to accelerate the ship in the direction the player or autopilot is inputting. If you just left all of the merge blocks running all the time, the ship would veer around all over the place, so the timing needs to be controlled.

(cont.)

I love this idea, but I'm having trouble reading the code (haven't coded anything in awhile). What is the principle of operation here? It seems that the code is systematically turning off and on the merge blocks and cycling the rotor speeds, but I can't figure out why

Fixed the script using the comments below and had fun flying this little prototype around! I tried deconstructing the ship and reassembling it inside a larger capital ship near its center of mass but keep getting flung into random directions. Tried tweaking the values in the script but to no avail. Haha, that's okay, Clang. Keep your secrets.

Turns out it was a simple script fix. IMyMotorStator.TargetVelocity has been replaced by TargetVelocityRad and TargetVelocityRPM.
Simply replace every instance of rotor.TargetVelocity with rotor.TargetVelocityRad

it doesnt look like the prototype itself is broken, using the x y z merge blocks do cause the ship to move

I don't know if you are still around, but it appears that an api change or something broke the script

Clang failing to work is a common bug introduced by KEEEEN! in the latest updates.

I've heard it can be solved by the ceremonial sacrifice of large ships to Clang.

If it's not working, will you fix it?

The big physics update might have broken it. I'm not sure.

I can't get it to work, the script just tell No TargetVelocity for rotor.
Can you help me to get it to work?

This is just.... insane. You won Space Engineers invention of the year.

This is actually the best thing I have ever seen in space engineers. Now I just have to wait for Hesterry to give us a tutorial on his AXE capital ship killer and then I will become god.

Yaaass!!!

Can we also get a bit more documentation? I tried making my own small ship version, but it's not stable.

Some ideas:
* Make a small ship version.
* Modify the RPM of the gears for finer control.
* Pair this with your gravity drives for fine control.\

Freaking awesome work.

Not only is this awesome, it's apparently extremely durable too. Still worked just fine after one half spontaneously combusted.

THIS MAN IS A GENIUS. GIVE HIM THE CLANG-BELL PRIZE!
Anyway, @Bridge is right, you kinda doomed us a 'little'...

You imbecile! You've doomed us all!