MStefan99

Agreed, I have yet to see a "1.0 full game" release that actually changes much about the game or its community, aside from maybe adding a few extra features, completing the story and raising the price.

I obviously don't have the numbers but I would argue that many of these channels are a place for existing KSP fans to gather. I haven't signed up for this forum because I saw a new game I might be interested in but because of the hundreds of hours I spent in KSP 1. As they say in "The Kerbal Effect" , KSP "has inspired a whole new generation of rocket scientists" and only marketing KSP 2 to existing fans of the series does not seem like the way to ensure it does the same.

I could see that... if they were actually posting there a lot but we only got a few posts since EA announcement

That's actually a bit disappointing if it's still the case as I feel like ray traced shadows and reflections would've looked great in a game like KSP. But why are they still on DX11?

We already know that KSP 2 will be built using a newer version of Unity but have we got any information on the new technologies the game might use that weren't in KSP 1? I'm talking things like HDR, ray tracing, DLSS/FSR, VRR, etc. The only thing I've noticed myself is that they seem to use HDR Color picker in Unity in this dev diary. Does this mean the game would have some meaningful HDR support?

I like the variety of parts in KSP 1 but I'd love to see some basic things be adjustable, like size. I had TweakScale mod installed pretty much at all times when playing.

I'm not, I'm just talking about one specific feature here which I think is implemented well there. If you want my opinion on SR2, it's way less polished than KSP, there's just not much to do in terms of gameplay.

While a "normal" programming language will be more flexible, it will almost certainly be less approachable, especially for those who haven't done any coding before. I think kOS would have much more users if it had a nicer syntax or something more visual like Scratch. I personally quit kOS after making a few scripts because I didn't feel like learning the syntax, and I'm a professional developer. Stealing another idea from SR2, there are multi-functional displays. Those are basically tablets capable of running your program. You can display any information on them, you can have buttons to control your program and much more. The best part, you can put those anywhere on your craft, even inside your cockpit!

Pretty sure performance hit will be negligible compared to physics and graphics calculations. Besides, if there's no code added then there's nothing to translate.

Probably never happening. All modern consoles and Windows 10/11 support background recording already. It's not perfect but don't think devs will spend time on that.

KSP 2 is having automated logistics? What did I miss? Well, many things in the sequel are strictly speaking "unnecessary" but wouldn't it be cool to have automation anyway? I think the demand for it will be there - kOS was downloaded almost 200k times (KSP 1 sold around 6 million copies) and even SR2 - a much smaller game than KSP - has this feature built-in.

Imagine when your expensive rocket with Kerbals crashes because you ran out of drive space... Ugh! I'd rather have autopilot be later in the tech tree but without these "performance limitations". And for progression there might be additional sensors you could unlock later on to give you more data.

Sure, it has to be optional, and with a way to share scripts using something like Steam Workshop you won't have to write them yourself but could use ones created by others.

But why not give players access to all the data right away? Locking information away behind the tech tree doesn't seem necessary to me when more advanced parts already are. Like, what exactly could "more advanced" information be that needs to be locked? I can see, however, some data being unavailable if you don't have a corresponding part, like having no pressure data if the rocket has no barometer. Also, why have one centralized computer? Going back once again to SR2, in that game you can have multiple computers, each running its own program at the same time. In my opinion it's actually more convenient to have many smaller scripts rather than combining everything into one and not using half of it. Oh, and each computer in SR2 can also have an interactive display to quickly view or change what's going on. That would also be a nice addition.

Seen that, that's why I said it's controversial. However, that post focuses more on what, not how. I also don't think we need any additional modules for the automation, just like in SR2 (much less a module for every action). Thing is, your craft would be naturally limited by your progression: you may write a program to fly all the way to Eve but if your craft doesn't have enough delta-v, then well, you can't. Speaking of key frame automation, we already kind of have that in KSP 1 and it should absolutely be a thing in KSP 2. However, my issue with that is the absence of any inputs, in a sense that your "program" doesn't know anything about the world or the rocket (good luck keyframing suicide burns in stock KSP 1!). But if the devs were to add some inputs, it would be very nice indeed. Still, having a full-fledged language that can do loops, conditions and complex math is much better if you want to tinker with it. And yes, having programmed probes would be sick!