Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
Tartışma Kuralları ve Yönergeleri
Bu iletiyi bildir
Its neither at the end of steam (i guess he means the steam server) nor is broken hardware the reason for this.
Its simply the fact that the steam client chooses to copy a game from one local library to another while patching. In some cases it takes hours or more because of some damaged harddrives or whatever are involved, but in other cases it takes "just" half an hour which is still unacceptable. Because its simply a harddrive destroying (and even more ssd) tool if it copies games with like 40+ GB on another harddrive to integrate a <1GB patch.
The fact that we can remove other libraries and then still normally update the affected game, without it having to copy everything around your computer, does show that its possible to avoid this problematic.
But I would emphasise that the other issue is underlined that it COULD be something like a failing drive causing this to manifest so you can't really blithely pass blame. Just a note of caution.
we other still blaim your setup, this is worse on Laptop, Balance mode and Battery mode, this is know as Full Performance, even other steam user admit , not a problem on Desktop pc , even faster there, as i said i already know laptop is build for power saving consumption, + partions issue and user most know disk issue with certain pc build ways will just reduce its outout, and same can be said with near disk full in storage mode.
this dont ruleout cable issue or disk itself, same goes with SDD cache disk, i and other have said it for years, if buffer is not handle fast enough, then system get bottlenecked.
you can use 2 explanation here , disk to slow or go raid. or reduce wan lines with limiting DL, to know all this require steam user is almost a hardcore skilled pc user from the past.
why will i reduce wanlines, that require 10 or 100g network maybe, and total new local network ( same as old switch with 100mbit that dont belong on a GB router.
im sure most steam healper know all this, that dont ruleout we are not support and can forget or will write all about it.
this is simple use a test pc, and as i said it, bust your own balls, thats part of process of faulty finding. cant say how many times i have get caugh in WTF work on other pc. and then the old replace hardware kick in, its here most steam user fail, they cant or have such possible solutions.
same here then im privat person, but i love that old laptop i have, nail or confirm a issue as 2 pc check.
gl with it.
do note some games devs use full dl of install files and then patch update, this is know as final installer or with patch in the installer, untill they fix a new issue as new final installer/patch.
and it dont help if you have lesseer then 200GB+ ( this will not help if game is 100gb as many newer games is today its soon 500gb free storage space as temporary work space. + on boot disk thats even more.
im sure CF know this even he has been here a long time in pc and so have other helper here, but to write all this to every user as explanation is soon way off,
if you have any issue im sure a hands on pc repair place can nail it, and that has a cost for service, almost cheeper to test with other new disk.
but as always, ask them nicly, do they have a script issue.
do test for network issue
https://www.speedtest.net/
https://packetlosstest.com/
same goes with ipv6 issue somehow effect network, then own ISP dont use it. ( this is your problem then ISP dont and do use it. ) and if when they enable it and you do not.
as you see master all, i know, what if this and that, and FFS dont have a OC pc while testing for stability even that will get you slapped around , then its that if you tell us that, well better be hornest about then lie, then more then you have complain over steam DL, so this is not you alone, other steam user have wrote of this before, and most problem of them is user own pc. they might not admit it, i have only seen 1 post then a steam tech dude confirm a odd global issue with many diffrent steam user, and that is so rare they will confirm it. im not sure steam will do this here, then it work for su many other steam users.
if you can test with bypass own router , this is know as direct connect to wall plug, even that is still your router,its rare but can happend. ( still fall under CPE ) thats mean Customer Premise Equipment (telecommunications provisioning) its so rare this is ISP ownership, but its possible this can happend again, sense they also have all-in-on solution. then contact own ISP.
And happened again today with Elden Ring :P
Still 100GB free on my SSD, the update needs 30gb space and Steam prefers to make the backup of files and download the whole 30gb patch on the HDD... Really, what's the point of having a fast disk to play and to quick patch games if Steam does this things?
As did the last time, i ended up deleting the game and will install it again on the same disk i had it. Maximum absurdity
The update might say 30gb. That's just the download. But what happens is, that 30gb of updates could affect 100gb worth of game files. So it will actually require 130gb of space to do such an update. Understand?
I had an odd issue like this before. Except it kept downloading the updates to my slowest HDD which was like the 4th steam library I had made.
So I stopped all updates and X them all so they are no longer scheduled. Go to Steam settings and clear download cache. Steam will need to restart. But when it does, no updates will trigger cause you X them out so now you have to click them manually. Go back to Steam Settings and Dsiable the steam library folder that doesn't have much space left on that drive. Then once you apply this. Now start your download that you had issues with and should now do the updating on your other drives steam library folder instead of c drive.
No, the update was about 450mb or so. don't remember exactly but it was a small patch. 30GB was the space required to create the files, not the patch itself. So with 100GB i had more than enough space to create the backup and to apply the patch at the SSD.
The whole game is 48GB. So what i was saying is that with Steam making this things, it's for me faster to re-download the 48GB again to my SSD than to let the updater copy those 30GB of files to my HDD, apply the patch there and then move the files back to the original folder at the SSD. It's completely absurd.
Let me explain...
If a game has assets within a large file, let's say the file is 4GB. And I release an update that just updates a few MB worth of the assets within this file, yes it must copy that 4GB file over to a temp folder, download the small update, apply it by injecting the new file contents into that 4GB file. When it's done it gets verified and then copied back over to your game folder. You will then notice that the file time stamp has changed on updated files within said game folder.
Why Steam says it doesn't have enough space to update that game for you, I don't know I'd have to look at the system more in depth to determine that.
Nothing of what you said contradicts what i said lol Yes, i know how updates work and i know that the amount of space needed for a patch depends on how the game packages the assets. For example for Unity it's usually around 60-70% of the total game and for Unreal Engine 4 it's about 90-95% (i mean if the devs don't split the assets and create new pak files for patches instead of applying them to a huge main file, which sadly is what majority does)
Nothing of that is new, and Steam using another drive if the one with the game is nearly full is not new, also, they made it that way years ago. But it's the first time (2 times in about 15 days) that i see this behaviour having enough space for a game to patch in the drive where it's installed and, despite that, using another one. I never experienced that before, and i have another 2 ssd smaller than the one i'm talking about and this never happened before (without apparent logic, having more than enough space to create 3 times the files needed like in this case)
So, in my understanding, or it's a bug or they have lowered the minimum amount of space in a drive that the updater allows in order to work in such drive before looking after any other libraries you have in your system. I cannot think in any other logical situations to explain this. And despite not knowing exactly how it is the code they use for the updater, the basics are there and it cannot work in any other ways:
-It checks the space in the same drive game is installed: if it's enough then applies the patch and returns success.
-if it's not it checks for other libraries in different drives with space and executes the work there (probably on the drive with more space available, it doesn't follows the order of your libraries and neither chooses by default where Steam app is installed, i already have checked that) Then it returns success.
-also if not then returns an error for not having enough space to patch the game and stops the process.
Anyway, they have touched the updater a few times already in the last year-months so who knows but it's doing things i never seen before and that have little apparent logic.
That was in one of my older PC though. The last 2 I made for myself and my wife, we have 3x ssds in the PC and no HDDs. This helps out alot much not cheap to do either. We didn't need any HDDs in our machines cause we have loose files, videos etc all on NAS which has 4x 8TB HDDs inside
That's something i didn't try: to temporarily turn off the hdd library before an update. As for me Steam seems to be respecting the "only update at launch" option i always turn on inmediately after installing any game, i can try what you said and then forcing an update and see how it goes.
Will post here the results, thank you for the suggestion!
Yes, i know that, the games that are queued for update and have that "X" to cancel are the only ones i forgot to change the automatic downloads option for the only at launch. I use to change it as soon as i install any game but sometimes i forgot so it's nice to have those games queued so i can cancel the updates.
At the time it's queued, though, i'm already sleeping so i am not surprised by those queued updates ;)
I never liked automatic updates in any case. I don't see a single reason to have them auto these days: Games that a poor patch can break and don't work afterwards and sometimes it is the last patch so devs leave it like that, unplayable for a good part of the players; Early Access games that suddenly receive a big patch changing so much the type of the game and the premise you bought that you can't recognize it anymore; Unnecessary patches to implement a shiny launcher from a publisher that break the mods you have installed or force you to pass an extra online check to run what you previously could run without it; Bugs, deleted progress, new "features" that you don't like at all, sometimes even completely changing the gameplay...
No, thanks. I prefer to have the option to keep an older version or, at least, to be able to check in advance if the patch has problems (waiting until i read enough comments about it)
Thank you anyway!
Well yes, but i don't want to launch the game before knowing i'm not going to have problems, so i prefer to wait a bit. It depends on the game, ofc (if it's early access, if it has mods, ec) Lots of games to play anyway lol
And unfortunately, very few devs use the Steam beta channel and even less for an older version. Some use it for experimental versions, which is great to avoid patching directly the main version and to let ppl check for unstabilities or gamebreaking bugs. But in general i think it's a shame that even having that tool, so few developers use it and even less "AAA" devs (that probably release in more platforms and doesn't care for specific platform tools like this one)