Mutex

So the length of time the game has been in development (which we don't actually even know, exactly) is being used to infer the speed at which the dev team is working, which is being used to infer the length of time it'll take the dev team to fix the bugs and complete the outstanding features, which in turn is being used to speculate on the chances of the publisher deciding to cancel the project entirely. This is building conjecture on top of conjecture. People are jumping to very, very unsupported conclusions and spreading a narrative that isn't helpful at all.

I think that would be more confusing, it's not very clear what "project" refers to. Even if "vehicle" isn't necessarily a 100% accurate description of all assemblies, it is at least obvious what they're referring to.

There's enough serious bugs that I think it'll take at least a month to make a decent dent in them. I'm hoping there will be weekly patches released for a while as they fix the worst of them.

I don't think it's helpful to discuss the length of time in development at all, really. It frankly doesn't matter. We don't know the exact circumstances the dev team had to deal with, so what can we infer from it? The quality of the dev team? We simply don't have enough info to make any judgements on that. None of us have ever designed and built a game like KSP2 - no one has, not even the KSP1 devs. What matters is the state the game was released in, and the price they're charging. Judge the game on that. Personally I think it would have been a better call to delay by another 6 months, and get a large group of beta testers to really kick the tires before release. I get there were reasons not to do that, but it would have resulted in a much better experience for the playerbase, despite the disappointment of another delay.

One thing I'd like to know, are the bugs reported in the Bug Reports forum being forwarded to developers (after being validated / de-duped of course)? Yeah I absolutely agree with you and Rayne that they should have at least been mirroring any announcements here from the start. Still, at least they're going to do that from now on.

My guess is it's down to visibility / reach. Twitter is completely public so potentially millions of people are seeing any interactions. I don't know how the Discord compares with here in terms of user count though.

Actually it's covered by SDL, which Unity uses for input/output control I believe.

It's astonishing that people are actually still acting like the 25k number is anywhere close to reality. Considering people would be buying at different times of day, in different timezones, not necessarily playing it at all on the first day (people have jobs), maybe not playing it for long given the buggyness and lack of content, maybe playing the game by running the executable directly (therefore not being included in the stats)... the number of concurrent users is going to be nowhere near the number of sales on Steam alone.

Does that hold true when the initial "release" is Early Access?

If I'd already given them five years, I'd be willing to give them one more if it made the difference between a successful game, and eating a massive loss.

I believe the reason for it is for multiplayer - one person going into their settings menu shouldn't pause the game for everyone. Perhaps for single-player it would be better if it pauses the game, though.

This seems like a much more reasonable prediction than some I've seen. T2 know that the better state the game is in, the more sales there will be. They'll absolutely give the developers a good chance to turn things around before they cut their losses.

It would be particularly nice to list the things KSP 2 has that KSP 1 never had. For example, finding parts in the VAB part list is so, so much easier. The favourites list is really helpful for newbies, as it by default lists all the basic parts one would need to launch their first rocket to orbit and back. The more I play KSP 2, sure, the more bugs I find. But I also keep finding things that are better than KSP 1, and that gives me hope for the future.

At the ESA event, there was a bug where rotating/translating a part didn't affect other parts in the symmetry. So you'd have to manually adjust e.g. each wing individually. That was fixed, because it's a much, much higher impact bug than multiple yellow boxes appearing for a second.

Ah, my lander was inside a cargo bay, might be something to do with it.

Flatpak is a way of packaging and distributing Linux software so that it can run on (basically) any distro. It's the easiest way to install Steam on Arch.

Went to Mun orbit and back, and somehow pulled quite a few gees, apparently. The splashdown was a little rough, but still...

No struts between the lander and spaceship. Will try with simpler craft and see what situation causes it though.

I made a spaceship with a lander attached using a pair of medium docking ports. Tried to undock while in orbit around Mun. 1st time, the undocked lander immediately smashed into the rest of the spaceship, destroying it. It was like the lander didn't inherit the orbital velocity of the spaceship. 2nd time, the camera just started flying away from the spaceship (with lander still docked to it), it was like the camera was pointing at a fixed, unmoving point, while the spaceship continues on its trajectory. I managed to switch back to the spaceship (with its still docked lander), the option to undock the docking ports is no longer there for either docking port.

The specs also listed AMD cards, so, very confusing why people assumed an RTX card was necessary...

For me I just had to change the Proton version to Experimental, and it works fine (I mean, no more issues than people on Windows anyway). This is on Arch + Plasma (Wayland), using Steam Flatpak, and AMD 6800XT.

I press M to do both. What buttons do you have to press? Did you change any of the input settings?

I'm using Linux + Proton Experimental, and an AMD 6800XT. There is a lot of graphical distortion on what looks like either a cloud layer, or the ocean. The ocean sometimes looks fine, other times it looks like the below. Another image here: https://imgur.com/lZkqUhf EDIT: Removed "[Linux]" from the title since people are seeing this issue on Windows. Perhaps the AMD driver is the common cause.

Arch + Plasma (Wayland) - I just had to select Proton Experimental, seems to be working now

I meet the recommended specs. Not taking into account any potential performance drop caused by using Proton. But then I probably have bigger things to worry about on that front, like say, if the game starts at all.