Space Engineers

Space Engineers

评价数不足
Battlemech - "Saber" Class
   
奖励
收藏
已收藏
取消收藏
Type: Blueprint
文件大小
发表于
857.181 KB
2018 年 12 月 15 日 下午 8:06
1 项改动说明 ( 查看 )

订阅以下载
Battlemech - "Saber" Class

描述
It's taken multiple attempts and many hours of trial and error, but i've finally managed to build it: A fully-functional mech in space engineers, and a bipedal one at that.

This is the Saber-class BattleMech: A bipedal walker capable of traversing flat terrain in 1G environments, with some pilot assistance. It was dubbed "Saber" as a derivative of "sabertooth", based on it's fang-like gatling turret, and partly orange colour.

The Saber features a dual-axis gatling turret with two guns, and two single-axis rocket turrets with two reloadable launchers each. In survival mode, the gatling turrets must be manually reloaded, but the rocket launchers are connected to an interior container which is accessible from the cockpit. The rocket turrets are designed as an anti-vehicle weapon, with enemy mechs and fixed-trajectory overhead targets (such as drones) in mind. The gatling turret is also meant for ground-targets, and was designed with an anti-personnel role in mind, although the latter isn't very practical since both turrets are torque-controlled.

The Saber has an average walking speed of about 2m/s, although this varies somewhat. This means it is very slow, although I hope to improve this in the next few weeks.

While this mech is "stable" so-to-speak, the Saber can fall over fairly easily without constant pilot attention, especially if it's walking up any inclined surface.

Increase/decrease pitch override options have been incorporated onto the toolbar to assist with walking up inclines. I recommend you leave the value between 1-2RPM while walking on very flat terrain. It is normal for the mech to lean forward while walking, as this ensures it doesn't fall on its backside. Occasional corrections may be necessary to prevent the mech from faceplanting. A good way to tell when to correct is to see if the feet are leaning forward at the end of each step.

[HOW TO USE]

There are currently two full toolbars to pilot the Saber with:

Toolbar 1: Weapons-related controls
Toolbar 2: General controls.

Toolbar 1 features:

1: Rocket Turret - reverse
2: Rocket Turret - On/off toggle (starts/stops rotation)
3: Select rocket launcher weapons
4: Select gatling weapons
5: Gatling Turret X (axis) - Reverse
6: Gatling Turret X - Toggle On/Off (starts/stops rotation)
7: Gatling Turret Y (axis) - Reverse
8: Gatling Turret Y - Toggle On/Off (starts/stops rotation)
9: Gatling Camera - View

There are also rocket launcher cameras, but by default they can only be accessed through the terminal. There isn't room for them on toolbar one, and I hope to fix this problem in the next few weeks.

Toolbar 2 features:

1: Initiate cycle - Trigger Now (use this to start the walk cycle)
2: Right Timer Adv 1 - Stop (use this to stop the walk cycle)
3: Script Loop - Trigger Now (starts the precise timers script, ensuring proper walk cycle functionality. Only needs to be triggered once, as long as the mech is powered.)
4: Forward Gyro - Toggle Override
5: Forward Gyro - Increase Pitch Override
6: Forward Gyro - Decrease Pitch Override
7: Body Axis - Toggle Rotor Lock (Toggle this off to put the mech body on a swivel between -45 and 45 degrees.)
8: Empty
9: Empty

Note: The swivel feature can interfere with mech stability, causing it to fall over, usually on its side. Because of this, I recommend centering the body rotor at roughly 0 degrees and keeping the lock on, when outside of combat.

Credits: The "Precise Timers Script" was made by SioxerNikita. It's an extremely useful script for timer setups where the vanilla delays (which are set in seconds) prove to be impractical or inadequate. This script has no doubt played a significant role in the development of functional mechs on the workshop.

One final note: Since this build uses both pistons and rotors, it is a bit buggy. I have tested it numerous times (with block destruction both off and on) and haven't noticed anything dangerous, but be aware there is a possibility something could spontaneously break or explode.

I hope to add more description to this submission within the next few weeks.