Or'Ipahs
Amarr Ministry of War
|
Posted - 2010.08.06 04:37:00 -
[1]
Sup, so I'm at the end of my tether here, tried everything...
Opened up the in-game monitor (SHIFT+CTRL+ALT+M) to see if I could make heads or tails of exactly when and what I have been doing when the socket closes in real time by checking the network tab's packet status. I've tried to heavily load my outgoing packets by means of inputting commands repeatedly e.t.c. and I can generally fly around and warp about a system hassle free with a great deal of response from my ship.
Trying to put some strain on incoming by opening up multiple player info windows, for example, didn't seem to kill EvE, nor has recalling my assets repeatedly, playing EvE whilst streaming video or going to a heavily populated area and trying to bump/lock-on-to/leg-hump everything in scene to try and break my connection, and a mixture of these methods.
I have read in many posts that idling seems to be the cause of some peoples problems and idling certainly is a reproducible way of causing the socket error. Open the monitor, spam the hell out of the left mouse button on empty space, watch outgoing rise (even just go about some sorta daily business), then leave to idle for 1min so the display shows no outgoing, after that it seems (at least in my case) the socket closes, this works especially well in stations.
Stations are a no go, incoming gets all erratic inside, but docking and un-docking aren't too much of a problem I think.
Session change is fairly random, but definitely a cause of this error for me.
Using windows network monitor also, I haven't noticed anything out of the ordinary, and my connection is not straining hard to keep up, without a shadow of a doubt...
I seem to remember a patch, not sure which or when sadly, that seemed to slow me down a lil, I thought it may have just been my comp not handling EvE so well, but...
...At first the market seemed to get very-very sluggish, and I mean so slow it was going backwards, and not too long afterwards I began getting the socket closed error nearly every time I used the market (never seen it before), and with rapidly increasing frequency. I had to get my fellow CORP members to purchase my items for me and the contract them over for all the trouble it was giving me at the time. That was the most reproducible step I can remember, and it seemed to bleed into the rest of the game thereafter for me over time.
Does anyone else remember a particular game mechanic other than session changes/undocking/docking which broke EvE, and seemed isolated at first? I vividly recall the market being an issue
I have tried over and over again to break my connection, within reason, but EvE just stops replying of it's own volition, surely idling in deadspace with say as few as about 25 objects in the area, looking at the nebulae and the purty lens flare from the system's star isn't nearly a strain on network resources, but it is, EvE simply seems to forget that you're there.
All my pinging efforts to TQ using command prompt are returned swiftly with no losses, well, apart from being at a loss myself...
I know it's a shot in the dark, but could this be caused by some line of code say, which is for a game mechanic unrelated to that of jumping and docking/undocking or connection protocol causing unexpected side effects?
It's been too long, I'd like to shoot down some stuff and things, an get back in touch with the corp, who will also back me up that my connection was fine until said market-death.
My eyes and temples are bleeding from repeatedly self-face-planting-keyboard, whilst screaming, "ZOMGZOMGZOMGZOMGFIXITALREADY!!!!", and I'm not-a-supposed to get keyboard in my eyes, it has adverse effects.
Still trying... and...
YES THERE IS SOMETHING WRONG WITH YOUR BLOODY PLANCK BUBBLE STABILIZER!
|