These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE General Discussion

 
  • Topic is locked indefinitely.
Previous page12
 

Server Disconnect in Mission = Dead Battleship!?

Author
Primary This Rifter
Mutual Fund of the Something
#21 - 2015-08-17 05:19:30 UTC
The netcode should really deal with this sort of thing better. Ideally I'd want it to kill the client as soon as it detects that the connection was lost. Instead you get these scenarios where it just goes unresponsive for 30+ seconds, and you can't even quit from within the client because part of that involves sending the logoff signal to the server and receiving the acknowledgment... which doesn't happen because, again, disconnected.
Rawketsled
Generic Corp Name
#22 - 2015-08-17 05:24:02 UTC
Primary This Rifter wrote:
The netcode should really deal with this sort of thing better. Ideally I'd want it to kill the client as soon as it detects that the connection was lost. Instead you get these scenarios where it just goes unresponsive for 30+ seconds, and you can't even quit from within the client because part of that involves sending the logoff signal to the server and receiving the acknowledgment... which doesn't happen because, again, disconnected.

As a work-around (one that we shouldn't need to do), I believe you can just open Eve again without the launcher and log in.
Kiandoshia
Pator Tech School
Minmatar Republic
#23 - 2015-08-17 05:33:34 UTC
Yeah just open the client again/another client and log in as the character that has had the dc. If the connection is back at that point, it'll throw out the other client.
Previous page12