Bej Kerman

I know of one... But first, you must surrender information you have on you. You said you know of a "Kraken Devil Temple"...?

There are links to the soundtrack here, but embedded in this message is also a comment telling you how to extract them yourself if you also want to look at SFX and stuff. Once you have copied the WEM files from KSP 2 and the contents of vgmstream-win.zip into one folder, drag all the WEM files onto test.exe and it should convert them all to WAV. Once you have that, you can drag all of them into a DAW like REAPER, and see what interesting things you can find - this should be more efficient than opening the WAV files individually. You can also enable spectrograms in REAPER and see what looks the most interesting. 95073679.wem is probably the most fascinating so far, but it's so far detached from the atmosphere of KSP 1 and even the parts of KSP 2 we have access to so far that I wouldn't doubt the possibility of it relating to end game content.

I can see what you are doing. Have a good day.

So in other words, you don't know You'll stop asking questions intended to frame KSP 2 as a complete product, then we can discuss.

Hm? On a less demonic note, 128088039.wem consists of the drumbeat motif hear in orbit around the Mun and other drumbeat stuff you'll have heard on mission failures and stage sep. Still, I wonder what non-euclidean Eldritch-esque Outer Wilds ending type stuff would instigate such a dramatic soundtrack. 176668843.wem sounds like what you'd hear from the Voyagers' recordings of the outer planets. 643641982.wem sounds like it could be related to 95073679.wem...

That's exactly what I'm asking, actually. Then you need to reframe your thoughts.

643641982.wem to add to the horror-esque music of KSP 2

No idea what 196515656.wem is supposed to be... Sounds like the Portsmouth Symphonia Jr. What in the 2001 is 95073679.wem?? Horror elements in KSP 2, since when? 644654856.wem and 751643722.wem also sound WAY out of character for funny green aliens. I realise now I'm probably spoiling myself on some big end-game content here, so spoilers beware, play these files at your own risk

Please quote me when referring to me. What realistic reason is there to use nukes with the possibility of torch drives that can work in an atmosphere?

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. It's not the same game and this build of the game is likely only 3 years old. You aren't asking why the stability has regressed from a much older and completely different game, you are asking why the goal wasn't achieved in the very first pre-release version of the game.

We joined in the first two years of development. If you think coming in slightly earlier gives you some kind of high ground... Mhm? And? People who aren't developers can still make competent decisions. Which Squad was seemingly incapable of. That's besides the fact that by 0.18 they were charging money for what amounted to what's barely even a tech demo. "Ultimate Goal" =/= to be done by version 0.1.x Nah, that's just the same 10 people club that are chronically in the forums thinking they know some magic context they refuse to mention whilst calling you names under the mod's eyes. You're certainly good at proving other people's points! Which they have been, else you wouldn't have been notified ahead of the EA drop that you'd need beefy hardware.

You wouldnt understand cause you werent around way back when. Some of us were there, 3000 (12) years ago when updates were fast and loose and modders got priority and early access to updates cause the community was actively engaged. I've been playing the game since 0.18 and Squad squandered most of its potential on focusing on novelty features rather than refining the core of the game. Your comparison is, frankly, a shallow, dishonest and lazy analysis of the situation. You lying about the devs' attitude to receiving bug reports is all I need to hear from you. And, just remember, if the developers didn't do an EA, they'd have continued all the way until the 1.0 launch thinking this stinking community liked the wobbly rockets of KSP 1. <s> But do continue banging on about how Intercept are evil demons who just want money and Squad are just innocent developers who can only do right and didn't do a terrible job on KSP 1, how they didn't have tens of thousands of bug reports piling on while they continued to add superficial features that only held novelty value. </s>

A strawman of the most egregious type.

Maneuvers broken? Any details? Like, did you keep SAS locked onto the maneuver marker or did you set it to stabilize after locking on?

I'm pretty sure I've seen a few Flat Earthers before also wave off context as something that's not important, as if it's not a foundation of most human languages. Furthermore, it's become clear you've highlighted these bits to draw attention from some of the people here with more incendiary opinions on the developers while leaving the context in the image, albeit unhighlighted, so you can cop out of admitting you're using these tactics to misrepresent what Paul is saying. Again, I've seen enough Flat Earthers use these specific techniques to see it when it happens Yes, PDC. They failed to meet the launch expectations for a pre-launch release.

I like how the highlighting dismisses the overall context of the quote. Way to go. Before, forum users were blatantly misquoting "Our ultimate goal is to slay the Kraken!" as "We killed the Kraken", now the naysayers have evolved to do what Flat Earthers have done since the dawn of Wikipedia, take what people say completely out of context using the highlighter tool and leave all the context in frame as if people won't catch onto them cherrypicking stuff. I wonder what people are going to do next. Just make stuff up, perhaps?

And then you proceed to assert in a very sure manner that A. you can't fix a game that's only three years old and B. that the game's foundations are shaky when they really aren't. KSP 2's failings are inevitably going to be ironed out. Why you think, for example, that corrupt saves cannot be fixed whatsoever and must 100% be a deep-rooted problem is beyond me.

They're obviously CGI

I'm not sure why the SAS has to go from Up to Locked when speed approaches 0. More often than not this destroys whatever balance you had going on while landing.

Hands up if you watched this guy back in the early days

Strange, how did I fly to Pluto in 2016? I don't remember any problems with the game at all. On the scale of the stock system, Pluto is almost another galaxy. Yes, you don't want to admit interstellar scales in KSP 1 are broken so instead you only go a fraction of the distance so as to not encounter any distance-related bugs.

Why? I have the latest version of KSP1 in my games folder, why do I have to do such a deep downgrade to appreciate KSP2? It's not even a release title. Are you familiar with this gaming meme? There is such a game, Anthem, there was a road map. But where is it now? Irrelevant

I like the fact my ships look like, well, ships, as opposed to scrap found laying on the side of the road, the fact the clouds look as cartoonish as the Kerbals, the engine plumes, and so on. I can hardly find a time in my playthroughs where I'm not religiously screenshotting whatever I'm flying and its surroundings. And whatever funny orbital shapes I can make with the maneuver node and an ion at 1% thrust limiter. But to each their own ¯\_(ツ)_/¯

Do I only have a choice between very early versions of KSP1 and KSP2? It only makes sense. Eh?

Everything worked fine for me, you must be using early versions of KSP2. By the way, how is the problem of interstellar flights solved in KSP2? Is it definitely resolved? Someone checked, flew very far? Or is this another advance for developers? They have discussed it before and their solution clearly isn't KSP 1's "Kerbol is too far from the player, GO TO RED ALERT!!!"