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
Notably if something is slowing down your install speed, that's on your computer's end, not on steam. As you say: the download itself takes nothing for time.
Make sure that your drive is allowing steam to work fully and properly. But I mean we just had a discussion about this very thing recently. All games patch this way, as far as I have ever known, any amount of code must actually validate and insert that code *fully*, so yeah it's going to be looking at the full install.
If your update has a patch, leave it alone to finish.
Same games that used to take under 2 mins to patch now take between 8 and 15.
I don't know of anything that could be throttling disk speed and I have made no changes to my PC from when it was working quickly. Usually my 960 NVMe was very efficient for time when doing patches.
Steam says its running between 50-90mb/s disk usage during patching and about 450 mb/s during the verify files stage. That all check out ok?
Previously before the download ui was updated the process was the same but you did not have a visual representation of what was happening. All you saw was a green horizontal line for updating.
Thanks, Perhaps I just never noticed the disk was still busy after download on my task manager for the last 10+ years. I always played the games right after though, so it seems strange that this process was "secretly" not complete and it still played fine. Also that the next game in line would immediately start downloading after the download part was finished for the first game.
I prefered back when i could do 6+ games in under 10 minutes, and start playing. Now it takes over an hour and it's rough hearing "it's always been like that" as an answer. I guess I'll have to get used to it?
Anyways, thank you guys for replying to what seems like a silly question.
For a developer, there is no win-win when it comes to issuing updates. If they don't patch, then they subject their users to downloading large files. If they patch, now they depend on their users PC to effectively compute the patch. In either case, there will be a subset of their users that want it the other way.
Depends how intensive the patch is. It won't be like copying files. It's a computational process and it's not a linear process.
so you went from: the code must be applied blablaba
to: all games patch this way
at least you learned something, still writing down wrong stuff though.
Developers certainly have the decision whether or not game is meant to patch or update full files. Some games are just not designed to patch, others are more flexible. Some updates just can't be done with patching and in those instances you get a straight install albeit a larger download.
The "2 small files" tell Steam to take code and splice it into all of these files which is done through patching. Your ignorance about how patching works is clearly evident.
I'm pretty sure that 100% of the time people come here gloating about how much time they have spent at a desk with a computer, 100% of them do not, in fact, know how Steam works.
You are not a Valve employee. You do not know how their system works. However, it's demonstrably true, as stated numerous times above, that this has always been how the process DOES work.
I've got a 20TB raid array as a game depot. Most of my games are installed on it. I also utilize a NVME 1.0TB in a PCIE Gen4 slot for the more demanding games that exhibit lag due when installed on the spindles.
I mass edited all of the appmanifest files to turn their update behavior to only update when launched in order to control what games were getting updates, but also to analyze their update behavior. For instance, I uninstalled PUBG because it was clear they update way too often than I'm comfortable with and I'm not really playing the game much to justify getting 1GB+ updates every other day or so.
During that time I was able to see how update behavior differed from game to game and it's clear there is range of choices that developers make from straight downloads of updated files, to patches, to a mix of both. Some games have to download and apply patches in chunks while others go in one shot.
Since then I went through and mass changed the appmanifest files to high priority so that the updates aren't scheduled any more and are applied automatically. I can spend that time doing more productive things like debating random people on Steam forums who spread misinformation behind their supposed epeen computer career, or just play games and whatnot.
I have been here 17+ years ( https://ibb.co/fHg2MwY ) as you have and i can state the patching process has not changed so please do not accuse me of spreading false information.
Secondly understand how patching works, which is the patch been integrated into the game and how a patch integrates into the game IS how the developer set it up, how the game is structured, what they are patching etc and Steam is the tool which has two patching process options for the developer to choose from to do the patching.
As for any other launcher - Cyberpunk 2077 on Galaxy takes forever to patch and it is easier to uninstall and redownload the game rather than patch. Secondly Ghost Recon Breakpoint on Uplay had a restructure with a patch reducing the game size and setting up for future updates to be quicker and just like Cyberpunk 2077 it was easier to uninstall and redownload the game.