Space Engineers

Space Engineers

56 ratings
Helios MSD-2-21 Mass Shifting Drive (superseeded)
   
Award
Favorite
Favorited
Unfavorite
Type: Blueprint
File Size
Posted
Updated
618.665 KB
25 Nov, 2019 @ 6:19pm
11 Jan, 2020 @ 8:53am
10 Change Notes ( view )

Subscribe to download
Helios MSD-2-21 Mass Shifting Drive (superseeded)

In 1 collection by Major Jon
Helios Defence Systems (Plug&Play Guns/Turrets/Clang Drives etc.)
33 items
Description
[Vanilla|Survival Ready|Subgrids]

Superseded by the MSD-35 Mass Shift Drive. It's much more compact and tileable. This still works and is still fully supported by the script.

A simple and ridiculously overpowered "thruster" that works everywhere and for free.

The MSD-2-21 Mass Shifting Drive is a type of clang drive utilizing two exploits, the instant rotor offset and the instant moving of items using programmable blocks. It pushes the ship off of the cargo container containing 21 tons of iron ingots, then moves them into the ship and pulls the now light cargo container back in. It repeats this process 30 times per second. This will accelerate the ship pretty fast and without cost. It works in gravity fields and can easily get you off any planet.
It is about as powerful as 8 large hydrogen thrusters, but much smaller and lighter.

You need the Clang Drive Manager Script installed on a prog block on your ship. The script will detect and operate the drive automatically. For more info visit the workshop page of the script. This drive works in two direction simultaneously, so a forwards facing one can also provide thrust in the backwards direction etc. You can place these in all directions you want, the script will recognize them automatically and address them properly depending on the orientation with wasd as input.

You want to build this in survival?
Easy, just build a basic assembler, stack two advanced rotors on top and put a cargo container on top of that. Then, fill the cargo container with excactly 21 tons of iron ingots. Nametagging anything is not required.
You can also replace the assembler with a cargo container, but have to make sure it is not conveyored.

Example ship here.


Some stats:
-Blocks: 6
-PCU: 252
-Mass: 26.7 t (including shift mass)
-Force: ~60 MN (can be overclocked to around 100MN)


How to use:
-Place it on your ship (see screenshots)
-Make sure it is in line with the center of mass (else it will exert torque on your ship)
-Install the Clang Drive Manager Script on a prog block on your ship
63 Comments
The_rebored_octo 9 Oct, 2021 @ 7:51am 
Dude this is Singapore architecture but overpowered X 300 is real shit bro
MrFox 28 Sep, 2021 @ 6:45pm 
HOLY CRAP
Unit-287 30 Aug, 2021 @ 5:17pm 
DID THAT JUST GET TO SPACE IN 30 SEC!
Judge Kronos 26 Jan, 2020 @ 2:26pm 
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 :)
Major Jon  [author] 24 Jan, 2020 @ 2:26pm 
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.
Darth Mord 24 Jan, 2020 @ 2:15pm 
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?
Major Jon  [author] 24 Jan, 2020 @ 2:00pm 
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.
Darth Mord 24 Jan, 2020 @ 1:40pm 
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?
Major Jon  [author] 24 Jan, 2020 @ 1:38pm 
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.
Major Jon  [author] 24 Jan, 2020 @ 1:37pm 
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.