Incompatible with Mechjeb 2.15

[JonnyOThan]

32392 [EXC 00:06:55.499] MissingFieldException: Field 'MuMech.MechJebCore.target' not found.
32393     SCANmechjeb.SCANmechjeb+<WaitForReady>d__13.MoveNext () (at <b67b1c892a3b4b18a985a5a0d486e6e3>:0)
32394     UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at <12e76cd50cc64cf19e759e981cb725af>:0)
32395     UnityEngine.DebugLogHandler:LogException(Exception, Object)
32396     ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object)
32397     UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
32398     SCANmechjeb.SCANmechjeb:Start()

Seems like MJ changed some stuff that we depend on.

[HebaruSan]

Specifically a bunch of fields were changed from lowercase to sentence case in MuMech/MechJeb2#1708:

MuMech/MechJeb2@1bcbef0

[Dalewyn]

Seeing as the RPM side of things is mostly settled, should we (end-users) expect something similar for ScanSat?

[JonnyOThan]

Seeing as the RPM side of things is mostly settled, should we (end-users) expect something similar for ScanSat?

Yes, eventually. I have some maintenance on other mods to do first, but this is near the top of the list.

In general, any open issue means you can expect it to get done. No promises on timeframes, but I usually keep a milestone for organizing the issues that I want to look at for the next release.

[Dalewyn]

Of course. None of this was meant to rush things, so I apologize if it came off that way.

I've always used ScanSat since the mapping process is a nice excuse to fly out scouting satellites. Downgrading to MJ 2.14.x addressed the immediate practical problems anyway, so I was just curious about the long-term.

[JonnyOThan]

There's a PR here with the necessary changes: #441

This is fairly tiny, so it would be a good idea to make this more dynamic and handle both versions of MJ via reflection.