whatsEJstandfor

I'm confused. Are you saying you can get into the game but the performance/FPS makes it unplayable? Or are you saying you literally can't load the game? Because the latter is a real problem a significant amount of people are having, and that should obviously be prioritized. Also, what do you consider acceptable performance? At 5120x1440 on High on my RX 5700, I get about 20 fps, which is acceptable to me given the amount of pixels I'm pushing. At lower resolutions, I can get around 30-40 consistently, which is also acceptable to me. But there are many Gamers™ for whom 40fps would be considered unplayable.

I certainly wouldn't agree. The performance is bad, but there are game-breaking bugs that should be prioritized. I don't think optimization comes until after stuff is already working as expected. Otherwise, all you're optimizing is something that might need to be reworked later, and all of that work was for naught

I know this is a workaround but I still don't really understand why it works. What is this actually working around? And why do the wheels have friction controls at all? What is that analogous to in real life? How much you ride your brakes?

Specs-wise, you'll likely be able to run it at a consistent 30fps at 1080p High, depending on part-count and other factors (performance has reportedly dropped the more vessels you have actively flying). Gameplay-wise, I would recommend it if you're already a big fan of KSP. The bones are there. Assuming we get past these initial pains, it will have been well worth it for me for $50. As it is now, it isn't worth it, because it's frustrating to play at best and impossible to play at worst. But what I bought was a promise that it isn't going to be like this forever, or even for that long. There are moments in the game where I can glimpse the sublime, and I'm hoping that, in a few months, THAT will be the game I'm playing. tl;dr: it's not worth it if you're expecting a fun or pleasant experience. If, like me, however, you love the chance to finally get to try the game out, albeit in an alpha state, and get to see how it evolves over the coming months (and years?) and to give constructive feedback, then it's totally worth it.

I was pretty confident, pre-release, that each step on the roadmap would be about 2 months apart, and that we'd see 1.0 before Jan 1, 2024: Given the current state of the game, though, I'm way less confident. I still feel like a 2-3 month cadence would make sense, but I don't even think we'll get the first step on the roadmap until the major extant bugs are resolved. I'm hoping that, six months from now, we can all look back on this initial release and laugh, and that the roadmap steps will then start being rolled out with that same few-month cadence I had predicted. So, based on nothing but gut feel, I'd guess we get Science in the fall, Colonies by 2024, Interstellar by spring 2024, Exploration by summer 2024, and Multiplayer by fall 2024. I'm absolutely not betting anything on that timeline being even close to correct, though.

Did KSP1 use PhysX and, if so, do you know if it also used this trick? If not, how did it work so well (assuming auto-strut was enabled)?

If you combine this with the Joint Rigidity hack (adding a bunch of zeroes to the existing value), does that help with the wobble? I'd test it myself but I'm at work, lol

Lmao, good example vid. I'd recommend mixing your audio such that the game audio is at a much lower volume; hearing your VO while the engine is running is kinda impossible.

Just want to add that I also have the shimmer effect on my vessel when it's rendered in front of clouds. Version 0.1.0.0.20892 Win11 22H2 Ryzen 9 3900X Radeon RX 5700 32GB of RAM

What do you consider must-haves for the first patch? I'd love if it addressed some of the stuff that makes the game literally unplayable (like getting stuck at Pumping Sim Once, for example) while also addressing some low-hanging fruit (multiple Game Paused/Unpaused notifications). As a layperson, it seems to me like they both are possible, but I wonder if you have your own criteria for what will be a successful first patch.

Same, tbh. Had the game been in a much more playable state, I would have adored this trailer. I mean, I still really liked it, but coupling it with my utter frustration at trying to get the game to do anything I wanted it to, it was such a huge disconnect. I don't know how else to express it, but it felt like I was being mocked somehow. Like, "Ha, look at all this great stuff you've been looking forward to! Enjoy continuing to not have it!"

Just wanted to add to the Greenshot recommendation. It's a tier 1 piece of software

Would nautical miles be 1/10 the size of our own

@Bej Kerman well well well

I suspect that, in a case like this, you could fit the KSC in the canyon between "identifying the problem" and "fixing the problem"

Fuel/Oxidizer Face/Off 15 divided by 0 in hex

As a workaround, you should be able to launch the game directly from the Kerbal Space Program 2 folder in the directory where your Steam games are. Look for KSP2_x64.exe, and try running that.

I really like this mockup, and the tree idea in general: It would also make sense to just combine the Parts Mangler and Resource Mangler into one window, similar to what you have, but also showing fuel levels and dV for each stage/tank/engine, etc. As it stands now, I actually can't think of a reason why they'd be separate. In trying to declutter both windows, they just made each one half as useful (and still cluttered)

If I see the phrase "project workspace snapshot" one more time I'm going to have a stroke

I wonder if the first patch will just set this to a big ol number by default for everyone. That seems like extremely low-hanging fruit.

I would argue that the game not loading and saves not working are more major than those

There's a place for both! The best game communities I've been a part of have had very active forums for thoughtful discussion, and IRC channels for chatting and proto-memery. I don't know what it is about Discord that makes me just not want to use it as much as I had used IRC in the past. I think it's UX stuff. Like, something I liked about IRC is that it's like shipping channels in the ocean very ephermeral. It was meant to be experience in the moment. If you left a channel for a day and came back, you just missed what was being talked about yesterday, and that was fine, because IRC was about being here and now with everyone else. Every time I load up Discord, I'm inundated with thousands of messages from previous days that I just don't care to read, even if I had time for it. I'm introducing a change.org petition to migrate everyone on Discord to the official #kspofficial IRC channel, linked up in the menu bar

As a sidenote, I was able to skip creating an account, and I still don't have one despite using the launcher. Also, you can launch the KSP2_x64 executable directly, though this appears that it may cause Pumping Sim Once to hang in some cases.

I wouldn't be surprised if this cinematic was already mostly in the can for years. Don't forget that Halon also did the announcement cinematic, so choosing them for this cinematic would have been a no-brainer. This isn't the kind of thing you just whip up in a few weeks to try to assuage an audience. Besides, if the developers were going to just be communicating in winks and nudges during this time, I wouldn't be impressed. Given the state of the launch, it's not cute; it'd be frustrating.