I am playing from an area where internet connection to MWO drops quite frequently, but only for 1/2 second or so. I keep getting the 'disconnected from the server' message and then a penalty when restarting the application.
Well, all the connection-oriented software I have written in the last 10 years has managed "connection lost" with an automatic reconnect without informing the user.
How about it guys, lets get with it and manage short tem glitches without annoying the poor hapless user!
Terry


Disconnection Penalties
Started by TransitTrucker, Dec 25 2016 11:52 AM
3 replies to this topic
#1
Posted 25 December 2016 - 11:52 AM
#2
Posted 25 December 2016 - 01:31 PM
if you loose the connection you have 2 minutes to reconnect to fht game before you get a penalty.
if you crash to desktop just relaunch the game, select the same Mech and click quick play, you wil launch back into the same game, and provided your Mech has not been destroyed you will be fine
I once had an evening when I could not connect to games but the problem then was something to do with my connection to the Euro server, after figuring that out I started playing US only, the problem had sorted itself out by the next evening
if you crash to desktop just relaunch the game, select the same Mech and click quick play, you wil launch back into the same game, and provided your Mech has not been destroyed you will be fine
I once had an evening when I could not connect to games but the problem then was something to do with my connection to the Euro server, after figuring that out I started playing US only, the problem had sorted itself out by the next evening
#3
Posted 25 December 2016 - 03:38 PM
Hi, I did know this but it isn't always quick and easy to do a game restart and it isn't in the least bit necessary for the user to be handling the problem. The software can and should do this automatically.
I write software that uses a database that is usually remote and often split across remote sites. Consequently, the connections are not always very reliable. When I perform an action that communicates with the remote db I test the connection immediately before the action. If it has gone "bye-byes", I do three reconnection retries with 1 second intervals. If after 3 attempts the connection is not restored I finally let the user know that there is a problem.
The strategy works really well, avoids the user having to do anything and gives the impression that my software is bullet-proof and user-friendly.
Come on MWO software engineers lets do a professional job for the sake of software engineers the world over.
I write software that uses a database that is usually remote and often split across remote sites. Consequently, the connections are not always very reliable. When I perform an action that communicates with the remote db I test the connection immediately before the action. If it has gone "bye-byes", I do three reconnection retries with 1 second intervals. If after 3 attempts the connection is not restored I finally let the user know that there is a problem.
The strategy works really well, avoids the user having to do anything and gives the impression that my software is bullet-proof and user-friendly.
Come on MWO software engineers lets do a professional job for the sake of software engineers the world over.
Edited by TransitTrucker, 25 December 2016 - 03:43 PM.
#4
Posted 26 December 2016 - 02:59 AM
Write to PGI about it via the support emails.
They don't read these threads.
(Also, they are hiring.)
They don't read these threads.
(Also, they are hiring.)
Edited by Koniving, 26 December 2016 - 10:39 AM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users