Bothersome

It's been proven that reality doesn't exist until you observe it (this on the atomic scale). Since the small doesn't exist until observed, then it stands to reason that the large also doesn't exist until it is observed. Therefor there are no aliens out there until one shows up and allows itself to be observed. This is why Ford Prefect had in his book, "covering your head with your towel". If you can't see the Bugblatter beast of Trawl, then it can't see you. If you can't observe it, it doesn't exist. QED.

The reason KSP was created at one-tenth scale is because they started coding in a 32bit world. If they made Kerbal Sol size, then they would have some pretty crappy looking hills and textures when you got close to them. If they had used larger (read, more detailed) textures and landscapes so that they didn't blur out so soon when got close to them, they would have run out of memory. The original mistake was done in making ksp 32 bit from the very beginning. The wise move would have been dump 32 bit for 64 bit from the beginning and force the developers/writers to make KSP 64 bit from day one. Forget 32 bit. Forget it ever even existed. Go 64 bit or don't do it at all. Squad should have realized that 32 bit was going to be inadequate for a game such as this from day one. Until you get a reliable 64 bit version going, KSP will be plagued with problems from now on.

It's just a shame that the hold back to all your imagination is the 32 bit address space.

I haven't added you to the score board yet because I'm a bit confused on what you want scored. How much fuel are you taking to orbit to leave there and how much are you getting in return for your craft? It looks as though you brought the storage tank back home and therefore leave nothing in space for later use.

Yes, I'm using RO 6.0 too. Think that might have something to do with it?

Just a quick look, it looks as though you've made it so we can simulate launches from other planets/moons.

Awe, that sounds like a GREAT idea. Now, gimme gimme gimme.

Yea, but he's rich, I'm not, so I'm stuck with KSP.

Yea right. As if I could afford my own real life space program.

Me, I've got to go and check on my Hubble Space Telescope to see if there are any more occultation stars ready for observing. And if I had to wait for a rocket to roll out to the pad, I'd start work on my next project. It just makes more sense to wait for roll-out than to wait for cleanup. Cleanup could be thought of as happening before roll-out but the window of time as one still works as one, even though separate windows of time would be better. I for one use this mod to add realism to KSP. Not to fancy up game play. KSP already has plenty of game play, especially with all the other mods. But I use this one for added realism. If it could get more real, then so much the better.

So how do we add time to the process of moving the rocket from storage to the pad?

OK, I have put back in TAC-LS just to give you your log files. Got two of them for you. 2014-09-09_084342.7z 2014-09-09_085108.7z The game shows loading all the mods and modifications made. Froze first time before going black to load menu (Three Kerbals Artwork). Second time froze right after going black and showing that orbit icon at the bottom right, but not orbiting, cause it crashed. Doesn't do this without TAC-LS loaded, so, the problem is deduced to be in TAC-LS. My mod list... Generic Mod Enabler - v2.6.0.157 [D:\Steam\steamapps\common\Kerbal Space Program\MODS] Advanced Jet Engines DeadlyReentry RealChute1.2 RealFuels TweakScale ProcFairings RemoteTech FinalFrontier Interstellar EngineIgnitor StationScience MechJeb2 FerramAerospaceResearch NovaPunch KerbalJointReinforcement KAS RealSolarSystem RealismOverhaul ProceduralParts Chatterer KCT BetterAtmospheres Loaded in that order works fine, notice no TAC-LS listed. Crashes when TAC-LS is loaded last so nothing is causing your mod problems. That's about all I can do for you. You make a good mod. Cause I think it is an excellent add-on, once it functions.

First let me say that this mod is fantastic. If I could make a suggestion it would be,... Can we reduce some of the time for the launch pad reconditioning and put that time added onto the launch itself? Reason I ask is because it seems like a loonng time to "fix" the launch pad. Yet it's instant roll-out of the vehicle to the pad when you get ready to go. This doesn't seem real to me. How long does it take to scrape off the burn marks, repaint the safety stripes, refill the water and fuel tanks, etc.? How long does it take to roll out a 1000 ton vehicle? Just a suggestion.

Yes, I've seen it once on a satellite I put up. I forgot that the flight computer can't estimate the burn time on RCS thrusters alone. I had forgot to put on some type of regular thruster. I don't know if that was the cause but it was doing exactly what you said. MJ kill rot would stop it though. I've only seen this once. My other sats behave like they should.

That's unfortunate that you don't understand what I'm talking about. The way KSP represents position is in floating point math. As you increase a number in floating point, the mantissa grows larger and larger. This leaves less room for the remainder portion of the number. Now when you're doing serious math on those numbers like adjusting where something is suppose to be or be going, and you don't have much remainder portion left in your number calculations, things get a lot less accurate. Which is where the kraken bug you speak of is coming from. It has also been determined that the kraken bug (math inaccuracies) occurs more at 750m/s than any other speed (discovered so far). So, when you say, send out the telescope to 967 AU (or whatever that figure is) that is a long way from where everything else is. This also means that high time compression is going to have to be used. And this also means that either the probe is getting less remainder portion in its positional numbers for calculation or the other stuff you left behind isn't getting them. When you "are the craft" that craft is at 0 position in space. So other things that are not close to you are at far positions in space. So, you can either time accelerate at objects around Kerbin/Earth or "be the probe" and accelerate there. But something is going to catch hell once the distances of 967 AU get realized. Especially if you play in RSS.