Earlier quoted context omitted.
It has jank, but I don't know anyone who stopped playing because of it.
The jank was sometimes part of the fun
The Kraken.
KSP2 is spamming the Windows Registry until the game stops working
121–130 of 306 posts
Re: KSP2 is spamming the Windows Registry until the game stops working
#122KSP2 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.
The pitch showed they know what players want
What they did so far showed they have nowhere near skill to pull it off
Re: KSP2 is spamming the Windows Registry until the game stops working
#123Earlier quoted context omitted.
And every time anyone mentioned any of that on the subreddit they got downvoted to oblivion, including myself. It's like everyone was (and to a smaller extent still is) on a heavy dose of weaponized hopium because the studio invested half their budget into a prerendered trailer. Even the youtubers that got to play the prerelease version pulled out every excuse in the book to not present what they saw objectively.
Watching Matt Lowne’s KSP2 videos just makes me feel better about not buying. It’s just buggier and less. While I was interested in the surface colony stuff they promised for KSP2, the addition of another star system you could travel to was very disappointing. Not so much another system, but that you could travel to it. One thing I liked was that KSP was somewhat grounded in real physics. Practical interstellar trave…
Well, it's natural extension to endgame and players already liked mods doing that
Re: KSP2 is spamming the Windows Registry until the game stops working
#124Earlier 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…
I think for all future development, the industry agrees with you. Chromeium, iOS, Android, and Windows Store apps all utilize packages and per-package storage.
We're just suffering from backwards compatibility for things made over 30-years ago.
Re: KSP2 is spamming the Windows Registry until the game stops working
#125Adding 322 mb of data to the registry isn't going to be healthy for windows either. Registry hives expand but don't contract again. The registry is effectively held entirely in RAM. You are therefore effectively wasting 322 mb of RAM even when KSP isn't running.
I'm surprised they didn't just shoved it in SQLite and called it a day. It's public domain.
NIH I guess. Or maybe some old fart in company doesn't want to let go off their abomination.
Re: KSP2 is spamming the Windows Registry until the game stops working
#126KSP2 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.
Why do "evil overlord" always seem to fail at understanding what they bought, especially the fact that the brand isn't worth much, and what are required investments/plans to capitalize it? Like, buying Palm and reselling cheap Android phones, buying KSP and releasing KSP2 as it is don't seem to make a lot of financial sense. Or does it? It's always assumed "they" make a lot of money by ruining a brand. How and how mu…
not an expert here, but there are thousands of variations of this.. the amount of effort and unique-whatever'ness that it takes to bring a product line into profitable maturity includes lots of people, places and things.. most of those are costs. If capital and their attorney buy the entire operation, with all the layers, the focus changes to the accounts and balance sheet, where lots of happy positive things are mercilessly cut. An unpredictable second part is, willing buyers for some of those parts. What happens from the consumer point of view after that, may or may not appear to make sense. Communicating to the customers costs money and risks reputation. Quite a lot of what happens in decision making is business-secret, some of the bad parts are forever hidden. $0.02 in America
Re: KSP2 is spamming the Windows Registry until the game stops working
#127Earlier quoted context omitted.
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?
Imagine every setting in ~/.config and /etc is stored in corresponding SQLite database, and you have common interface to access both. Now imagine this database is not a great engineering product like SQLite but really, really REALLY fucking sucks at being database, and slows down quickly with sizing up. Now imagine there is no sensible way to get obsolete data out of it, and as every program uses same file it just ga…
> REALLY fucking sucks at being database, and slows down quickly with sizing up.
This is over 20-years out of date.
Re: KSP2 is spamming the Windows Registry until the game stops working
#128Everyone seems to love shitting on KSP2, when the same people forget what KSP1 was like in Alpha. No science, shitty graphics, excessively wobbly rockets, inconsistent orbits, (other than graphics) seems familiar? It took a looooong time for KSP1 to get where it is now, it will also take awhile for KSP2 to be as polished. Chill out.
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 disaster but they basically chose to poach ST developers instead, because why you'd buy a company where management now failed to deliver on promised goals twice.
My guess is ST either bite more than they could chew or purposefuly lowballed T2.
Re: KSP2 is spamming the Windows Registry until the game stops working
#129Everyone seems to love shitting on KSP2, when the same people forget what KSP1 was like in Alpha. No science, shitty graphics, excessively wobbly rockets, inconsistent orbits, (other than graphics) seems familiar? It took a looooong time for KSP1 to get where it is now, it will also take awhile for KSP2 to be as polished. Chill out.
I forgot KSP2 was made by an indie studio /s
it was (althought hired by take2 to make it)
they failed
Re: KSP2 is spamming the Windows Registry until the game stops working
#130Earlier quoted context omitted.
A central key-value store that can be programmatically accessed to persist state across users, processes, and boots, that is also strictly typed and hierarchical is quite useful. I think it would actually be quite useful to have an /etc/conf virtual file system that could be programmatically accessed by user space processes and used as a "dumping ground" just like /etc already is.
I think the "central" part is where you lose me with this argument. What advantages does the registry have over application-specific KV stores... besides the potential to interfere with other applications and the OS itself?
Where do you store where the application-specific KV stores are located? Are you just going to hard-code it so the application cannot be moved or installed elsewhere or on external drives? Where does the OS store its own settings?
There are a lot of problems with software "shotgunning" their junk across the system. This isn't exclusive to the Registry or even a specific OS unfortunately. Just go look at what configuration files are located between applications on Linux for example, it is not consistent at all.