Steam installieren
Anmelden
|
Sprache
简体中文 (Vereinfachtes Chinesisch)
繁體中文 (Traditionelles Chinesisch)
日本語 (Japanisch)
한국어 (Koreanisch)
ไทย (Thai)
Български (Bulgarisch)
Čeština (Tschechisch)
Dansk (Dänisch)
English (Englisch)
Español – España (Spanisch – Spanien)
Español – Latinoamérica (Lateinamerikanisches Spanisch)
Ελληνικά (Griechisch)
Français (Französisch)
Italiano (Italienisch)
Bahasa Indonesia (Indonesisch)
Magyar (Ungarisch)
Nederlands (Niederländisch)
Norsk (Norwegisch)
Polski (Polnisch)
Português – Portugal (Portugiesisch – Portugal)
Português – Brasil (Portugiesisch – Brasilien)
Română (Rumänisch)
Русский (Russisch)
Suomi (Finnisch)
Svenska (Schwedisch)
Türkçe (Türkisch)
Tiếng Việt (Vietnamesisch)
Українська (Ukrainisch)
Ein Übersetzungsproblem melden
And herein lies the problem. That should be the choice of the user, as it is for other titles. You are free to decide to do that, but if it takes someone's system longer to verify 13 GB (not because there is a fault in their hardware, but just because it's slower), they shouldn't be forced to sit through such a process for every 50 MB patch. For example, my copy of Train Simulator, for which I have something like 80 GB of DLC, just updated itself in about 60 seconds (260 MB download, 2.3 GB patching). This is how updates can be efficiently handled. And if I wanted to then verify 80 GB of Train Simulator files after that, the choice should indeed be mine (of course, I wouldn't unless I noticed problems after the update, for exactly the reason that it takes time for nothing), which it is for all my other titles except ETS2/ATS.
No. If someone's patching takes longer than your own, sure it's because they have an HDD and you have an SSD, but if it just 'takes a while' period, that can be simply down to how the patch is being handled. A good way to know would be to see whether it's systemic or the problem only exists for one piece of software. Fortunately Steam users can compare patching between the different games they have to notice if one is slower than all the others, which is the case here. And as I said above, if this patching 'takes a while' because it forces a game file verification after each one, then that's not down to a user's hardware, it's how the patching is done. Again, if other games on Steam can install larger patches in a fraction of the time -- I'll reiterate, a 260 MB train simulator patch completing in about 60 seconds on my system, while these 50 MB ETS2 downloads are taking several minutes -- then the problem simply does not lie with a user's hardware, it's how the patch is implemented.
This misses the point, as it implies users having these issues with only ETS2/ATS are not accepting of games in general being continuously updated.
Current spinning hard drives suffer a lot if there's even slight amount of defragmentation. This is due tech used how data writings are done to platters.
At that point drive performance drops completely and it starts to live it's own life (usage 100% read / write speeds vary between from 0 to something.
Fact of the matter is ETS2 and ATS used to take a very brief amount of time to update (to the point where disk activity stops again), even when the update size was into 3 figures...
Now it takes 10-20 minutes to do a 50mb patch, because it wants to verify the whole install with every bloody update!
WHY CANT IT JUST VERIFY THE BITS IT CHANGED like every other game does???
And because every other game doesnt take this long to patch, it stands to reason that it has NAFF ALL to do with Valve's methods anyway - it is something SCS have changed - and its a change for the worse IMO
Yeah, not changed anything for me either. The info is presented differently for sure but it says how much the patch download is i.e my patch today was 75mb.
Look closely next patch and you will see.
https://steamcommunity.com/sharedfiles/filedetails/?id=2691489581
Assuming that you have done due diligence with Promods, so start a new thread and after a crash event, link your game.log file after you upload it to Pastebin.com - provide the pastbin link for your text and someone can assist you.
Perhaps I need enlightening about why a properly tested new version should require updating on an almost daily basis, often with a new version number. (I shouldn't say it but I will. Sloppy QA/QC.)
The cause of a CTD would probably show up in game.log, if you'd like help with that
Only game daily updates were last week - Krone trailer update, then DAF XF update. You may have also had mod updates on a daily basis.
It is odd that tens of thousands of users have no problems, but a literal handful of folk have issues.
This thread was about the number of updates and their 12GB size (which isn't even a thing)
For a good moan, start your own thread. For actual assistance, again start your own thread.
Happy holidays.
__
Hello,
The Steam platform uses a binary patching system - this means that only changed parts of the file are replaced.
For example the changes in this update are about 140 megabytes spread across various files.
In such case the Steam client download the 140 megabytes of changes and then applies the changed data across all game files (12 GB).
This process may be compared to when you make a mistake in a line of text, you correct only one incorrect letter instead of deleting the sentence and writing if from the start again.
Let us know if you have any further issues.
Best regards,
SCS Software Tech Support