JAFO

Just so long as it's clear it was said with tongue firmly in cheek! Frankly, I'm in awe of what you lot have achieved!

Truly, the first 3 levels in particular should give you very little trouble at all.. have a read through the earlier Caveman threads for some examples.. they're linked to in the first post. The reason you see so many mind-numbingly difficult missions in this thread is that the old hands have now gotten bored with the basic stuff, and are just showing off. While the Mun isn't very far off, Minmus is far enough away that it would make life-support a real pain for a caveman.. and if you play it straight, even a Mun trip should require some supplies. And in those cases, yes, Jacke, the payload limitations are bad enough that it would present some serious obstacles.. (which I've no doubt could be overcome, with a bit of caveman ingenuity)

Ok.. thanks for that.. I really do need to get around to updating those for 1.4 anyway.. a lot has changed since then. Edit.. link in sig has been fixed.. hopefully. In any case, this is the new URL for it here:

How can something intentionally added by the devs be considered "exploity"?

Thanks! Another one for my collection!

This one, you mean? And thanks for the heads-up that my original post was somehow borked.. I've added it to that post again.

Woohoo! Congratulations!

Now that sounds like a caveman technique for checking course corrections, if ever I heard one!

Awesome! Please do!

You're very welcome, and I'm glad it helped.. it would have been a shame to see all this effort go up in flames at this late stage.

What I normally use for fixing undockable or otherwise broken docking ports is KML, the persistence file editor. But given the tangled monstrosity that is your ship, finding the right docking port might be a bit like looking for a needle in a haystack.

MANY thanks!!!

Why not try it and find out for yourself? Then you'll know for sure.

Fair enough.. interesting.. I've only ever tried orbital assembly myself, and figured doing it on the ground must be less of a hassle.. thanks for the perspective. Bummer.. nothing is ever easy, eh? Still, when a caveman attempts the "impossible", obstacles are inevitable, I suppose. Good to see the mission can still proceed. It would have been pretty disappointing and annoying for you if you'd had to abandon things at this late stage.

My psychic powers are telling me that if you ever re-do this particular mission, you'll opt for lawn assembly instead of orbital. Kudos for sticking to this.. by now you must be still docking craft in your dreams.

Ahh.. I missed out on the whole early PCs saga, thankfully.. I was into the UNIX-based Amigas back then.. Never touched a Windows machine until Win98SE was a thing. And not long after that, XP was released. My attitude/opinion is that it took Micro$oft until then to get things half-way right.

Big Fine Rocket Big Friendly Rocket Big F...ing Rocket Take your pick. But in this case, it's most likely a reference to Elon Musk's SpaceX BFR concept (officially called the Big Falcon Rocket). No prizes for guessing how he really came up with the name, though.

<Sigh> The more I learn about Windows, the more I like Linux. If anyone ever invents a time machine, I hope they go back and erase Bill Gates from history before he ever started his damned company.

Thanks for a most succinct and informative explanation.. I'm saving that one for future reference! I am SO tempted to use that for a sig! It gets even more interesting.. see this post of mine on the subject.. Essentially, we seem to have a case of a 64bit program, calling a 32bit dll, which itself makes calls to 64bit dll's, and it works better than Micro$oft's own 64bit dll. Go figure.

Yep.. the original and the best... accept no substitutes. I'd seen on Steam that you were playing KSP recently, but didn't know you were on the forums until I saw your post here. So no, it wasn't your writing style or confrontations that got my attention.. it was simply that just after I submitted my reply, I thought "Hang on, I know that name from TLD!"

I can confirm that the version in the 64bit folder is, in fact, 32 bit. For how to check this, see this article. It uses a wonderful little tool called DependencyWalker. DependencyWalker confirms that the dll has several problems, not the least of which is that it's a 32bit library that calls 64bit libraries. The potential for problems is huge. It's pretty clear this is a less than desirable situation, especially when a 64bit version is available. Your experience of much more stable gameplay after switching in the 64bit version would tend to confirm this. Edit: I see I misunderstood your solution.. hmm.. so a 32bit .dll, called by a 64bit executable, that calls 64bit .dll's, and it works better than the M$ standard 64bit one? Hmm.. very weird. Please do consider reporting all this to the Squad devs, if you haven't already. (Incidentally, it's nice to see you over this side of town! Long time no see!)

That's awesome news! Many thanks!

That's not what he said. Consider the difference in meaning between "there is no 1.4.5" and "there will be no 1.4.5".

It makes no difference to doing that. You can have as many install folders as you like.

Fair point.. and one worth submitting a bug-report over, IMO.