Allow pausing the game while setting up a maneuver

[Kasuha]

For long burns, maneuver nodes are unreliable. I already experienced it several times, last time it was today when I prepared a mission to Moho with single burn from Kerbin's 100 km orbit. The burn was 12 minutes long. I started it six minutes ahead of the node and finished it to within 1 m/s. After that I was well over 5° off the planned trajectory and definitely not going to intercept Moho. To fix it I needed to execute correction burn which was over 250 m/s, about 15% on top of the total planned maneuver.

Of course it would be best if no corrections were necessary, if the burn accounted for the burn length and corrected for changing conditions during the burn (like direction and strength of nearby body's gravity).

But I understand that might be very complicated.

So the only thing I am asking for is to allow pausing the game while setting up a maneuver. Because fixing a maneuver node aiming to the other side of the system while the ship is speeding at over 3000 m/s low above Kerbin is next to impossible.

[Shepard]

And for every times I accidently close the node because I had to plan it fast, the only thing I can do is to agree with that idea.

[Roderik]

I agree totally

[Yourself]

Of course it would be best if no corrections were necessary, if the burn accounted for the burn length and corrected for changing conditions during the burn (like direction and strength of nearby body's gravity).

That would certainly be more computationally expensive, but not necessarily that much more difficult. The solution wouldn't have to be perfect, just closer to what you'd actually get. The game could make several simplifying assumptions, such as the rocket being a point mass, no staging in the middle of the burn, and the rocket remains pointed in a fixed direction.

I'd kind of like to see this as an unlockable guidance computer part. So you wouldn't have access to better prediction initially.

[Ernest3.14]

I second the 0x time warp part of this suggestion. Maybe even 0.5x, 0.33x, 0.25x, etc.