安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
https://support.frontier.co.uk/kb/faq.php?id=265
Solved pretty much all of my connection problems (well appart when there's actual server problems of course)
I don't have an answer re: if it's normal or what the fix would be - my assumption is that it's a bug with the newest update.
Neat - although I have no intention of messing with my network settings just to get this feature to work properly.
It's pretty harmless though, you can always set it back to default, I have a couple of batch files to switch between the 2 configs in an instant
Aye, unless someone somewhere uses a different game/service where the MTU matters there as well.
Regardless, the "comms" error isn't critical for me at all. Hopefully they'll come out with a patch/update that's not reliant on a static MTU requirement.
@OP - let us know if you try the workaround supplied by Frontier and find it to be working better for you. o7