Lisias

Granted, here is a donut made from liver and kidneys. It will last forever. I wish I could sleep right now.

#StopKillingStudios ! It's hard, costly and time consuming to build a team capable to build a game. We are seeing it in first hand here. All these developers being laid off at the same time will mostly surely switch industries. Many of them will even end up earning more money on the long run - guess how this will reverberate on the Game Industry? Right now, if I would be working on this Industry and since I have a family to care about I would sincerely considering looking for relocation. It's mid 2024 and more game developers were fired already this year than the whole 2023, that was a excrementsty year! The carnage did not ended yet. I'm foreseeing a huge chilling effect also on the Stores, 2025 is going to be even worse than 2024 for Gaming in general. These corporations are, literally, destroying the whole landscape, this is Scorched Earth tactics.

I think the engine is that luggage rack looking thingy over the wheels. Gas engines are notoriously smaller than piston ones, and that air intakes must be there for a reason...

quidquid Latine dictum sit altum videtur I second that. People blame the Industry, completely ignoring that someone has to fund such Industry at first place. The current generation of customers are funding their own slavery. I would be laughing at them if they would not be dragging me with them. People nowadays are just seeking immediate rewarding, completely disregarding any consequences beyound a couple days at best. This is an excellent essay about the current situation on the Industry - and not only the Game one:

Please publish the ENTIRE ksp.log. please use Dropbox or Google Drive or similar services, then post the link here! Also, avoid pasting long pieced of the log on the Forum, it makes Forum slower- and are useless anyway, because we need the whole log in order to diagnose the problem. Right now I can only guess. Remove BDA.Armory and see what's happens.

No, you missed the point. He's talking about "faking" work to deflect responsibilities. At the same time, one would want to avoid "real" work to prevent wasting money handling change requests, as people would be incentivized to engage again. On this assumption, keeping the Launcher would create a facade faking the franchise is still alive by just feeding some nonsense on whatever feeds the Launcher news. By removing the Launcher, they would not only lose this loophole, but also would create an expectation that there're people back on development, increasing the load on the support guys, that costs money. Corporates don't work using common sense, they work by the letter of the contracts (or the absence) disregarding any common sense. I don't know if he's right, but it makes sense. Almost. It's the cost of development vs financial gain vs losses by not doing the work. Yeah, it costs them to do the work. Yeah, there's no financial gain on doing the work. But there's also the financial losses by not doing the work. Paying someone to spend a couple hours every week to give the appearance of development is way cheaper than refunds in the short and medium run. And the long run will be someone else's problem. Now, this is what they are doing? I don't know. The removal of the PD-Launcher from KSP2 is surely an evidence that they are going another route at least with KSP2. It would be nice if they decide to go the same route with KSP¹ and free us of that pesky thing.

And you really think this is a valid, sounding rocket for a engaging problem solver game? This thing would not be stable even on space, what to say on launch? We had gone from a (bad) extreme to the other (yet worst) one.

It's not an unreasonable expectation - some programs really need things like that. But KSP is not one of them (someone in the early days did some pretty nice, long standing decisions for us!)

Yes! If fact, I have about a dozen with different configurations and eve KSP versions. KSP doesn't have any DRM or whatever preventing you from doing it (some other games do).

I don't think we can count with Paradox anymore... (sorry to tell you) === == = POST EDIT = == === And it got worse - the Tectonic Studio (responsible for the game) was closed and the whole staff laid off.

I hate Mondays.

1964 GM Bison. This thingy used a turbine as engine. Incredibly futurist (The Jetsons cartoon were regularly mentioned when talking about it). Incredibly impractical. Incredibly Kerbal. https://www.motorcities.org/story-of-the-week/2023/remembering-the-1964-general-motors-bison-truck-concept

You made me remember Guitar Hero (1): "Never let the drummer handle the money - it will end in tears..." (or something like that!). Thanks! I'm going to need some happy memories today! That's the thing - he's responsible for sure. It's on his job description, so the criticism is fair play. However... I'm working in or to corporations for almost 30 years already, and I'm closely looking the Game Industry for about 5. I have some experience to share: the most publicly bashed dude is rarely the real culprit for a major corporate screw up. There's a chance waaaaay bigger than 0 (I would guess about 125.82% ) that the real responsible for this incredibly epic borkage is more than happy on seeing Nate taking all the blame in this witch hunt. It's obvious that Nate is one of the responsible for this messed up, but no one is able to do such a marvelous screw up without help - lots and lots of help. Don't put all that weight on a single dude. There're more people deserving some bashing - some of them even more than Nate.

IMHO that labels are effectively preventing them from get into yet hotter waters. I think they may walk on a FTC lawsuit (may, not will - there's a chance they may lose, besides IMHO is not that encouraging) exactly because besides implicitly telling people to buy KSP2 because it was going to have a lot of things they are not going to get anymore, all footage at that time made clear everything was in pretty early stages of development - caveat emptor. IMHO they had drawn themselves into a corner after the launching. From that point, they were effectively delivering a bad service (check the EULA, KSP2 is not a product), and so they may be held responsible on that terms by the FTC - on USA and Common Law countries, where Contracts are "Law between the parts". On Roman Law countries, I think they are pretty screwed because Contracts there are "civil agreements" 100% subject to regulatory laws. And the Contract says the magic word "service", so they are automatically subject to the Services legislation, and that's it. I think this is the reason the Europeans are getting refunds more easily, by the way.

I understand your point, but your argument is intrinsically flawed when you say "I'm not talking legalities". Heck, lawsuits are all about legalities. Even on Common Law judicial systems there's the concept of higher laws overruling lower ones. The FTC overrules all commercial contracts they find abusive, point. It's the very reason the FTC exists.

What you understood from what I wrote wasn't the message I meant to transmit. I understand "they" as the last entity I mentioned, Star.Theory. But now, I remembered you anglophones use a lot the terms "former and latter", so apparently the rules for implicit subject are way different between my mother-tongue and yours that I was aware. In a way or another, I slightly edited my original post. Do you think it's transmitting the correct message now? === == = EDIT = == === Gee! The dude is Argentinian! (people knowing the infinite jokes between Argentinians and Brazilians - from both sides - are probably laughing their arses out!!)

Nope. Misleading marketing is ground for a lawsuit by the FTC. Things are not that simple. Besides, KSP2 is a service, not a product. Check the EULA. You can't have it both ways. That said, I'm not telling that anyone suing TTI will win. I think they will probably lose on USA - but they have grounds to try.

This: I don't know what it is, neither want to know.

Please develop. I failed to detect such difference. Quoting myself: Exactly what this is different from except by not mentioning Intercept Games, that were created way after the events the original correspondent was talking about?

This is just to notify that the site is back online right now. Cheers!

Dear sirs, I want to kindly and friendly remind you about a thing called the Art of Synthesis: simple clarification of facts, without finger pointing. The dude (correctly) guessed the problem, but didn't managed to pinpoint the ones responsible for it. I made the smallest answer possible that would explain the situation, avoiding personal bias and opinions (being them mine of from ShadowZone). I assumed that if the correspondent was interested and wanted more information, I could expand the argument pinpoint the ShadowZone video and letting them taking their own conclusions, and perhaps after it engaging on a healthy discussion about the subject. I'm not trying to deny your arguments, they are correctly grounded - but they are not exactly the answer for what the original argument was.

Humm... Yeah, reading now what I wrote, this is a possible interpretation. Language barrier is a sun on our beaches... Allow me to try again. Water is way more dense than air (obviously), so the pressure of the exhaust would eventually not be able to break free from the bell's mouth. Something will have to give in, probably the bell's wall. But this wall is probably stronger near the combustion chamber, right? If we have water enough in the bell, the water will protect the weaker parts of the wall from breaking. If the upper part of the bell is strong enough, the engine itself will be the one giving in - destroying exactly the interesting bits.

Because they really used helmets all time. https://www.nasa.gov/history/55-years-ago-gemini-5-sets-a-new-record/ Not only they were still wetting their feet in space (and, so, environment pressurization wasn't a priority yet), Gemini capsules had ejection seats - and the astronauts must be wearing their helmets to survive such traumatic event (that was never needed, no one is complaining!)

In the last days, with the head cooling down and getting proper sleep, I was thinking about this thread. And I think there's an additional positive post mortem thought on it: now we, finally, know what we are buying. No more wishful thinking, no more promises, only the cold, hard and harsh reality: this is what you get, this is all what you are going to get. Point. You know what? Now it's not impossible than even me will buy this thing someday, once the price drops to a reasonable level - or it enters into a nice sale. Now, assuming that Reverse Engineering will not be banned for good for USA made Software (see my signature), what prevents one to import some (or all) of the KSP2 assets to be used on KSP¹? As long you properly own both games, it would be perfectly legal to do such. You would not even need to copy assets around, being enough to pinpoint the KSP2 installation inside the KSP¹ add'on and let it do the trick - we already have custom loaders, by the way - 80% of the job is already done. You will never have KSP2 implemented inside KSP¹, but some of the features are plausible. (I had bought scraps before to repurpose its working parts - it would not be something new on my life)

You see, besides being one of the harshest critics (you will not find many of my criticisms around - guess why? ), I think things can end slightly better. Yep, this whole ordeal is a major screw up, a really, really, really major screw up - the type of screw up that in some other industry would end up in lawsuits, banning from practicing the profession and, perhaps, jail time. But this is the Software Industry. Worst, this is the Game Industry. But there are loopholes that can make things bearable. One of them is, well, opening the Source (see my signature). For KSP2, this is obviously not happening on our lives, but there's KSP¹ that is well known and highly moddable. Now, assuming that Reverse Engineering will not be banned for good for USA made Software (again, see my signature), what prevents one to import some (or all) of the KSP2 assets to be used on KSP¹? As long you properly own both games, it would be perfectly legal to do such. You would not even need to copy assets around, being enough to pinpoint the KSP2 installation inside the KSP¹ add'on and let it do the trick - we already have custom loaders, by the way - 80% of the job is already done. You will never have KSP2 implemented inside KSP¹, but some of the features are plausible. In truth, once the KSP2 pricing gets into a reasonable level (or in a sale), it's not impossible I would buy it - now I know what I'm buying. (I had bought scraps before to repurpose its working parts in the past - it would not be something new on my life)