KSP2 is Spamming the Windows Registry Over Weeks/Months Until the Game Will Stop Working Permanently
KSP2 is Spamming the Windows Registry Over Weeks/Months Until the Game Will Stop Working Permanently
Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB Main Issue: KSP2 will throw a PlayerPrefsException error when the game's registry Key/Entries is filled up with too much information, At that point KSP2 will n...
Lol jesus
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
Lol. They dun goofed hard
This is the kind of mistake I would have made as a CS undergrad lmao
I mean, why bother reading this ID in the first place. It's not relevant to the underlying object outside of the immediate context. They can't set it, so it's not even used when writing the stored data back into an object. It literally does nothing, and yet they have managed to use it to completely fuck up their own registry keys and affect their players.
KSP2 is adding information every time a SOI change happens or if a save file has been loaded.
How do you fuck something up this badly?
Are they also storing binary data as comma-separated hexadecimal? Am I understanding that correctly?
It could just be that that is how it is presented.
I bought ksp 1 before it was on steam, never once migrated even though they've begged me to for ages lol, I think I bought before the Mun was added. I still stand by never buying ksp 2 and just using more and more mods for 1