monophonic

Since Mun is orbitin Kerbin above the latter's equator, using it as a target should work for the AN/DN.

Grout / Grouts ?

If you can't get the return to happen by dragging the maneuver node around, remember that the farther away from Kerbin you make your correction burn the less fuel you need for it. So in case you still need to do it, it's best done right after you leave Mun's SOI. Personally, my first time visiting Mun I had to wait a quarter month before returning because I didn't pay attention and took off into a near polar orbit. I didn't have the skill to correct inclination nor enough fuel to brute force my way home, so my only option was to wait until the Munar cycle brought Kerbin into my orbital plane. Thanks to time acceleration that wasn't as painful or boring (to me, poor Bob might disagree) as it may sound.

Sorry about that... DF seems to be leaking into other realities by now. :-P

It was inevitable.

My current pet theory is that kerbals are not a native species of Kerbin. Rather, they are the survivors of an interstellar mission that met some catastrophic failure (Kraken attack?) in the system. Remnants from a disintegrated space ark ending up on Kerbin would nicely explain why so many space ship parts are found simply lying by the side of the road. It would also explain how so many kerbals are recently found simply orbiting by the side of Kerbin. Their drive to reach space to the detriment of all other civil infrastructure would be explained by their desire to get back home. I presume the name "Kerbin" would in this case be diminutive form of their actual homeworld's name. Not being a xenolinguistic I have no idea what it would be though.

Yes, to your last question. You are forgetting that when pointing diagonally, you are not getting the full thrust in either horizontal or vertical direction. In the (bit simplified) end you need (approximately) the same amount of dV regardless of whether you do one burn diagonally or two cardinally. The effects of gravity will cause some difference on the two routes, and the point of touchdown wont be exactly the same either. But the actual difference comes in at an advantage to the diagonal burn.

I have heard of a similar case before. Turned out the culprit was a joystick buried under stuff. If you have one, try disconnecting it.

Works just fine. It's like saying "I want more Saturn VI's!" ;-)

This reminds me, I must build an Eluder in KSP. Then go out and park it on Eeloo.

An understandable concern. But the attempt at fixing it... ...has been poorly executed. It is actually making life harder for all players, experienced and novice alike. My expectation was for throttle to be at the announced 50% when first loading the ship on the launch pad. I cannot accept throttle moving when returning to ship that was already on the pad when I decided to visit mission control or science or whatever as valid UI design, nor it moving when pausing and unpausing the game. Luckily in all likelihood that part is a valid bug, unless Squad has said otherwise. Anyway I'd much rather have it remember where the throttle was when I launched the previous rocket and restore it to that. First default before anything was launched in a new game could be 50% for all I care.

The displayed number is wrong. Actual throughput is one per the displayed value. It's a bug in the UI.

:-D I didn't get it either until you spelled it out. Now it's funny though. :-)

Looks like you'll have to be the pioneer here. Maybe do a quicksave, tell Jeb to stand outside during re-entry and check at which altitude he falls off. Then quickload and get him inside just before then. Or, if save/load doesn't suit you, use another (expendable) kerbal for the test run.

Shouldn't that be 0.22.1 update more appropriately?

Ok, I missed it then. And why 9m11s, there's nothing special in those numbers. Now if it was 1m12s instead...

Sorry to be a spoilsport, but it has a name. It is "Not a Number". Means you somehow managed to totally break reality. Not the usual "divide by zero" way either since that would produce an infinity. Possibly you managed to divide a zero by zero. That's the easiest way to obtain a NaN.

On Kerbin, the oceans mess with you? Reminds me of another place...

I just had to register just to post this: http://www.stationv3.com/d/20120130.html#.UfjHDxisj8E.link