安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
PING......96ms
DL Speed....... 5.38 Mbps
UL Speed....... 0.43 Mbps
Every single link can cause problems. Wifi is always a 'random' factor as it can appear fine one moment, but if you nuke a pizza upstairs, it will obliterate the connection. Local issues like your router NAT table being overloaded by torrents, or the wifi channels being saturated or having a weak signal can really make troubleshooting things odd.
Then you have issues relating to your ISP which may increasing latency or doign QOS on specific packets such that tehy get LOW priority. Which means that totally awesome ping and bandwidth can still translate to TERRIBLE performance as your 'concrete knee high wall war simulator of the month' traffic gets releated below 'pond scum' and 'spam' for priority on the network.
Then you have issues with what you connect TO. Is it another user who is hosting MW3 on their 300 baud 3COM modem? Is the game's lag compensation doing weird things for high ping users? etc.
As you can see the 'numbers' don't really tell the whole story and may not even be relevant.
From you ISP to your Netwrok Card, Modem or Router. Even Browser's and Software. As Satoru mentioned it can take trouble shooting to determine the cause.
Minimum:
OS:Microsoft® Windows Vista®/XP®/Windows® 7
Processor: 2.3 GHz CPU with SSE2
Memory: 1 GB RAM (XP), 2 GB RAM (Vista®/Windows® 7)
Graphics: 256 MB DirectX® 9.0c shader model 2b compatible GPU
DirectX®: DirectX® 9.0c
Hard Drive: 21 GB free space
the pc setup should be fine
have him pingbomb google for a minute and see what the results are
start -> cmd
ping google.com -t
wait about 1 minute then hit ctrl+c
will get results similar to this
C:\>ping google.com -t
Pinging google.com [74.125.225.64] with 32 bytes of data:
Reply from 74.125.225.64: bytes=32 time=20ms TTL=55
Reply from 74.125.225.64: bytes=32 time=20ms TTL=55
Reply from 74.125.225.64: bytes=32 time=23ms TTL=55
Reply from 74.125.225.64: bytes=32 time=24ms TTL=55
Reply from 74.125.225.64: bytes=32 time=18ms TTL=55
Ping statistics for 74.125.225.64:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 24ms, Average = 21ms
Control-C
^C
if the loss is over 5% there is a problem with the connection