Commander Zoom

I went the Indian route with my own program, inspired in part by one of Arthur C. Clarke's famous works. Krishna - one-kerb capsule, initial orbital flights Rama - three-kerb capsule, advanced orbital and munar missions. "The Ramans do everything in threes." Sita - lander, companion to Rama, tested but not actually flown (yet) Working now on further revisions to the Veda interplanetary vessel, to be assembled in orbit from a Brahma command/hab module, a Vishnu service module, and Shiva (nuclear) engine module.

I'm in the same boat as you, OP. It seems wrong to "waste" that time, but... As others have suggested: get Kerbal Alarm Clock, set up your launch window alarms, and then build as much "infrastructure" - stations, bases, satellites, etc - as you have inspiration and/or patience for.

Seconded.

Inspiring! Listening to the other tracks on your 'album' now... thanks for posting!

My compliments to your friend and his truck-building, and my thanks to you for posting this.

Nice rover! The hab looks good, too. Any chance of posting a .craft file (for the first, at least)?

In your own art, which is words, I would say that you are every bit the equal of our celebrated directors. Patiently but eagerly awaiting more.

Not for me, as the DPAI (while an excellent tool) doesn't actually provide a picture, and the Lazor system - even the supposedly stand-alone version - comes with stuff (including a persistent, unnecessary and IMO annoying in-game configuration menu on some screens) that I do not want. So, my thanks to the poster, and I will give his mod a try.

Nice core there, Tilion.

Remember that order Rozer gave Berty? Nothing is as important as the mission. Certainly not some silly vote.

For brevity's sake, I agree with everything Amazonys said.

Did you just tell someone (a moderator, no less) how he should be spending his time?

Love the Compassionate Clamp-o-Tron. The Well-Adapted Truss is pretty spiffy too.

Fixed that for you.

Agreed, and with particular relevance to "Scott of the Antarctic" - you might look it up, if you don't already know.

I liked it.

Maybe to you, but in context with the rest of this thread, it looks to me much more like he's making this up as he goes along and just hasn't gotten around to it yet. I understand your concerns, but perhaps you could try some tact first, before jumping to the accusations?

Wwwwwow. That is amazing. Thank you for sharing it. Some ingenious (and funny) building there.

Another astonishing feat of engineering from the master.

Thank you, that's just what I needed. (And thanks for confirming that the update from the dropbox IS necessary.) I'm aware of the option to patch the functionality right into pods, but I think I'll keep holding off on that. Thanks for that also, though.

Thank you. Still waiting on an answer for the rest of what you quoted.

Forgive the noob questions: unlike many posters here, I don't need any help using this, but I would appreciate some help on installing the forked version properly. So I've gone ahead and backed up my existing "official" version of MechJeb2 in a zipfile, just in case. Ditto my current persistence file. I assume the next step is to delete the existing MechJeb2 folder(s) from GameData and replace them with the contents of the "full zip installl" (sic) MechJeb2-Multipatch zipfile? How many versions is that currently behind the latest build linked on the front page (the dropbox link)? Should I install that build, and if so, how exactly should I copy it over the above directory(s)? Will this work with any MechJeb2 AR202 parts installed on spacecraft already in flight? Will it destroy such craft upon load, due to missing part? Are there any other issues I should be aware of, transitioning from the last official build to this one?

Just wanted to thank Robau for "Swirly Jool", particularly how he handled the storms - to me, the Red Spot is so uniquely Jupiter that seeing it on other gas giants spoils my immersion and/or makes me think that all the creator did was take a stock map or texture for Jupiter, greyscale it, and then tint it some other color. His version has a plausibly similar, but clearly not just recolored feature.

Blergh. That gets so tedious, though, when you're catching a dozen modules and sending them down to the Mun. The idea was to do less baby-sitting during the docking process, automating it as much as possible. 1. Interesting. 2. I'm usually verrrry reluctant to use unofficial/beta forks of mods. 3. It's got a lander can now, with reaction wheel; it's a matter of getting the autopilot to actually use it. All of the above answers (even the ones I don't like) are enough that I'll go ahead and change the status on this. Thanks, everyone.

"To strive, to seek, to find, and not to yield."