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
Also possibly a factor, before the download UI update the UI didn't actually show the size of the file I/O work it was doing, just the size of the download, so patching stuff was still being done, it was just a bit less visible than it is now.
The recent change to the download page only changed how information is displayed.
It's way more transparent now what is happening.
So, no. Downloads did not get slower, or patching. Some games just have very inefficient file structures.
Patching has been around far longer than the download UI update.
Your downloads and patching speeds are limited by
1) your cpu
2) your disk IO
3) your anti-virus killing disk IO
That's the main culprit. Most recent games (I can think of Cyberpunk right off the bat) consider that with the size of our HDD/SSD having large files is OK. Except that patching 10 files that are 4GB each is less efficient than a hundred of files that are 500MB. If you only need to update a few files, on one side you can end updating 2 dozens of GB and on the other side maybe less than 1GB total.
And there does seem to be some new behaviour recently, I saw this in the Steam content_log.txt earlier:
I've never seen this "switching to update single file mode" bit before, and I do tend to keep an eye on this sort of stuff. In this case, I looked at the logs specifically because Steam did something weird of spending a long time patching before it attempted to download anything. I'd not seen that exact thing before either.
EDIT: Did some additional research, the "single file mode" was mentioned by Valve to a dev on Total War by at latest April 2019: https://www.reddit.com/r/totalwar/comments/be88f9/comment/el3qxxw/
So, not new, exactly. I guess I've not been trying to install updates on a nearly full drive before. Anyways: it does show that Steam's download behaviour is very much not immutable over time.
I've got Ryzen 5900x 12-core processor so cpu should be fine, the HDD definitely will slow it down as maximum speed I saw it perform was about 40mb/s or something, still. I don't have an anti virus software :) They tend to interfere with so many multiplayer games etc I stopped using it, I depend on Defender to sort of take care of most things and I'm staying away from anything dodgy out there.
Still I'm not blaming Steam or the new UI in why I posted this discussion at first, all I wanted to know if there are anyone else who's noticed this. When we had old UI it seemed to download update however big it was and patch it if not instantly then much quicker than now. I remember it having ''patching'' phase but it definitely didn't take too long.
E.G.
Game called Icarus had a little update of 60mb, but it was patching for over half an hour over 48GB, makes little sense this unless this is some sort of Forced ''reverify'' game command? Not sure.
Anyway, thanks to everyone who responded, I normally just suck it up and don't dwelve into asking the crowd on opinions since they are mostly quite colourful ^^
This is not entirely accurate. Ive not changed my hardware in 3 years and i dont run AV on my gaming rig. The only thing that has changed, is the steam platform.
And this is patching vs. downloading has been occuring on more and more games in the past week. This is most certainly a change done on Valve's side in order to attempt to provide a more efficient download process, but ultimately increases the patch time for any game signficantly.