Jacke

5188: Find the sign for floor 5187 on the floor, realise there were 2 floor 5186's.

Ah, ClF3. Let's see what John D. Clark said in his autobiography Ignition! (1972) Chapter 6, "Halogens and Politics and Deep Space", pp73: In short, like many of the halogens and exotics, the advice is simple "Don't use, not worth it."

I really miss not being able to 'like' posts. I love '2001' and have since seeing it back in 1968. I'm going to see it again this coming Tuesday.

When I deorbitted the 2nd stage of the KILOLIMA, it survived reentry (even with SAS stuck on) and slowed down to just above 70m/s before impact. All of it was destroyed, but I can believe the larger upper part of MIKE had something survive.

I haven't heard anything about what data structure will be used in KSP2. But if it's a more general graph type than the tree used in KSP1, that can make traversing it more computing and memory intensive. So it may be different that the KSP1 tree, but I don't think it'll be radically different.

And there's a 3rd option: use the mod EasyBoard. Look in the first post for "Herd Instinct". It'll tell you how when maneuvering a craft to have it automatically pick up a Kerbal on EVA and either grab a ladder or board.

Thanks for tracking down the source of the SAS locking, @ManEatingApe. Considering we likely have to wait for a launch window but also would like to hit the first one, if that's before day 109, perhaps a manual edit of the .sfs file to fix the offending timestamp should be tested. In other news.... This time, I created a branch of my own forked master to receive my changed files and to originate the pull request back to @ManEatingApe's master. https://help.github.com/en/articles/creating-and-deleting-branches-within-your-repository After the pull request was accepted, I deleted my branch, then attempted a different way to integrate the master's commits into my fork. https://stackoverflow.com/questions/20984802/how-can-i-keep-my-fork-in-sync-without-adding-a-separate-remote/21131381#21131381 Alas, GitHub's interface doesn't have the proper tool, a git push, so I did it the other way in that link. Results: my fork was now the same as @ManEatingApe's. But damned GitHub still had the damning and incorrect words "1 commit ahead of master". Final results: I just deleted my fork and forked again from the master. Again. Sigh.

DELTA doesn't appear to be affected by it. When I undocked DELTA in my flight, it starts with SAS off and toggleable. I just checked it again from my submitted latest.sfs and DELTA still behaves that way. Using the updated latest.sfs, I just test undocked the other 4 cores from MIKE (the 3 vacuum landers docked at the rear and the first one docked to the front). After undocking, they have SAS off and SAS is toggleable. But the KILOLIMA 2nd stage was affected by it. After I undocked it, it was as MIKE, with SAS active, showing lite but greyed out, and not toggleable. When I redocked DELTA with the KILO tank, its SAS was on. When I docked the 2nd stage, its SAS was off. I don't know if that is repeatable.

This SAS locked-on thing might be a disaster waiting to happen. It's inherited by parts of MIKE that undock. I can imagine this screwing up at least the LAYTHE craft. Don't know what caused it, but it was already in the state of MIKE on the LATEST I received. Just confirmed that to be sure.

It's not fine-grained attitude control (which still can be toggled on and off). The SAS light is on but greyed out. Can't disengage SAS. After docking the KILO tank to MIKE with DELTA, when I detached the KILOLIMA 2nd stage from LIMA to deorbit it, it inherited that state with only one probe core. The 3 cores in BRAVO, VICTOR, and TANGO are hibernated. The DELTA core and the other forward core on MIKE are still on, so that there's still a live core on MIKE when DELTA undocks. ( @ManEatingApe, perhaps we need an update to the Mission Plan in the first post along with some updated module pictures.) Anyhoo, here's after I docked DELTA with the KILO tank (even docked with SAS engaged, yay). And here's after I undocked the KILOLIMA 2nd stage. @ManEatingApe, let me know if that's okay. I'll get onto updating my fork and put in a pull request with the new latest.sfs and latest.loadmeta. EDIT: Pull request with updated files created.

I have docked LIMA to MIKE with the KILOLIMA fuel 2nd stage still attached. DELTA with the KILO tank still attached is about 270m away. Just killed the low relative velocity and proceeding to dock.

I'm trying to maneuver MIKE to line it up for the docking of the KILO tank LIMA. But SAS is showing on MIKE as lite but greyed out. I can't rotate MIKE with the reaction wheels and I can't toggle SAS. Any idea what's going on with MIKE? EDIT: Turns out I can rotate MIKE. It's a bit slow now.

So...like the last time. But no Boaty McBoatFace stage. But likely with more crazy crashes and flying out replacement buggies.

Rendezvoused just outside of 20m away from MIKE, 66m/s remaining. Switching to DELTA.

MIKE is in a 79.8x80.2km orbit. I've launched KILOLIMA fuel into a 73.0x79.5km orbit and it's about 30deg behind with 185m/s delta-V left in the 2nd stage. I will be able to get a close pass and commence close rendezvous. Then I should be able to assemble KILO fuel tank and LIMA onto MIKE with DELTA.

@ansaman, very few mods are locked to a particular version of KSP. While it's better for those mods with code to be recompiled for each version, it's not necessary. Some mods require mod recompile or are locked to a KSP minor version. Kopernicus is an example of a mod locked to the KSP minor version and its version numbers reflect that. Most minor KSP version differences don't matter, in that a mod for version X.y.z will work for later z. KSP 1.7.0 to 1.7.1 was an exception due to the release of the mod Breaking Ground and changes that happened with it. The current Kerbal Attachment System mod doesn't work with KSP 1.7.0. Parts mods can be often used over many KSP version changes until something is change with the parts systems. That has happened recently and older parts mods need ModuleManager scripts or other fixes to avoid minor issues. Otherwise, you can often find mods even back to KSP 1.5.x, 1.4.x, and even rarely earlier that still work. The forum topic for a mod is a good resource. A good way to handle the problems of mod dependencies is to use CKAN. Once you set up for your KSP installs and adjust the Compatible KSP versions, it will handle most of the mod dependencies. I use CKAN to run several KSP installs of different layouts and versions. I only rarely need to manually install mods (and I have another tool for that).

Huh, think that's bustin'. It's exactly 299,792,458m/s by definition (in that with the definition of the second it defines the metre).

Ah, @Triop, I see you're finally acknowledging your true nature. Good, good! It does. As for landing.... LOL! Those short aircraft are tricky. Try either landing at a faster speed and/or putting in some rigger's angle of incidence on those wings so you don't have to nose up as much. Some way to see your vertical velocity might help too.

Might I suggest Mahal's QuickBrake (now maintained by @linuxgurugamer).

Well, then, we'd be overrun with Little Red Men instead of Little Green Men. Reactions are disabled except for staff and moderators until what's not right is fixed.

Yes. I was away for a while too. Lost in time, and lost in space....

Got the latest latest.sfs and loaded it. There's 2 craft (and 7 debris) in orbit: Core_U, which looks like the jettisoned front of MIKE, with just a core and electric charge keeping it from being debris; and 'FOXTROT', obviously the rear of MIKE with all other craft docked, the mission spacecraft under construction. Renamed it MIKE, made it a Station, and turned it up from 5 (?) to 11. I believe @ManEatingApe said next is a KILOLIMA fuel. Where and how does that fit into the final assembly? I'm not sure how to proceed especially as I don't see in that test final assembly image a vessel docked to MIKE that has a large engine facing forward.

Apollo 15 had 1 of its 3 main 'chutes fail to deploy. But the Command Module was designed to be able to safely land in the water with just 2.

@ManEatingApe, if there's anything left to launch and dock to MIKE, I'd like to give it another try. And apparently you can get Configuring Vessel Naming in flight. Explains it when it was added to the game. Also covers these special cases.

One thing I found out that I did wrong with my docking from watching another docking video. I forgot to turn off SAS just before contact. That's what likely resulted in all my dockings bouncing.