RockyTV

They could've tested both qualities in both cards. It shows to me and other skeptical players that they don't care at all and they are just continuing with deceiving players and constantly disappointing us.

Care to explain why the benchmarks were performed in two different graphics card from two different brands? Why not test low and high specs on the same card? This is literally not informative at all.

I don't know why this showed up in KSP2. What is Intercept doing different from KSP1 that we never had a problem like this back then? Are they literally storing object information to the registry and using the instance ID as the subkey, which as others pointed out, it changes every time the game is launched? As for the data they're storing, is this a consequence of not using ConfigNodes as KSP1 used? Why store this information on the registry and not on files? And lastly, this just adds more fuel to the fire that Intercept Games don't even know what they're doing, as pointed out by other members. This is shameful. And mark my words, it will take a week for this hotfix to be released, because it's critical but not critical enough that it should be fixed on the next day after confirming and reproducing this bug. Judging from the past where Take2 doesn't like Linux, I don't believe this will be a problem for them. Even then, the PlayerPrefs docs page on the Unity website list the location for each OS where this class is saved to: so if they ever release a Linux client, if they use PlayerPrefs it will be saved to a different location other than the registry. (and interesting observation, UWP games store it in a file inside AppData, why are standalone games using the Registry?)

3 weeks later and it's finally here. ETA for next patch?

They are. IG is a studio created by Take2 after they cancelled the contract with Star Theory (which was contracted to develop KSP2 and Take2 attempted to purchase them, only for the CEOs to refuse and Take2 poach half of its employees). How well this worked out in the end? The EA release is completely broken. Because the same way everyone tries to say T2 is to blame for the rushed release, they are also saying they are to blame for delayed patches. The patches are up to the developers to release, aren't they? They should've released a patch by now already, at least to fix some severe bugs (hello UI calculations being reduced by 50%???). And judging from the interview @Delaylinked, the devs knew exactly how the game was and decided to not do anything about it (not even release a day-1 hotfix/bug fixing patch) makes them responsible for the state the game's currently in. So, yeah, we're not disagreeing that it's T2 fault for the rushed release but the devs knowing it and deciding to not do anything to polish the release, or release in this state and release a bugfix maximum a week later, they are also the ones responsible for the crappy state the EA release is in. My point is, they know exactly what's going on and the way they handled it just tells me and other fans that they shouldn't be trusted at all. It feels like they're dropping an F-bomb to fans while trying to not make it look obvious by releasing occasional updates to pretend they're working on something.

If this is true then this just made me not trust IG anymore. If they knew the state of the build that was released to the public, why the hell did they release it anyway and not release a hotfix, if they knew about these bugs a while before the game was released to the public?

In other words: we can expect patch 1 to be as buggy as the EA release because the same QA team that, for some reason, didn't find the game breaking bugs we've reported since release, is doing the QA for the patch, and back then those findings didn't allow for the release date to be pushed back. It's not like IG is a contractor hired by Take2. They are owned by Take2. They aren't a small studio. Anyone with a multi-billion dollar company behind their funding and resource management is not "small". If you'd ask people in these forums they would say it's not fair to compare Wube Software with KSP2 devs and they might even say Wube is not a small indie company. Because yeah Wube has a multi-billion publisher behind them and they can use their resources whenever they want, right? Yes they can. David Vonderhaar from Treyarch went public saying it wasn't their fault (3arc) that Black Ops 3 (or 4) was riddled with loot boxes. They went public saying those decisions weren't theirs, but Activision's. So yes. Unless IG is actually scared of being removed from KSP2 development, there's no reason to think they aren't accomplices to this excrementsty behavior in the games industry. Let's not forget that Take2 "fired" the original KSP2 devs and poached them to work for Take2 instead: https://www.videogameschronicle.com/news/2k-allegedly-pulled-ksp2-from-its-developer-then-poached-its-staff/ The thing is, they can be public about it to a certain extent, I agree with you they must have a NDA or something. But Take2 taking "revenge" on them for revealing the excrementsty publisher practices would just look bad for them. I started to question whether it would be a good thing that KSP was bought by Take2 (and I expressed my opinion here) and now we can see that it's definitely not a good idea.

Wanted to chip in that I just requested a refund on Steam, if anyone bought it on release day and don't like the fact that it's been 2 weeks and IG just confirmed on their discord that the patch is not coming this week (and probably next week), I'd suggest you do the same. Will check back in 1-2 years time; if the game gets good I'm buying it again. But I'm really inclined to not give money to them anymore after this crappy attitude towards launching bugfixes in a EA game...

I have to agree with you that they do bend the rules in their favor, but these are definitely not reason enough to justify a removal from the Steam store.

Oh this is interesting: They gave us a EA roadmap with colonies and other solar systems. They promised things that might end up not happening during the EA cycle. Also: literally doing the opposite, charging a higher price and then claiming the game will have a price increase just so no one can say they are being shady by charging a AAA price for an incomplete EA release.

Well, early access is literally open beta testing. If they want to withhold patches until they are stable enough, might as well change the release state from Early Access to released. Then done, no problem, they can withhold patches for how long they'd like. They have a huge user base to do a huge amount of QA. They can definitely skip QA for some trivial fixes like KSC being dragged with your rocket, or performance issues. But no, they want to internally "test" it (which is a bit worrying since their internal testing didn't pick up any of the issues everyone reported) before releasing it to a testing public. From the documentation itself at https://partner.steamgames.com/doc/store/earlyaccess

Well that's clearly what happens with KSP2, if they had a minimal amount of QA or testing the game breaking issues everyone is reporting wouldn't be there in the first place.

Well, it technically is if we look at its price, $49.99 SRP makes it qualify as a complete product, I guess. If by hearing more you mean frequent patches then yes, otherwise just coming to the forums once in a week and saying "hey! we added more fixes to our list of fixed issues for the next patch which will be released sometime soon!" doesn't really do anything to get people to restore their trust in the devs. Also, for those that argued with me and pretty much said it's a dumb thing to demand a more-or-less working, decent product in EA: I realized this type of releasing half-baked products is the industry standard now and not just for games. I was talking to a few coworkers of mine today and they told me that my company does the exact same thing I'm complaining about for IG and KSP2. They promise a ton of things and then they have to deliver. The problem is, it's not me, you or casual, random players. Other huge companies depend on the products the company I work for is promising/developing, so things get more complicated. So, yeah, the industry itself has a problem where there are lots of promise and lack of delivery. We're talking about a EA product here so we can take it a bit easier, but there were SEVERAL AAA games released recently that were literally half-baked games because they promised too much to create hype, get people to buy the game, then they could slowly polish the game whilst also trying to maintain the hype up so people won't lose interest in the game. Which doesn't seem to be happening with KSP2, honestly.

No, I'm treating the game they way it should be: it's unacceptable that there are several game breaking bugs at this state and the least we get is a dev saying it will take up to 3 weeks for the first batch of patches to be released when I've paid 50 euros for a broken, open-beta game. EDIT: in case it's not obvious, thanks to this, ahem, high game complexity and development story, the game is losing players day by day, for the past 4 days it couldn't even maintain an average above 4k players, while KSP1 has 2x the amount of players.

HarvesteR's way worked for their limited resources. IG has an infinitely amount of resources at their disposal and still manage to be worse than the small team that made KSP1. Anyway, it's difficult to convince people that had lots of copium doses that what's going on is unacceptable for a company this size and with lots of resources and new tech at their disposal compared to 12 years ago when KSP1 released. I'm waiting for the first patch and if there are still game breaking bugs and the second patch will be released 2-3 weeks later I'm fighting my way for a refund on Steam.

Except they don't seem to understand this and just want to get as many fixes in one patch as possible.

Except that the OP says the fixes are at least a couple of weeks away, by the time they are released the game will have reached 3 weeks or a month into EA before receiving its first patch. If you think releasing a patch in a couple of days after release is superhuman frequency, I don't know what to tell you. As we've mentioned before, HarvesteR managed to pull it off with a much smaller team and with less resources than Take2 can give PD/IG. And yes, I keep bringing it up because they supposedly can ask for more resources if needed, pretty sure Take2 isn't just making IG crunch and receive a lot of profit from their hardwork while IG doesn't get to enjoy the benefits of having a triple-A publisher backing them. Other triple-A games that were launched into EA had patches just a few days after release, it didn't take long, and if they were game breaking bugs they would have the top priority. What I mentioned about a day-0 patch is simple, if the game was locked for release, you can work on a patch, release the game, if everything went well, release the patch you've been working on for the past weeks. But it doesn't seem like IG was working on anything after the launch and it looks like they just found out about the bugs after the EA release. Which brings to another point, how come their QA team didn't pick up the issues most players are having now? Do they even have a QA team? Maybe their QA team needs to realize they actually need to play the game instead of just checking if the game "works".

Being the devil's advocate here, SQUAD was a media-focused company and had no experience at all with software dev. The problem is not that we want KSP2 to be completely polished. It's the fact they had to delay the release 3 times, plus the feedback they received from the people they invited to test the game a couple of weeks before the EA release, combined with the fact that they are now behind a multi-billion dollar publisher, to have gamebreaking bugs on launch day and not releasing fixes for bugs that have been around for almost a month now (if you consider the time when they did the ESA playtest event). Game was locked for release? Okay, but do the smart move and release a day-0/day-1 patch fixing some bugs that were pointed out a couple of weeks before. This is what an early access release is for, something that IG / PD don't seem to understand. There will be bugs? Yes, of course, no one is complaining about that. We just don't think it's fair to charge almost the full price of a AAA game for early access and not have frequent patches to fix game breaking bugs that the company knew about them for quite some time now. EA is made for testing, but they are treating it as if it was a full release, withholding patches to be released just when they have "enough" content or bugfixes.

I appreciate the insight on in but unfortunately I'm not as naive as the others to believe this is how it's going to work out. As I said, I appreciate you taking the effort of answering our concerns but still, is this exactly what's going on? I just checked the KSP1 version history. Correct me if I'm wrong but HarvesteR was the single dev back then when KSP1 was released. A single person. According to the wiki https://wiki.kerbalspaceprogram.com/wiki/Version_history#v0.0 Initial release on June 24 2011 First patch 13 days later, correcting bugs and adding new features Another patch 6 days later with bug fixes and new features Another patch at the same day to fix some bugs Another patch 4 days later adding more content, features and fixing bugs Since its initial release on version 0.7.3, to 0.8.5, the dev team back then managed to correct tons of bugs whilst still adding new features during a course of 23 days. Probably HarvesteR was the only one doing QA back then, so imagine how it would be to deploy a fix and test it to check if the bug was actually fixed. You guys have the resources at your disposal, and as someone mentioned, how come your QA team didn't pick up the issues that roughly 70-80% of the players are having right now? Also, I think it's important to notice, this game was released in Early Access. It's an open beta, sort of. It's okay if things break (they are broken already). I'd expect the team to be working on fixing game breaking bugs from day-1, but it doesn't look like it. It feels like the team has relaxed after EA release and are just taking things slow, as if the game has been released to an actual released state, instead of EA. If the game wasn't ready to be released, why release in early access then?

not like Intercept Games and Private Division have the resources from Take2 at their disposal, not like they have a multi billion dollar publisher taking care of the game... oh right, they're indie devs, aren't they?

What's holding you back from releasing these patches from day one? Game has been released in EA for a week and no updates or hotfixes or anything. Plus, saying these fixes will come in the next weeks makes the situation worse. As others have stated, KSP2 with a triple-A team behind them can't do what HarvesteR did back when KSP1 released its first alpha/beta versions. I wish the patches would become more frequent. Taking 3-4 weeks after releasing in EA to address some issues that should've been fixed and caught during pre-launch QA tests is simply unacceptable for a company as big as Take2.

This is just sad. And a terrible move by Take2. If T2 wasn't already being criticized for its past behavior (for example, banning singleplayer mods on GTA V, taking legal action against modders from OpenIV and FiveM), they will certainly be criticized now. They pulled funding for an indie studio because they didn't agree with the buyout terms, then poached the majority of its team. My hopes for KSP2 were high, seeing the developers contacting scientists and asking about science was great and looked like KSP2 was going to be amazing. But now it's just sort of gone. I wouldn't be surprised if the game becomes an Epic Games exclusive, with little to no modding support and no Linux and macOS support, all that behind an anti-cheat that doesn't work on anything but Windows. Thanks for killing a dream, Take 2.

What .NET version can be used? .NET 4.7, .NET 4.5 or .NET 4?

Probably asked already by someone else, but are mods going to be exclusive to Steam Workshop, or will KSP2 be like KSP1 and we'll be able to host our mods on SpaceDock, CurseForge or GitHub?

Well, it's not going to be their decision until the developers themselves start boycotting the excrementsty practices publishers do and enforce upon developers. Also, in this case, I'm pretty sure Private Division will accept another exclusivity deal from Epic Games. And we've already saved screenshots and the page where a SQUAD staff said that it's not going to be an exclusive. It's only a matter of time, though. I'm pretty sure Sweeney right now is coming up with a millionaire deal that will cover up the failure of sales when they announce that KSP2 will be a EGS exclusive. And because that's what happens to these deals, you don't need to bother "not supporting the developers by pirating", Epic Games is already doing that for you. It's a trial by fire for PD, Take2 and the new company. I just hope they don't burn the trust the KSP community was built upon. The worse things that can happen are: EGS exclusivity and Denuvo DRM.