Dude this is Singapore architecture but overpowered X 300 is real shit bro

HOLY CRAP

DID THAT JUST GET TO SPACE IN 30 SEC!

this is really fun build. I tried it with medium cargo containers as well on small ship. it works.I just cant build well enough :)

It does work, I've tested it so far with medium cargos and the same mass. It did work, but I'm pretty sure it's not the most efficient way and I can reduce the necessary mass while increasing power.

Thank you for the insight. I've got a couple of ideas I want to try now.

You mentioned small ship... so cargo - rotor - rotor - cargo on a small ship would work as well? Any particular size cargo container or just large enough to hold the requisite mass?

Speaking of which, for a small grid ship, what would be the requisite shift mass?

Technically that should work, but I'm pretty sure the script wouldn't be able to differentiate between the drives and crap out. If you want more power, you could put more mass in the cargo container and increase this variable: int shiftmass = 15748; at line 951 in the code accordingly. So like add 10 tons and increase to 25748. For that to work you need to go for the cargo-rotor-rotor-cargo build and not the assembler-rotor-rotor-cargo one (unless you have inventory multiplier on).
You can also add a third rotor for more power, but that might be way too unstable.
I'm working on adapting the script to adjust the shiftmass automatically depending on how much you put in and what rotors you have (small ship), but for now you can do it manually.

You answered my question.

Though it does give me another one... would this drive work if it were multiple drives connected at each end?

The basic drive is: cargo - rotor - rotor - cargo

Would this work?
cargo - rotor - rotor - cargo
cargo - rotor - rotor - cargo
cargo - rotor - rotor - cargo

Where the cargo containers at each are connected to each other?

Perhaps you could actually put a third drive in the middle if you offset it a bit, so the cargo container would be between the rotors, cause rotors don't take up as much space.

I'm not sure if I understood what you mean, but you have to leave one block of space around the cargo container or it's gonna crash into everything, so two of these would need one block of empty space between them. You can fill that with small stuff like blast doors etc. though. I've linked an example ship, you can look at that to get an idea of how to place them.

How closely can I build the different axis of thrust together? Immediately adjacent / side by side or do I need to leave a block of space in-between?

I will try this out today :)

I updated the script, you can now also build these with only cargo containers, just slap all blocks on top of each other and add the iron, works like a charm. You have to make sure the cargo container is not conveyored though.

Mostly so you don't accidentally conveyor it and move other items inside or pull out the iron by accident, since it only has one conveyor port. Initially also because the inventory size is limited to around 16 tons of iron, but I updated the script so it only pulls out 16 tons anyways.
The reason 5 tons stay in the cargo container is because if it retracts too fast, it fucks up the timing. I tested it quite a bit and this configuration was the one I got the most power out of, but there might be a better configuration.
It's totally possible with just cargo containers, but the script won't recognize that atm.

Questions:
1. Why the assembler block?
2. Why 21k ignots?

Perhaps if build it like in the video the script might even recognize all drives. No idea what would happen then, but the rotor offset would probably fuck everything up.

The rotors can extend up to 60 cm, but at power=1 they only extend 30 cm for safety. overclocking the power makes them extend further which increases the power, but also makes it less safe. 1.2 should still be fairly safe, but I wouldn't crank it much higher.

I've seen a concept of a 6 axis mass shift drive on youtube, but it's probably smaller to just build 3 of these. Also it would be pretty hard to place it, since it would have to be exactly in the center of mass.

Couple of questions...

1. Is it possible to come up with a MSD & related drives that are entirely 6 direction as a single object?

2. I was looking at the script to control this particular engine. Overclocking the engine would be changing the double float to some number greater than 1, correct? I am assuming that 1 is 100 % so changing it to 1.2 would be 120%, correct?

Thank you this will certainly give me a tactical advantage

*need

I forgot to mention, they actually work both in two directions simultaneously, so a thruster pointing forwards will also work backwards. So basically you just 3 for a 6-axis drive.

No, I would recommend to just start with one in forwards direction. The script is very adaptable, so you can place them in whichever direction you want thrust and as many as you like. Just keep them in line with the center of mass.

do you need one of these in every direction?

The 25.5 Million kg is his ship. He already has 16 MN of thrust from the Ion thrusters on it. I don't know if they are reduced on the planet he's on. We already know those thrusters are insufficient to get him off the ground.

The planet does have a minor atmosphere but only up to about 1 km. Per the math, he only needs 75.5 MN to lift off from there. If each MSD had 40 MN, that would be 80 MN. He's unable to lift off with just those two we built.

But if they are closer to being roughly 4 large hydro (which is what my testing implies with no changes to the script as of last night), then another two should suffice to lift him off.

The reason we didn't choose to use a different clang engine is we wanted something very simple to build and implement. He's not entirely trustful of Clang Devices. In this regard, he's very traditional.

https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=1958911211
*link broke

Woah that's a massive ship you have there. Large hydro thrusters have 7.2 MN and this thing has roughly 40 MN, but I honestly didn't do that much testing on it. So for 25 million kg you would still need at least 7 of these to lift off. If you want something a little more powerful, a single one of [/url]these[/url] will be able to lift your ship and accelerate to max speed in ~5 seconds. I've just updated the script again btw a couple of hours ago and fixed a couple more bugs, so reloading it from the menu might make it more stable.

Observations:
1. They work rather well with other thrusters actively in play.
2. They definitely reduce space and power requirements.It does make me wonder how well they would work in 1.2 gravity on a ship with just Ion Thrusters.

The testing also tells me what to do on a server I play on to help a friend who has two MSD and still cannot lift off.

If you have any suggestions regarding the testing results, please let me know. I definitely want to keep playing with these and see what else I can learn and accomplish.

Test 2: Same ship, now 25.5 Million kg, 2x forward, 1x left, 1x right, 2x lift, 0.25 gravity

The ship clanged into the ground on takeoff. The landing gear was embedded in the ground. I was unable to take off without using ship hydrogen thrusters.

Per the writeup, 2x MSD ~ 12 large hydrogen thrusters. I would estimate their lift to be closer to 4 or 5 large hydrogen thrusters. The exact amount would require more testing

Once off the ground, I was able to stay aloft with just the MSD (which flies in the face of takeoff behavior since the gravity hadn't changed).

I also had terrible rolling (highly unresponsive to Q & E) despite centering all directions on the center of mass. Acceleration was exceptionally poor and only served to move me in reverse regardless of forward input. All drives were observed to be responding to inputs as expected.

21 tons is 21k kilograms, correct?

I performed two tests and noticed some interesting behavior:

Test 1: Ship is 7.7 million kg, 2x up, 2x forward, 0.25 gravity

I was able to lift off and fly forward without issue. Barest hint of torque, corrected with Q & E. Toward the end of the test flight, I lost all control of thrust with the MSD, could only speed up to maximum speed.

I did the following:
1. Programming block off/on
2. recompile
3. Edit script/check code

Did not correct situation. Turning on/off the ship's hydrogen thrusters made the MSD work again.

yep you got it, but you also have to place them about halfway between the bottom and top of the ship or it will pitch up or down.

Got it. Thank you. It appears the ship I am using on a server is a good candidate for this drive. I happen to have the space and requisite placements free of obstruction. I think it's going to be my weekend project =)

Would it be fair to say that if I put two drives for forward thrust that if I put them equal distance from center of mass on the horizontal plane, they'd not cause any yaw because of equal distance from the center line?

EX: COM is 0,0,0. E1 is -5,0,0 and E2 is 5,0,0

There would be no yawing or other torque applied, correct?

yes excactly, if you would for example only place one on the right wing in forwards direction your ship would yaw to the left. There's an experimental option in the script to counter that torque with gyros to be able to place them offcenter, but you have to set the gyro override manually.

In-line with center of mass... This means that in the direction of movement, a line drawn through the engine will pass through the center of mass as shown with that toggle on, correct?

Just wanting to make sure I am using the correct definition in my understanding.

Thanks!

Update: this drive is now handled by the clang drive manager script and better than ever before

A speed mod, I just used it illustrate how powerful it is. The video would have been kinda boring otherwise. I don't remember which one exactly, but there's lots of them out there.

how did you break the barrier of 104,33 m/s in the video?

@roman.bezsmertniy whats a merge drive

Can't use it for missiles cause can't print moving parts (

I eventually abandoned this in favor of merge drives. Finer torque control, more power, simpler maintenance, and most importantly much more power.

eh, just make a missile and then it crashed on porpuse!

Usually by crashing into something, but you can also toggle it off, turn around and toggle it back on :D

Heres the question.. How do you slow down

Also, will you continually improve it?

More saftey, more power, and more KLANG?

also, mb for making it behave more like a thruster, get help from someone. If you want, I could ask around (I have a steam friend who has made a very useful and complex script, and if that fails, I’m sure I could find someone)

Impressive! Now, to use this on a missile... MWAHAHAHAHA

Hm... maybe I should combine it with a grav drive?

Oh... Ok
But now I'm thinking of what would happen if you attached this drive to the rotating part of a ship with the Vector Thrust 2 Sctipt
Might test it out when I have the time

Probably not, I'm not really into coding that much.

Awesome! Any plans on making it behave like a normal thruster with inertial dampeners on?

@Tom foolery I already have prototype for a new clang drive using merge blocks, but it doesn't need the rotating arm and is a lot smaller Still needs much refinement though

still pretty good

I've tested it from ~100 tons to ~1.500 tons and the mass seemed to not influence the force, so yes, but it's "only" as powerful as 10 large hydro thrusters, so you might need to add more than one.