Mechjeb2-2.1.0.0 (is this the latest?) does not calculate the next transfer window correctly. If I do the transfer to another planet, wait until the node is set to activate in 9 days but then leave to check something else, when I come back (in just a few minutes with no time warp) Mechjeb says the next window is in 122 days.

How did the window in 9 days disappear?

I've had this happen to me as well.

My minimum time to launch is 2 hours though so when I reach that point if the window it previously claimed disappeared I just go in and out of time warp a few times and eventually it'll see that original window.

While this doesn't address the problem itself hopefully you can use this to get you though the issue while an actual solution is investigated.

Thanks. I hadn't tried that. I'll give it a shot and see if it works
for me.

On 1/27/2014 5:49 AM, SignalSam wrote:

I've had this happen to me as well.

My minimum time to launch is 2 hours though so when I reach that point
if the window it previously claimed disappeared I just go in and out
of time warp a few times and eventually it'll see that original window.

While this doesn't address the problem itself hopefully you can use
this to get you though the issue while an actual solution is investigated.

—
Reply to this email directly or view it on GitHub
#241 (comment).

No virus found in this message.
Checked by AVG - www.avg.com http://www.avg.com
Version: 2014.0.4259 / Virus Database: 3681/7035 - Release Date: 01/26/14

Closing this as an old MechJeb issue. Many MechJeb issues have had little interest in years, have been fixed for years, do not include adequate replication steps, refer to old problems which are no longer applicable, or are difficult to determine what the problem is. This issue is being closed for one of those reasons. We apologize for any inconvenience, but keeping the TODO list tidy helps the developers.

If this bug/issue is still a problem, please open a new issue. For bugs please try to include a Minimal, Complete, Verifiable Example that explains all the steps required to replicate the issue. A link to the KSP.log file should be ideally included, but is often not sufficient information. Screenshots or short videos are often the best way to show a bug.