blizzy78

There's no need to get a perfectly circular orbit in the first place. So to stop the markers from wobbling around, you just need to raise your apoapsis or periapsis by a few kilometers.

Please don't. Posts containing "me too" or "I second this" don't add anything useful to a discussion.

RAD+ is the "radial" direction. In a circular orbit around a body, that would be exactly towards the sky - away from the body.

Not a gameplay question. This would be better suited in the Addon Requests and Support forum, I think.

It looks like you're doing it Apollo-style - which forbids the pre-docking in the VAB, mind you - and have a docking port right below the decoupler. You can also right-click the docking port and select "Decouple Node". That should separate the decoupler from the craft.

If I remember correctly "idx" is the seat index number of the part a Kerbal is assigned to.

For fuel transfer the yellow lazors must have line of sight, as does the main lazor.

Here some more documentation: http://forum.kerbalspaceprogram.com/content.php/121-Writing-Tutorials-A-Demo-%28and-some-source-code%29

Personally I've switched to using fairings all the time (with the Procedural Fairings mod) just for the looks. I'm ignoring nosecones, though

You might want to try out my two in-game tutorials for orbital rendezvous and docking. (see signature)

Right, going backwards is pretty good advice. Actually I've done that with my Eos Program, too, though I didn't tell that. Actually the real reason for the whole program was to get proficient with manual landings on non-atmospheric bodies. I just didn't want to rely on MechJeb anymore. But then I thought, heck, I know how to build ground bases, so why not set up a Kethane rig there, complete with a refueling station in Munar orbit, plus a fuel shuttle. So there, I walked backwards from all that, leading me to a total of 25 launches...

Before I began doing my Eos Program, I've laid out the complete program in a simple text file in Notepad. (Yes I know there are better editors, I just didn't bother So I just set everything up and followed that plan.

heh, okay... sometimes you need to juggle around with the vocabulary... craft, vessel, vehicle... lose the "file" word... such things

That's basically how you start making a tutorial - you set up a savegame that serves as the basis. Personally I just use HyperEdit to put things where I want them to be. Other than that, you need to program a DLL that will be driving the tutorial pages. Have a look at my in-game tutorials and their source code to see how it can be done. (see signature)

Ah well. Sorry about that, I was just curious why "searching for days" would not turn up the mod. Pardon my ranting there.

Your "solution" is exactly what I described earlier: Pardon my saying this, but I think you only see what you want to see.

Not sure what you were searching for, but googling "ksp change root part" turns up the SelectRoot mod right on the first page for me.

You might want to try out my in-game docking tutorial. (see signature)

Only deleting the ladder might confuse part indexes.

So what is the question? Besides, a parachute does nothing on the Mun other than speed up your fall. There is no atmosphere there.

heh, looks like I got my own section there... thanks

Does it feature a docking port? If so, you can try to dock with it, then use the Crew Manifest mod to do IVA crew transfer (as opposed to exiting the hatch, then entering another hatch.) Other than that, I think they're doomed :-(

Well, have my apologies for trying to help.

The only thing I can think of here is that even though you do manage to get "NaN" at the AN/DN, the relative inclination is not perfectly zero because of the long distances (and rounding errors) involved. If that is the case, there is nothing more you can do but to wait for the next AN/DN (most possibly only after you've achieved a stable orbit around the target body.) He was trying to guide you through the trajectory. Of course the "5-10 days before encounter" mark comes after the mid-flight inclination change at AN/DN, and he pointed that out before that correctly. Again, he was trying to guide you through the trajectory, advising you to make additional course corrections as you get nearer to the target.

What exactly did you not understand? Please elaborate. It all comes down to doing mid-course corrections, the most important of which would be a plane change at the ascending/descending node. To which you replied it would not work.