安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
There are certain things that can, in theory, throttle your downloads if you're on a relatively fast connection, and those are the things worth giving attention instead.
Servers in the US should be void of congestion enough if I try it at somewhere around 4 in the morning though, right? Thinking I could look at the current overall US server usage before I run the tests too. I believe I saw Steam has graphs for this. I'd still like to see the ms difference between, say, Dallas and Washington (or wherever).
I've done searches to check the boxes on anything else that might my connection, unless you'd be willing to provide a list I can try? It's not horrible right now, just thinking it's not optimized to the best it can be. Perhaps someone else could use this info too, ya never know.
For the most part, the issue will be your ISP's routing to those servers.
The internet is like a bunch of streets, interconnected at what we like to call nodes.
A ton of nodes can be flop, and we're not going to forget local DNS problems.
If you were to do a ping / trace-route to any Steam server (through some method), the packets will take a certain route, and again, the results may not be as fancy as you'd expect.