Flush Foot

The patches spice must flow!

@ShadowZone is it possible that some of today's fixes are community-driven (time-warp indicators, parachute-deployment failures, etc.), just without the -badge? Another community-adjacent item might be the addition of "obvious Recovery button" (which I won't see until after work )

Is @Provisional Name 45 a @Vanamonde-alt or super-fan?

@Nertea appears to be here, per Online Users anyways, so :hi:

Also to clean up the Steam page... still showing the full roadmap and write-up like "Major updates coming during Early Access: Get a front-row seat as major new systems come online, including the addition of new star systems, interstellar travel technologies, colonies , multiplayer, and more ." (punctuation-spacing is as shown on Steam)

Aziz found a screenshot from somewhere that includes KSP2 under PD

So maybe the WARN really was just about dumping office-space? <thinking/chin-stroking emoji>

I'm moderately new to modded KSP... What is this SimpleRepaint 'Blacklist' of which you speak? (I assume it isn't the NBC show with James Spader)

Apologies... you're right The 'break' is that BTW.C's .dll fails to load at startup Modmanager (or whatever) actually states that there was a problem with it during launch, but only when SimpleRepaint is also present.

My original comment was about KSP 1 allowing you to try (even if it yielded 'mixed results') while KSP 2's warp made even the attempt fail to trigger: To which you said: But when asked for clarification: Me:

Are you sure? If you're warping in-atmosphere in KSP 1, it's a physical-warp, not purely time-warp (as it defaults to in vacuum)... I could see it leading to chute-failure if warping in-atmosphere in KSP 1, but I wouldn't expect the staging event / chute-deployment action to outright 'fail' (ie "not even try")

I think that's the best-case scenario (getting a last bit of work out of the devs)... not the worst-case

I absolutely agree that doing so is... ill-advised... but at least you could do it and see the failure occur, unlike in KSP 2 where trying the same thing just results in nothing... nothing... nothing... kerbsplat!

I've not encountered parachute-bugs in my sessions either, but I also can't swear to never once having a "payload with parachutes within a fairing"... But I do also agree with this point: And again, why does KSP 2 atmospheric warp-mode not allow for staging / chute-deployment?

I was wondering if people were adherents to the Matt Lowne School of Impatient Players ('excessive' time-warping), but even in KSP 1, if you were in atmosphere, the time-warp was 'physical-warp' so you still had full-control over your craft... I have no idea why it is in KSP 2's atmo-warp that you cannot even do staging...

At least the KSC didn't follow you all the way to Laythe (and yes, I know that bug is / seems to be gone now)

I think the idea is that while T2 is the one shutting down KSP 2 development*, it was Nate who was constantly 'overstating' the condition of the product we were about to 'receive'. *likely from visible evidence, but "unclear"

Finally found the straw that broke the camel's back... <ignore-list++>

@linuxgurugamer ... I know that Simple Repaint is not your mod, I am wondering if you have any idea why two mods (yours/this one and Project Orion) 'break' when that mod is installed. "No idea / don't have time to investigate" are perfectly fine responses, I just thought I'd "flag" it.

Removing Simple Repaint also allowed me to successfully load up 'BetterTimeWarpContinued'... weird!

I simply noticed the activity because I have a tab for 'online users' with a filter for KSP Team, and JJ is one such profile: Just Jim KSP Team I wasn't saying "boo" about culpability... I just haven't often spotted 'KSP Team' (or Community Manager) on anything besides "Viewing Forum Index". I also wasn't saying 'this person has doomed the game', just that they were looking at this very thread when I spotted them.

Who said they were authorized to 'relocate' it? Might it not have been the legal property of ST and thus, despite the KSP2 contract moving from ST to IG along with many of the employees, the code maybe could not move over as easily?

Might not Kerbals having noses look kind of like Sonic the Hedgehog having (human) teeth?