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
EDIT : Kingston FURY Renegade are good .
Up to you.
That is to say, a 20GB update doesn’t actually add 20GB to the game’s installation size. I mean it’s pretty damn obvious to anyone with a basic degree of common sense that that isn’t how patches work on Steam. Take a minute to think about it logically:
Over the past 2.5+ years the game has been out, the game has received countless updates some ranging from a few hundred megabytes to tens of gigabytes in size. If each update added to the installation size cumulatively, this game, at the bare goddamn minimum, would be over 200GB+ in size if not over 300GB. Yet a vanilla game install only reaches 70-80GB maximum in size. Hell, even with a heavily modded game, the folder size seldom reaches in excess of 100GB+.
Why?
Because that’s evidently not how Steam updates work. Steam game files are stored in bulk encrypted files many of which are GBs in size. If the developers want to update a single, specific file/feature etc, you have to re-download the entire encrypted file and hence why updates can be massive in size. It’s not really hard to understand.
I was just talking the other day I remember when my brother brought home one of the first mp3 players, a 32 mb Rio!
But yeah, I remember the mega floppy disks. Oregon Trail in the school computer lab lets goooo.
I was just talking the other day I remember when my brother brought home one of the first mp3 players, a 32 mb Rio!
But yeah, I remember the mega floppy disks. Oregon Trail in the school computer lab lets goooo. [/quote]
Man I miss Oregon Trail
What if your just a gamer and not an IT tech or PC enthusiast? How are you meant to know how patches actually work? It's not like steam tells you.. All steam says is downloading 20GB for example... Honestly I thought it always added to file sizes.. cause every time A major patch comes up , my drives get a bit fuller.. I only play games, so I appreciate the information on how patches actually work.
Steam "stockpiles" patches, and, depending on how many you've received earlier, it increases the "bytes affected on the drive" value report. If you actually reset download cache, it'll stop spooking you with high numbers.
Either way, it always show you "affected on drive" and "downloaded" values. One is about how many bytes were moved on your drive, and the second is about the actual size of files. Always keep in mind that the downloaded patches often consist of fully replaced files(basically, you download a 113kb file, and it replaces a 110kb file, which means the taken space on your drive only increased by 3kb)