Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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