MechJeb2

MechJeb2

4M Downloads

Autoland not working

Ryland3 opened this issue · 5 comments

commented

Hi - I've been having problems with the autoland feature. Attempting to land at a target often causes the initial deorbit burn to go crazy - it usually puts me in a polar suborbital trajectory. I don't think it's related to the craft having control issues because it's common across many craft that work very well with mechjeb in other maneuvers.

So usually I have to manually cancel the deorbit burn once it gets close to my target, which is not too bad actually. However from there the plugin does not autowarp (the box is checked), and sometimes it doesn't do anything after that - the status stays as "doing high deorbit burn" all the way to collision with the ground.

The Land Anywhere tool is also not autowarping. I'm running it now to see if it brings me down safely, I'll update with that info.

Let me know if I can provide anything to help! I'd love to get this fixed, it's quite frustrating for me.

commented

Try the latest dev build of MechJeb2.dll at http://jenkins.mumech.com/job/MechJeb2/ and see if it doesn't solve your landing issues.

Land anywhere doesn't autowarp (yet).

commented

Yeah looks like Land Somewhere isn't working for me either - I got about 10km up from terrain and it started trying to decelerate before it flipped out and spun prograde instead of retro. :(

commented

I have been getting this with manually entered Coords, compared to clicking on the map. Not entirely sure if it is caused by entering coords with such a large East coordinate it can be expressed as a small West coordinate.

commented

On this topic, interesting behavior can be achieved by manually inputting coordinates on the extremes (N 90° 0' 0" for example).

I had to manually schedule the deorbit burn and course corrections, and not activate the landing autopilot until rather close in or else it'd burn in incorrect directions. Also, at 90° 0' 0", the target marker does not appear.

commented

Closing because we fixed a bug that caused similar symptoms in 2.0.8: see #64. Please open a new bug report if you still have landing AP issues in 2.0.8.