MechJeb Compatibility

[Starstrider42]

MechJeb is the most popular autopilot mod in KSP right now, but it has serious conflicts with RemoteTech. A more detailed discussion has been done at MuMech/MechJeb2#382.

As I understand it, the problem is that MechJeb's and RemoteTech's input locks override each other, but they are used for different things -- on the MechJeb side, for keeping the human from overriding the autopilot; on the RemoteTech side, for simulating communications blackouts.

[Falkvinge]

(copied comment from MJ2 thread to bump)

Allow me to also add my interest in this. Since MechJeb is running locally on the vessel, there should reasonably be no RemoteTech (RT) signal delay from MechJeb to the vessel controls, BUT there should be an RT signal delay from the control center to the vessel in order to execute MechJeb commands or set MechJeb states (such as "land somewhere", "vector-surface-up", "begin docking", et cetera). Is there any hope of this happening?

Today, there is no RT signal delay when setting new MechJeb states, and no RT signal delay for MechJeb execution, which effectively eliminates the difficulty of a scenario like landing remotely with signal delay. One of those signal paths needs a delay, and the logical place to have the delay would be on the set-state command as the execution of MechJeb code happens at the remote location on the vessel itself.

[leftler]

Something I have been playing with, https://github.com/leftler/RemoteTechMechJebBridge Basicly I override MechJeb's Drive method and make it a NOOP I then register the pilot and have it call base.Drive(s)

I doubt I will ever release this code as a public release mod so feel free to take the idea and run.

[LupusTheCanine]

I would like to see compatibility with smart parts as they provide quite a few neat triggers like fuel level, altitude, engine flame out, time... and are quite useful for atmospheric landings.