Subscribe to download
Stick & Throttle

Configurable Stick and Throttle bindings for your Space Engineers ships.


This script requires wolfe_br's SE-AnalogThrottlePlugin[github.com] plugin to deliver stick and throttle events to the game, and cannot function without it. To install the plugin, use the Plugin Loader mod, following its directions to set up launch options.


Your ship must have a single main cockpit, to use as a reference for the vehicle's orientation. If your ship only has one cockpit, the script will use it. Otherwise, use the terminal options to enable "main cockpit" on exactly one of them. Note that remote control blocks count as cockpits.

Once the plugin is installed and a main cockpit is selected, this script can be installed in a programmable block. It will control thrusters, wheels, gyros, and other features on the same grid as the programmable block only (and will not control anything on attached subgrids).

The programmable block must have the tag in its name. The script will try to add it automatically if it's not present, but if this fails, add it by hand. The plugin uses this tag to route controller inputs.

Bindings are stored in the programmable block's custom data. When installed, if there are no bindings present, the script will initialize itself with a default set of bindings. These bindings are appropriate for the Saitek X-56 HOTAS stick and throttle and the Logitech Warthog throttle (since these are the devices I have handy to test with). Bindings can be customized using the block's custom data.

The script must be recompiled in order for it to detect changes to the bindings or to the grid. Input states will be lost when the script is recompiled, so any ongoing inputs (throttle selections, reversers, and so on) will need to be reapplied by moving the associated control.


Bindings are described using the INI format.

• Each device must be described in its own section. The section name must match the name of the device reported by the AnalogThrottle plugin exactly.
  
• Each key under a section describes an axis or button on the device. The value of the key determines what controls the axis or button will be bound to. The key of the axis must match the name of the axis as reported by the plugin exactly.
  
• Each axis can also have an optional customization section, to control parameters such as deadzone, sensitivity, or reversing the axis. A customization section's name is the name of the device, a dot, and the name of the axis.

The following options can be used to customize the behaviour of an axis:



This script would not be possible without the help and inspiration of Digi, wolfe_br, Malware, Whiplash141, ChillCreeper, and (of course) Keen Software House.