Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
You would be wrong. You cant sue someone for not having confidence in a product. I guess you could, but the lawsuit would be thrown out. What contract with Steam or the game company was breached and how did it damage you?
I'll tell you the answer to those questions. 1 - there was no breach of contract. 2 - you were not damaged.
Imagine buying a McDonals burger, sitting on it for 7 months, and then suing McDonalds cause they wouldnt give you a refund 7 months later.
You had an opportunity to request a refund within 2 weeks or 2 hours of play time. So, no, as you haven't suffered damages from what you're arguing as negligence. You should really go back to your arm-chair law school and demand a refund for your tuition.
The system will not load HKEY CU until a user logs into the system, which if you bypass login, then it goes straight to loading that hive data. This gets down to a fine point of how windows looks up registry keys and values however, which I do not have knowledge on and do not care to, I stopped handling windows devices many years ago for a reason.
However loading and processing that hive data very well could have an impact (see below), but as I mentioned before its likely not noticeable for SSD users unless you measured it. Platter drive users would be the ones to notice the biggest impact depending on how large that file gets.
This HIVE is responsible for many users settings including: Personalization Settings, User Specific App Settings, System Settings (settings in Explorer, network connections, device settings), the users environment, AppData (locations to an app's appdata is stored in HKCU), and more. In order for any of those things to be looked up, windows has to load that file and process it, which will be based upon the size of the file, number of entries and disk speed.
I do see the point you're making, however, it would be negligible even with auto-logon. The issue will hit the element limits and break the game (and thus its ability to do anything further) before it would be meaningfully impactful to the boot or user login.
Regardless, long story short this isn't as egregious an issue as people are portraying it to be, however, it is yet another example of incredibly amateurish development on Intercept Games part. I think the bigger issue for Intercept Games in regards to this is the potential implication of this being a rather cavalier use of the registry shocking quite a bit of the ardent fanboys back into reality.
That would be correct, for SSD users they would have to use some tools to measure the impact on the load time. Platter drive users would be the only users who would really feel some sort of impact on time for the OS to load and process the reg file.
Just for fun I had chatGPT come up with some "theoretical" numbers for an idea of impact with a 7200 rpm spinning disk and a worse case scenario where the registry file grew to a size of 10GB. This is also in ideal conditions, not taking into consideration a number of other factors, but for the sake of simplicity we will ignore those things:
Disk Speed: The average sequential read speed for a 7200 RPM spinning disk is around 80-160 MB/s, but this can vary based on the specific drive and its age, among other factors. For the sake of this calculation, let's use a conservative average of 100 MB/s.
File Size: The registry hive for HKEY Current User is 10GB in size, or 10,000 MB.
Using the formula:
Time = File Size / Disk Speed
Time = 10,000 MB / 100 MB/s = 100 seconds
So, theoretically, it would take approximately 100 seconds or 1 minute and 40 seconds to read a 10GB file at a speed of 100 MB/s.
Compared to a M.2 NVME SSD:
Disk Speed: The read speed of M.2 NVME SSDs can vary based on the specific drive and its generation. As of my last update in 2022, typical consumer M.2 NVME SSDs can achieve sequential read speeds of 2,000 MB/s to 5,000 MB/s, with some high-end models even surpassing these numbers. For the sake of this calculation, let's use an average speed of 3,000 MB/s.
File Size: The registry hive for HKEY Current User is 10GB in size, or 10,000 MB.
Time =10,000 MB / 3,000 MB/s = 3.33 seconds
So, theoretically, it would take approximately 3.33 seconds to read a 10GB file at a speed of 3,000 MB/s on an M.2 NVME SSD.
Compared to a SSD on SATA interface:
Disk Speed: The average sequential read speed for a SATA SSD is typically in the range of 400-550 MB/s, depending on the specific model and other factors. For the sake of this calculation, let's use an average of 500 MB/s.
File Size: The registry hive for HKEY Current User is 10GB in size, or 10,000 MB.
Time = 10,000 MB / 500 MB/s = 20 seconds
So by comparison breakdown for a 10GB registry file:
7200 rpm platter disk = 100 seconds
SATA SSD = 20 seconds
NVME SSD = 3.3 seconds
You don't need to spam this in every thread. Should have been pretty obvious that your request would have been denied before you even submitted it.
They seriously think I should do other people's work. Are these people doing my job?
Sure. Why not just ask them to play the game for you too?
Since Gargamel told me in the KSP forum that this problem was with Steam and that I should contact Steam, I did so. with screenshot of the entry. Since there are such great suggestions here that I should clean up my registry myself, I will contact Microsoft and inform them that KSP 2 uses the registry to store its garbage data. Let's see what they say then.
Best regards
All kinds of programs use the registry to store garbage data. Registry bloat isnt a new phenomenon created by KSP2. Its happened before, it'll happen again. Its a minor patch fix. Windows Update has probably done the same thing at one point or another and you had no idea. Just like you had no idea of this particular instance for 7 months, because its not really an issue.
Why are y'all hung up on this? It doesnt damage your computer, it could slow down performance but it would be akin to drinking so much water it kills you.
This is whats really going on, using your same analogy.
You heard theres something wrong with your car from someone. You ask other people about it, and they're like, "ya bruh, your front left tire is low on air. Its not that big of a deal, put some air in it, or dont, whatever." And then you're like, "its not my job to put air in the tire, I'm not a car expert!". More people tell you, "bruh chill, its not even a big deal". But you insist - "I want to sue Toyota and the car dealership for lack of tire pressure maybe doing harm to my car in the long term". I demand a refund!".