DrKerbalMD

Exactly. The KSP2 Kraken is still recognizably The Kraken™, and it's a meaner Kraken at that. So that leaves us with two possibilities: The starting point for the KSP2 physics sim is the KSP1 physics sim. The code was largely transplanted from the old game to the new game. If that's the case, why has it regressed so severely? The starting point for the KSP2 physics sim is Unity itself, i.e. the physics sim has been reimplemented from scratch. If that's the case, why is the Kraken back? If the answer to that question is "limitations of Unity," then what was the point of reimplementing the physics sim? KSP1 physics sim had the benefit of 12 years of iteration. It was battle tested. Why throw that away just to recreate all the same issues, many of which the old one had already conquered? If the answer to that question is "well the rest of KSP2 is too different from KSP1 to simply port the physics engine," then why set the expectation that the physics simulation would be improved over the first one? That's my real question here. If they thought the KSP2 physics engine was going to be a better foundation, what went wrong? Can it still be salvaged? On the other hand, if they knew it was going to be worse on launch, why talk about it at all?

What did I ask that frames KSP2 as a complete product?

So in other words, you don't know. Got it, thanks!

That's exactly what I'm asking, actually.

I'm not asking why it isn't done in 0.1.x. I'm asking why the stability and reliability of the physics simulation has regressed from KSP 1.12.5 despite the fact that fixing it is a stated objective for KSP2.

So, serious question: what's going on with the physics simulation? How did we go from "our ultimate goal is to kill the Kraken" to the Kraken being alive, well, and angrier than ever? To put a finer point on it: What did the dev team do which led Tom to believe the Kraken could and would be tamed? Why didn't it work? What's the plan to wrestle the Kraken to the ground for good?

Thank you R-T-B and Gotmachine!

Thank you for bringing that config line to my attention. Now I can reinstall mods with Community Fixes as a dependency. I understand the logic here but the Mohole was promoted from bug to feature years ago. It's definitely not a bug anymore: it has a dedicated biome and appears on the map. "Fixing" this bug really just introduces a new bug in the form of a discrepancy between map view and ship view. Worse, other mods declare this mod as a dependency so from a CKAN user's POV, installing, say, Procedural Fairings removes the Mohole for no apparent reason. This setting really should default to "false."

This mod removes the Mohole from Moho. See this Reddit thread for screenshots: