| Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Inceptor
   |
Posted - 2010.12.04 12:06:00 -
[1]
http://www.eveonline.com/ingameboard.asp?a=topic&threadID=1424091
Same issue, basically.
Further info (another topic):
Edited by: Inceptor on 02/12/2010 14:37:00
My consistent 'grind to a halt' issue is persisting. Everything was running fine for a while this afternoon. It happened this time last night too. Modules slowly stop reacting on time, target locks dont happen then all at once I have locked a bunch of targets, jerky movement onscreen - it looks as if I am losing packets. Any ideas as to how I could further diagnose my connection to the eve server, packet loss wise?
At the moment eve wont even allow me to get ingame, after choosing 'enter game', it hangs on the 'character selection' screen - 'entering game as XXXXXXXXX'
Edit: just got the 'soul crushing lag' message -
'Your client has waited 5 minutes for a remote call to complete.
This could mean that the server is very loaded.
Please be patient, chances are that the call will complete eventually but depending on the load it might be considerable time.
Click here to see the remote call debug viewer'
I open the remote call debug viewer to find a lot of 'outstanding'. I am guessing this is me trying to punch a message through to the server and it not getting there.
Anyone able to help me read this little window, and get an idea what im looking at? |
Inceptor
|
Posted - 2010.12.04 12:21:00 -
[2]
Edited by: Inceptor on 04/12/2010 12:23:43
 Originally by: Infinity Ziona
I'm having the same problem. I get slow loading times now, my client freezes up and then disconnects.
Bit of an annoyance since I just started a war.
Pingplotter shows if-1-3.tcore2.NJY-Newark.as6453.net giving me a constant 10-11% packetloss.
Just started playing with pingplotter too, nifty little program. I'm also getting 10-15% PL on the same node.
edit: for those of you wishing to try;
http://www.pingplotter.com/download.html
87.237.38.200 is the IP to trace (eve server)
# of times to trace to: 1500
Trace interval: 2.5seconds
Samples to include: 1500
If everyone is having the exact same PL on the same node, then maybe we can begin to narrow things down?
|
Inceptor
|
Posted - 2010.12.04 12:38:00 -
[3]
easy way to find out. pingplot to the eve server. if you plot to that node / ip, according to whois that node lives in montreal.
|
Inceptor
|
Posted - 2010.12.04 15:28:00 -
[4]
Melbourne too.
I'm gonna throw an ISP out there - optus.
|
Inceptor
|
Posted - 2010.12.05 02:39:00 -
[5]
no PL at server end either.
Beginning to see a pattern - swedes and aussies with similar ISPs only having this issue since the latest patch, and that everything we have all collectively tried has not fixed anything.
I'm at a bit of a loss - and as for kapersky etc - I dont use it. So its not AV related. The only thing common between us is location (somewhat), ISP (somewhat), and a new patch (everyone). The previous two COULD be coincidence.
Clutching at straws now. Anyone got any further ideas? This ruins my gametime and I really need it fixed.
|
Inceptor
|
Posted - 2010.12.05 12:53:00 -
[6]
yep this is still occurring for me. Would really appreciate some CCP feedback here.
Even if it was just to tell us what we should all be looking for, or doing.
Theres no use ringing optus and saying 'Hey I play this game... and since their last patch I get really choppy gameplay and random disconnects, its a possible packetloss issue but I dont know'. Theyll ask if I have my computer plugged in and turned on. Then theyll tell me its not their problem.
Beyond a joke now. Simply cannot play eve.
|
Inceptor
|
Posted - 2010.12.08 11:20:00 -
[7]
I've stopped playing altogether these past four or five days, its simply unplayable. Will let my subscription lapse if its not fixed in another week... kinda rediculous really.
|
Inceptor
|
Posted - 2011.01.05 10:49:00 -
[8]
confirming issue still exists for australian optus users.
Seriously, its been how long now? I REALLY thought that once I came back from holidays (christmas and new years) that this would be fixed by now.
This is revolting.
Fix it.
Yesterday.
|
| |
|