Installera Steam
logga in
|
språk
简体中文 (förenklad kinesiska)
繁體中文 (traditionell kinesiska)
日本語 (japanska)
한국어 (koreanska)
ไทย (thailändska)
Български (bulgariska)
Čeština (tjeckiska)
Dansk (danska)
Deutsch (tyska)
English (engelska)
Español - España (Spanska - Spanien)
Español - Latinoamérica (Spanska - Latinamerika)
Ελληνικά (grekiska)
Français (franska)
Italiano (italienska)
Bahasa Indonesia (indonesiska)
Magyar (ungerska)
Nederlands (nederländska)
Norsk (norska)
Polski (polska)
Português (Portugisiska – Portugal)
Português - Brasil (Portugisiska - Brasilien)
Română (rumänska)
Русский (ryska)
Suomi (finska)
Türkçe (turkiska)
Tiếng Việt (vietnamesiska)
Українська (Ukrainska)
Rapportera problem med översättningen
According to the steam stat API, steam servers are mostly normal. However if everyone in your area is using internet, it can cause congestion on the "roads of the internet" so to speak.
General question tho: Are you concerned more about Steam servers / CDNs bandwidth and costs, or more of a general internet infrastructure load, when changing these changes? Because you know, if it is Steam servers / CDNs, you can do throttling and rate control on the server side instead.
Just a suggestion. Otherwise, everyone stay safe out there.
I already have a scheduled download period. It's not without problems…
I often find that scheduled downloads aren't started automatically. (These tend to be ones which I've started then paused and end up apparently queued for a specific time; they also tend to be scheduled for the start of the download period.)
I find it… less than useful that manually-started downloads aren't automatically paused at the end of the scheduled download period. As such, I have to resort to exiting and restarting the Steam client during the download period so that they are automatically resumed and, in case that doesn't help, scheduling a task to cause it to be terminated (“killall -HUP steam”) shortly after the scheduled end of the download period (such that I can tell if automatic pausing happened). More control is needed over automatic pausing – default settings and per-download settings should be sufficient.
Both of these problems are long-standing.
Also, I noticed that typical American assumption that we all use that stupid broken muddle-endian date format showing up in the download scheduling. Either make it locale-dependent or use YYYY-MM-DD globally.
One other problem: when an update occurs while an older version is partially downloaded but the game isn't yet installed and the download is paused at some point and, after the update occurs, is resumed, there is currently a need to intervene manually and move the (old) downloaded files out of the way, uninstall the game, move the files to their final destination then install the game such that Steam will find the “already installed” files, thereby reducing the amount to be downloaded. Without that, the download will be restarted. Now imagine a slowish ADSL connection and a typically large AAA game which wasn't far from being fully downloaded…
It would be nice if these were scheduled in the same way, mainly for reasons related to 'net usage metering.
(Incidentally, I notice that my SteamVR update preference appears not to be forced to the highest priority, “update immediately”. That is a welcome change.)