As of the latest revisions, I don't seem to be able to move my 'Mechs anymore (haven't yet tried for other units). The log shows several methods in MovePath and MoveStep apparently calling each other in sequence again and again without coming to a "natural" end until the stack finally overflows.
Turns out that every time addStep gets called, it automatically compiles that step, which calls a method to get all the steps leading up to that step, which in itself includes a call to addStep when it creates this sub-path. I've added a flag to addStep to tell the method whether or not the step needs to be compiled. So, in the case of getting the sub-path, where we already know those steps have been compiled, we don't need to re-compile them.
[r11038]
Related
Commit: [r11038]