This blog post starts talking about the first ever hotfix, since the game was released (4 months ago). Intercept Games managed to “accidentally activate” the DRM on Steam and lots of players reported that they were unable to launch the game outside the Private Division launcher. I really doubt it was accidental seeing how “reputable” and “reliable” Take-Two is. I wouldn’t be surprised if, in the future, this was the only possible way to launch the game. Since then, they have fixed the “issue” and you can launch KSP2 normally through Steam again.

They mention that another hotfix is on the way (of course, release date is yet to be defined, maybe it will be in the next 2 weeks) to fix an issue that makes the navball blurry. They try to, unprofessionally, joke that they are “sneaky little devils” and will manage to include another bugfix in this upcoming hotfix to fix the bug that affects SOI trajectories.

If these fixes prove stable and low-risk, we’ll release a second hotfix. Fingers crossed!

Intercept Games mentions that this SOI trajectory bug was number 2 on their “high-priority list” and credit their teams for a “well-coordinated joint effort” and “fast turnaround” (maybe they live in Mercury where each day lasts 59 solar days, thus they considered it fast). Maybe everything is going according to the greedy corporate plan that Take-Two has for Kerbal 2.

Anyways, the new “high-priority” bug list was decided by community votes, orbital decay being the most voted one, with 25 votes, and UI artifacting being the least voted, with 6 votes only.

So, apparently, the developers really don’t play the game to decide what bugs should be fixed first and instead rely on the community to do some project management for them. Nate Simpson and Intercept Games don’t disappoint in surprising us every day that goes by with their perfect (mis)management! Hooray, Nate, you deserve a raise for that!