Ilfar
Manta Ice
1
   |
Posted - 2015.10.21 14:15:17 -
[1] - Quote
I'm from New Zealand, all servers are on another continent, my problems go downhill from there...
I've been on and off from Eve for a while now, and things are depressingly tragic.
This past week I've been running three computers each with their own client and account running. Only one computer at a time will get the Socket Closed error, the other two will continue running. I've gotten this error over a couple of years now, through five different ISPs - Snap, Slingshot, Flip, Vodafone and Spark (Spark has been tested with both landline and mobile broadband). I've also been on six different routers now, I can only give model numbers for two of them now, the others are no longer with us, and one is sealed in box on the roof (don't ask). In all cases the connection has been a wired one. Also in all cases, other games have continued just fine with no connection issues (that weren't related to my flatmate's habit of 'fixing' his youtube buffering by restarting the router).
One thing I'm noticing is that the issue only tends to happen when I'm doing something fairly low intensity - sitting there watching something, and especially while harvesting ice. It's so bad while harvesting that if I sub all seven harvester accounts I actually have trouble keeping them all connected. The flip side to this is that when I'm running around in a frigate gang, or chattering to folk in Minmatar Empire channel, I don't have the problem. BUT it has to be traffic going from me to the server - keeping Recruit channel open to keep traffic coming back to me doesn't seem to cut it. Something along the way seems to killing my connection if I'm not sending enough activity back to the server. (That's supposition, based on the fact I never get Socket Closed errors while I'm actively playing, but do while I'm just sitting and spinning, or reading a book while harvesting - Weber's Safehold series rocks, by the way)
The thing that inevitably pisses me off to the point I unsub AGAIN is that the client is utter balls at figuring out the socket is closed. I can see when a toon falls offline on the other toons, so the server knows the socket is closed, but the client is going to sit there, almost indefinitely, till I do something. The disconnected client looks like it's going, the modules are still cycling with no apparent problems, and it's not till a little after I try to toggle a module, or chat, that the client will realise it has fallen over. If I don't notice a disconnect warning on another toon, I don't know that anything has gone wrong... Case in point, the alt fell over about four minutes ago, and he's still sitting there, cycling his fleet boosting mods, and thinking he's okay. He only just fell offline now, five minutes and a bit since the main window popped up the disconnect notification.
So yeah... My preferred thing to do - resource gathering and markety type stuff - seems to be the exact thing that causes my Socket Closed errors. |