Subscribe to download
[v1.5.4] MECS: Motor Extensible Control Sequencer

MECS, my latest creation! I made this software from the ground up so that I could sequence things without the need of timers, making it a very compact and safe option for walkers, and a very powerful tool for automating factories.

v1.5.4
Fixed issue with commands not being sent if parts happen to be in correct positions. Ensures parts don't skip and then get stuck because they happened to be passing through the complete range.

v1.5.2
MECS now works in degrees instead of radians. This should make editing the customdata slightly easier to deal with. The system will perform the conversion to degrees on old sequences without breaking them.

You can now record and set the torque of a rotor. If rotor torque isn't present in the customdata it will add it in. However, if you have a really old sequence you might need to reload the script a second time for changes to take effect.

Unlocked setting on servos now works like you would expect. Rotors with this tag in their customData will now rotate the shortest distance every time, without having a min and max angle. This was a bit fiddly to get right but it works.
Please note that in unlocked mode rotors have to set the opposite angles to +-180 to avoid slider collisions.

I also made an internal change to the keybinds system. The system will now filter out keys that have no sequence applied to them. This makes it more compatible with itself and other systems as well. For example, a design with just w/s controls only takes the w/s keys into account.

What it does:
It stores a list of positions/states, and uses that information to send commands to all the the different parts to achieve that state.

Basically, in a robot arm, it will try to get all the rotors and pistons in the correct position and advance when they reach it. For doors it will wait until they are completely open or closed (although there is a neat caveat with doors). Landing gear it will wait for it to lock. Or not, depending on how you record it's state.

You can train this behavior just by toggling the blocks yourself and then telling the program to read the state.

In addition, you can now tell the script to read controls from any ship controller, allowing you to bind sequences to key presses.

Guide:
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1420398166

Known issues:
0) If you try to run an argument that takes a name and enter a space but not anything after it it will crash.

1) On rare occasion the game will crash when the program is trying to read from a projector. This mainly has occured to me when it is running nonstop and I am alt-tabbing in and out of the game. Perhaps it has to do with me cycling the projector's power to force it to update too quickly? I wouldn't mind if someone presented a better solution.
EDIT: As of 1.2.2, this problem should be resolved. Whiplash let me know of a more effective solution, which was pretty cool of them. Please let me know if this bug rears it's head again.

2) Since v1.3.9, there seems to be a scenario where the script will not update properly after updating keybinds, thus, not actually reacting to those key presses until you recompile. I actually can't remember if I fixed this one or not.

Currently scheming:
0) Overhaul the guide.
1) Sequence optimiser. (To reduce size and impact of a sequence by removing unnecessary information.) (v?.?.?)
2) MECS 2 at some point???

Footnote:

I created this with the intention of making it easier for people to make things like mechs and factories without having to worry too much about code. I hope this serves as a useful tool in your arsenal, and enables more amazing creations!