Flush Foot

Good day, good sir! I just wanted to confirm that the performance/output of (stock) drills, ISRUs, and maybe even fuel cells do scale with their tweaked size? And if so, is there any way to see the estimated performance in the VAB? (I think I can see 'stats' from TweakScale, but maybe this is only part-mass) Thanks!

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!