jost

Well, the IG and T2 staff has too. So it's no wonder they don't want to risk their job by appeasing people who wants them to "defend their honor" "admitting the game is crap" etc pp. Obviouvsly the communication and development is doing the way the managment wants. That doesn't mean it's perfect or even good. But it's in line with the people paying the checks. Thus it's kind of pointless to expect from developers/community managers/designers etc to do things the community (or the angry parts of it) want but not the people paying for the gig. If these people (aka investors) would like a different approach we would have it. It's a pity we havn't but I don't blame the workers that they won't risk their job on it.

I think that a middle path should be aimed for. First: Commercial providers should be treated different than hobbyists (so an open source company like RedHat or Ubuntu should still be liable for any bad things resulting from bugs in their software but hobbyists can still work on fun projects) Second: I can see why working on high risk things (like medicical or military stuff/controlling power plants) etc should be regulated. In some way it's already: If you apply for a job in a government or otherwise sensitive area (like military supplier) you need to agree to a lot of background checks. Even in my current job as an sysadmin for one of Germanys public employers insurance agencies I needed to provide a police certificate of good conduct. Of course this doesn't help if the company (or state agency see NSA and wikileaks) have a messy mode of operation. But this is more of an missmanagment issue than bad engineering Third: There are bugs which should have consequences especially in information security since most of them are actually avoidable or at least possible to migtate with relative simple effort. Bugs can and will happen. Not talking about them and not issuing a patch if it's presence means that your web shop or whole hospitals/universitys etc can be taken hostage by ransomware gangs should have consequences. Not so much for the software engineers ( I thin it's enough if they might be lose their job because of it although I think I woudn't fire them in any case, depends of the kind of bug and how stupid the error was or not) but for managment. Because: Not communicating and not publishing a patch is not a engeneering decision. So: Companys should be fined when they mess up information security. And I can imagine other bughs which should be fined this way. Third: To put software engineers out of future jobs or fine them with an occupational ban due to bugs in a video game, a web shop or something else which is not actually hurting anybody if it doesn't work like expected seems a little bit harsh to me.

You could keep an copy of the last Version with the bug

I doubt that any staff member of IG, Take Two or Private Devision will talk about their internal company politics and managment wisdom (or the obvious lack of it). At least if they want to keep their job and get another one in the industry in the future. Concerning the steam sale: I guess the publisher want to make some money. Since most people don't want to pay the normal price for the game in it's current state (I wouldn't either even if my old potato would be able to handle it) they propaby said "Hell, let's try to see how many people will buy this for that price so we have at least a little bit revenue out of this mess". I don't expect an official confirmation or denial for obvious reasons.

Well maybe because the root cause is more complicated than fixing other issues? And why should work on science mode (especially but not only the artistic elements) stop? It's good practice to do things in paaralel if you are able to do so. Part designers don't need to stop their work due do game breaking bugs. They can't help to fix them anyhow. And why should an developer who mainly works on heating or the graphic technical overhaul switch his work to another part of the code base he don't even have any clue where to begin with (thus introducing new bugs during "fixing"). The idea to use team members for work they are not qualified to do would only result in more delays in fixing the bugs and the road map.

Very cool! How does it work and how did you manage to get the needed height?

Very cool! How does it work and how did you manage to get the needed height?

I'm not ok with the publishers pricing and communication politics. But it's not a big issue since the game can be refunded. At this point I wouldn't buy KSP2: Too buggy and it wouldn't even run on my potato. I'm fine with buying a new rig but at the moment I wouldn't even know what Hardware I should take ( because the recommended is way over my budget). I'm also not ok with entitled gamers who want the developers to risk their job or working "full hardcore" for a video game. Several times in my career I told my boss when I wasn't happy with a decision. Never ever did I complain about it to the public since I wouldn't risk my income on it. Thus I don't blame KSP2 developers for doing the same. Both opinions are not mutually exclusive.

Well people have bills to pay. I think it's quite entitled to assume that people would risk their job because of such a thing.

I think we need to separate the business, technical and legal issues. First from a business point of view I agree with you: It's not in the interest of T2 to hurt sales ( of KSP1 and 2) by a open source version. Might be different some years after KSP2s finalization/cancellation though. Second the technical side: I would love to have the source code since it would make fixing bugs/developing mods etc a lot easier. On the political side I'm also a Linux-User for 20 years so I think it would be "doing the right thing". Of course there are tools which allow this right at the moment but ( as I don' t need to tell you as Kopernicus maintainer) they are operating in a grey area. So freeing the source under a practical license would be great. Thus: I absolutely would love to have the source but I don't think it will happen before KSP2 is finished

[snip] The success of KSP2 needs more competent team members not less. And even with new hires it would take some time to show any results (since they needed to be trained, getting used to the source code etc).

Hopefully Musk won't do this. The recent development at twitter doesn't look like a good way to do engineering or buisness

Yes, the textbox was white. Doesn't matter anymore though: I uninstalled the mod and reinstalled it with ckan and everything worked as expected I can live with it although it feels a little bit wrong not to know the root cause. Many thanks to you and HebaruSun for your efforts. Best regards, Jost.

Nope. I'm still getting the same error. And I'm trying this since last week.

I can't update Distant Object Enhancement (DOE) /L with ckan at the moment, all I got is this error: @Lisias did some checks in the mods thread at and pointed out that the problem seems to be with ckan For the moment I downloaded and installed the update from CKAN so it's not a big issue for me. I'm wondering however what's the root cause of the error.

Thanks, will do

CKAN doesn't work at the moment: Are you still to busy with real life work or should i report the issue to the CKAN folks? I downloaded and installed the release from github instead so it's not a big issue for me. Best regards, Jost

I came to this conclusion not so much because of the offensive remarks (I don't think they will help but of course people are allowed to feel this way and express their feelings). I also don't talk about the many kerbals who are highly criticial of the state of the game but having good points (e.G data mining showing that KSP2 ist actually just a refactored KSP1, managment issues at IG,T2 , obvious showstoppers going into release, underwhelming communication with the community etc). Obviously these girls and guys are NOT entitled teenagers. But to expect that people will doing a walk to Canossa (1), risking their job just to please some angry video game nerds (who will still be angry afterwards) is just ridiculous and childish. To expect that the developers won't have any vacation until the game is feature-complete and free of bugs too. And I can't help but guess that these kind of people never actually had a job in a company with an own PR department. Which people are most likely to not having these experiences? Teenagers. I don't blame them for it but I don't take them to seriously either. They are entitled to their opinion about the game and I'm entitled to my opinion about them (1) https://en.wikipedia.org/wiki/Road_to_Canossa

Why should he (or any other member of the KSP2 team) publish such a statement? It can only result in his dismissal without notice, why should anybody do such a thing? To risk their job to please a crowd of angry and entitled teenagers? I'm sorry if this angers somebody who is is actually older than 20 but I can't help it: The KSP2 discussions reminds me of an old blog post by Jamie Zawinskis (former netscape developer): https://www.jwz.org/blog/2009/10/big-daddy/

I think it depends in which parts of the Internet you used to hang around. I'm an oldtimer too and started in the Usenet newsgroups. At least in the German newsgroups LARGE CARPS were considered as screaming. And like in real life people didn't like people who SCREAMED without reason. Maybe english speaking newsgroups or web forums were/are different in their nettiquette?

The Image doesn't seem to work for me.

It's one thing to be angry about the work of the developers of KSP2 or their management. I don't think it's helpful or healthy but at least understandable. I don't understand why people expect that modders (who are developing mods in their free time as hobby) will start developing mods when KSP2 doesn't even have official support and API for them.

Last time I checked customers were not forced with a gun on their head to buy anything. If a game suck: Don't buy it, don't play it.

Ouch, this hurts just from reading. I hope your salary compensates at least a little bit for this pain.

That's not the point. Of course everybody is entitled to ask any questions. This doesn't mean that it's smart to ask any question. And like verybody is entitled to his questions and opinions I'm entitled to think that some questions and opinions are dumber than others. Maybe it's because I'm not a teenager anymore but I don't see the point in asking dumb questions just for the sake of asking. And any question like "When will you guys finally admit that your game sucks, your developers sucks and your company sucks?" is a dumb question because nobody will answer such question without risking their job. Which most people won't do no matter how much they hate their job, their company, their boss or their companys products. A smart question would be something like: Given the current issues with the graphic subsystem how do you expect to implement colonies with a decent performance? Or: There is a ongoing debate on multiplayer and timewrap in the community. Some kerbals are concerned that timewrap and multiplayer won't play nice together. Can you say anything how you want to address such issues? The answer will still be mostly PR, but there would be at least a chance in given some insights (let's say 5 to 10 % of the answer) and it would still be a critical question.