Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

KSP2 is spamming the Windows Registry until the game stops working

forum.kerbalspaceprogram.com

Post reply on HN
Print view View original

141–150 of 306 posts

Re: KSP2 is spamming the Windows Registry until the game stops working

#141

Post by golergka »

sBqQu3U0wH wrote: post #53
Arcanum-XIII wrote: post #29

Earlier quoted context omitted.

Not sure, but isn’t unity in this case covering your need for some tools, like rendering, assets management and so on, but maybe not all - i.e deferring to them the physic. Or so would I say assume ?

I heard from someone who actually works in the industry (as engine developer) that companies usually don't use Unity out-of-the-box and write their own tools and extensions (e.g. memory management) and change parts of the engine as the needs vary greatly depending on the game they are making. Not sure how common that really is though.

> write their own tools and extensions (e.g. memory management)

I've been using Unity since 2009, and have been a lead developer and CTO in several different companies. I have never heard anyone writing their own memory management for Unity. May be you're talking about object pooling?

Re: KSP2 is spamming the Windows Registry until the game stops working

#142

Post by dralley »

pratikss wrote: post #18
SketchySeaBeast wrote: post #3

KSP2 is really becoming the premier example of "Nearly perfect labour of love's legacy ruined after being bought by a larger company." More on topic: I have no idea why one would want to use the registry to store this information.

It's far worse than that. Take-Two bought Squad and KSP along with it. Soon after they took Squad's original IP from them and gave it to Private Division to develop KSP 2. Then they poached staff from Squad. It's not like KSP 2 is developed in some innovative way, I was expecting that game like KSP 2 should have been developed in it's own engine since it's so unique among other games. But nooo. KSP 2 still uses Unity…

I'm assuming that the "Squad" you're talking about has nothing to do with the "Squad" multiplayer tactical FPS game developed by Offworld Industries.

As someone not familiar with the KSP ecosystem that threw me for a loop.

Re: KSP2 is spamming the Windows Registry until the game stops working

#143

Post by [deleted] »

echelon wrote: post #76
tyingq wrote: post #4

One of the comments mentions this: "Alright, doing some investigating it seems that they are saving the Pqs preferences based off of the instance ID of the pqs object, which, according to unity's own documentation, changes between runs of the game, hence why its saving 10 trillion different copies of the same data" So, somebody didn't notice a "changes every game" instance ID was in the path and/or data. They thought…

Coming from a Linux background, what is the windows registry and why do things need to write to it? All I ever read about it seem to be horror stories. Can't you store stuff alongside the install? Or in some user data location?

[deleted]

Re: KSP2 is spamming the Windows Registry until the game stops working

#145

Post by ivanjermakov »

Aperocky wrote: post #133
dotnet00 wrote: post #9

KSP2 had all the warning signs of being a disaster ever since the initial delays and controversies with the original studio. Unfortunately, as usual, the community put on hype blinders until it became impossible to ignore.

KSP1 is really complete, especially if you are using OKAN and common mods that people install. I don't understand what they are trying to do with KSP2 to begin with. Skeptical from the start and it somehow turned out worse.

The only complaint for modded KSP1 I have is loading times. I'm surprised devs didn't properly optimized that part.

Re: KSP2 is spamming the Windows Registry until the game stops working

#146

Post by eterm »

mattsan wrote: post #31
TylerE wrote: post #15

Earlier quoted context omitted.

I knew it was going to be a disaster as soon it became obvious that it was a continuation of the old code base, which has a lot of fundamental issues.

This is the first time I'm hearing it uses the old code base - do you have a source? I thought in the initial marketing they were big on saying it's a full rewrite.

It might not use literal code (although it might), but there's definitely signs that some things like the terrain system were cribbed from KSP1, complete with the limitations of that system.

Which means they've ended up in an awful state where even if they were competant (which they are not), best case things might not be much better.

You're right they marketed it as a full re-write to avoid the problems ("Slay the Kraken"), but what was delivered was trash.

Re: KSP2 is spamming the Windows Registry until the game stops working

#147

Post by tremon »

rapind wrote: post #104
dataflow wrote: post #81

Earlier quoted context omitted.

> what is the windows registry and why do things need to write to it? It's a centralized, high-performance small key value store that's the alternative to writing a million config files in random places. It's arguably much better in my experience. E.g. one of the never-ending headaches I always have on Linux is updating config files when a package updates. There's no automatic file merge in general (hence .pacnew and…

What's always annoyed me with many operating systems is this need to organize based on function instead of domain. If I install an application named "Bob" then I want ALL of Bob's configuration to live within Bob. I don't want it split between different registry keys or /usr/local, /etc/, /var, /lib, etc. I'm fine with there being conventions and categorizations, but I'd like to root node to be the application itself…

You are correct, from a user's perspective this seems like unnecessary complexity. But here on the system administration side of Chesterton's fence, these splits enable more secure, more robust and more reliable systems. Among others, this allows for improved backup and recovery, better storage efficiency, easier application of security patches and providing centralized configuration.

Re: KSP2 is spamming the Windows Registry until the game stops working

#148

Post by ilyt »

Xeamek wrote: post #117
tambourine_man wrote: post #92

“Be warned though, deleting the wrong thing can stop applications from working, or even break the entire operating system .“ You gotta love Windows.

Yes, because if I go to /etc or /var and delete some random thing, linux is just magical and nothing will possible break. Cut the crap

No, you cut the crap.

/etc can be entirely readonly to most apps, many of them also either wont start from root or drop permissions right after loading.

That is not the case for registry, far more ways to fuck up.

Re: KSP2 is spamming the Windows Registry until the game stops working

#149

Post by eterm »

ilyt wrote: post #128
ye-olde-sysrq wrote: post #45

Earlier quoted context omitted.

KSP1 was made by a bunch of scrappy lovable indie devs making their first game (iirc Squad's team was a marketing company prior to this?) in a LCOL area funded by dreams and whatever $10 early access sales they made on steam, with no-one to tell them what to do. KSP2 is made by TTWO, who is a publicly traded AAA studio of notable fame and decades of legacy and domain expertise. If Squad sold KSP1's IP to TTWO and the…

> KSP2 is made by TTWO, who is a publicly traded AAA studio of notable fame and decades of legacy and domain expertise. KSP2 was made by indie devs (Star Theory) hired by T2 They just... failed.. they negotiated budget, failed to deliver, negotiated another bigger one, failed to deliver again, and T2 said "fuck it", took IP from them and created studio to develop it. ST actually wanted to sell out to KSP2 after that…

But the people they poached included the management which was perhaps the worst decision that T2 made when they created Intercept Games.

Furthermore, looking at the demos presented in 2019, it's not clear that much progress was made between then and now.

The complete stall since early access release (7 months with just a handful of hotfixes) and lack of feature delivery suggests that IG don't have the competency to deliver.

That, or they moved all their staff to their other "unnamed title" they're hiring for and have KSP2 on the most minimum of developers to pretend they're making progress toward their roadmap.

Re: KSP2 is spamming the Windows Registry until the game stops working

#150

Post by eterm »

ilyt wrote: post #129
mattsan wrote: post #36

Earlier quoted context omitted.

I forgot KSP2 was made by an indie studio /s

it was (althought hired by take2 to make it) they failed

If you're contracted by a publisher to make something, you are by definition not an independent studio.
Post reply on HN