does setting MTU to, say, 1453 allows you to play? with more lag, but stil being in game?
I can play with lower MTU values. If it gets laggy, i can just reduce the graphics resolution a bit and it’s good (not that I want to play like that all the time).
The timeout error we discuss here still happens with the same average frequency.
But I found something interesting:
My router (O2 / Telefónica 6431) always sets the MTU size to 1492 (the default for PPPoE), no matter what MTU I set up in my Mac in OSx.
That explains why the game.log always shows the client MTU size as 1492 which is indeed correct.
It is not possible to change that value on the router (not configurable)
The ideal MTU for me is 1472, as that is the most I can get from the game-server over my connection, as my previously posted console log shows .
So when I set my MTU to that value, your server should never get a package lager than 1472.
Your server might send one as large as 1492, but that would get split on my Mac without causing a problem on the server.
Conclusion: 1472 is the optimum MTU for this connection, a higher MTU on the router is not a problem.
I suspect the real problem is something else:
According to the game.log, it can successfully connect to the proper game-server for the chosen environment and game-type during triangulation.
But then (still turing Triangulation according to the log), during the setting up of the session (Initialisation), a timeout error occurs.
I have no indication to believe the timeout occurs in the network (my ISP or my Mac), but that a threshold in the game is exceeded during the initialisation on the game-server during triangulation that is incorrectly attributed to the connection.
I also looked at the RakNet API and noticed that a variety of API-calls have timeout threshold parameter on them.
This could also result in an false time-out message, without a real timeout happening on the network.
I had a continuous ping 5.153.37.199 running the entire time in a second window, and no real timeout occurred.
And, as mentioned in my original post, the ‘re-connect to battle’ never works despite the functioning connection as per the ping.
sgdmity, I would certainly appreciate if you could look into that.
Thanks as always and best regards
…was going to add something but just saw I can still edit the post, never mind…
I finished editing.
Thanks for your great efforts in investigating this, but our devs say this is a known ‘bug-or-feature’ of raknet and maybe someday they’ll do something with it.
But for now it is a known issue, and the workaround is to tune the MTU.
I don’t see the ‘feature’ aspect of this bug, but certainly appreciate your honest feedback.
Just keep in mind the RakNet sources are on GitHub now, so if you ever feel like fixing it before they do, I am sure that all your customers having this problem will be very thankful for am improved gaming experience.
Other than that I thank your for your great and patient support.
Love the Game.
Best regards
PS: Maybe your devs could try to get the re-connect dialog to work. That part might be in your code…
The error now happens much more frequently, more MTU-fiddling doesn’t make a difference.
It has gotten to the point where it’s taking the fun out of the game…