Lag must stop

Tch...

try only one team spawning in HoH...
I couldn't take screen shot becuz there wasn't even an elapsed time... just free fame and sigils...

I don't lag much in my campus; internet is lightning fast. But I only get those lag spikes randomly. My character just stops moving along with everybody else; I teleport all over the map, and zooms back to my *proper* place (common lag everybody gets). But that random lag can cost a big GvG match; it doesn't take much to piss us off eh?

Backread sir (which is one reason people are happy to flame you) :

If I knew how to do this personally I would - but I do not, glad someone else did tho.

I deserve the flame for not backreading... granted and noted.... Here's what we can learn from that trace route... I will follow this all with an explaination of how you can do this yourself.

Once the route breaks into the Scottsdale Arizona area of the chain (lga.llnw.net) ping times of 248, 177 etc. start to show up... This is not the end of the world, but for someone who started out with low ping times it's WAY too high and indicates a scenario where I would not be suprised at all to see some level of packet loss... simply from the evident fluctuation.

Someone might read the bottom where requests are timing out and make the assumption that this is where packets are being lost but this is likely not the case. The router that the packet is travelling through in a traceroute must respond to ICMP ping requests, and what is happening here is that your hitting a router which does not want to respond to you. Here is an example of a traceroute that I did from my PC to the same server... Note the fairly consistant ping times...

1 <1 ms <1 ms <1 ms [CENSORED]

2 * * * Request timed out.

3 19 ms 18 ms 15 ms [CENSORED]

4 12 ms 14 ms 9 ms [CENSORED]

5 7 ms 13 ms 14 ms 68.86.103.146

6 14 ms 9 ms 21 ms 12.125.159.89

7 38 ms 53 ms 31 ms tbr1-p013704.dvmco.ip.att.net [12.123.207.146]

8 38 ms 32 ms 55 ms tbr2-cl31.sffca.ip.att.net [12.122.12.133]

9 47 ms 40 ms 41 ms ggr2-p3120.sffca.ip.att.net [12.123.12.22]

10 40 ms 39 ms 34 ms att-gw.ashburn.eli.net [192.205.32.74]

11 44 ms 43 ms 45 ms 0.so-2-0-0.XL2.SCL2.ALTER.NET [152.63.57.102]

12 49 ms 43 ms 51 ms 0.so-6-0-0.XL2.LAX1.ALTER.NET [152.63.57.81]

13 52 ms 51 ms 50 ms POS7-0.GW4.LAX1.ALTER.NET [152.63.53.61]

14 * * * Request timed out.

Never higher than 52ms.... This is MUCH better than high fluctuation with 248 pings in there....

At any rate. To do this from your machine, just drop to dos by clicking start, run then typing cmd

Then from the dos prompt type tracert followed by the IP address you want to trace to.

If you want to share this data with us, follow this command with a >c:\traceresults.txt which will create a text file of the same name you can cut and paste into this forum:

i.e.-- c:\>tracert 192.168.168.168 >c:\traceresults.txt

Thank you! Most helpful. However I will wait till my husband gets home before trying this (that way if I screw something up I can blame it on him >_>).

Tried to beat Eternal Grove last night and twice right when i beat it, i lagged out!!! I'm getting angry with this lag-issues. It used to be no lags at all when i played online. Maybe A-Net need another server restart or change something to stop this lag issues?

Seriously... Try tracert when you're lagged out to see if there is a problem... Also run: "C:\Program Files\Guild Wars\Gw.exe" -diag
This will help you determine if there are connection issues.

The issue started this week, but i'll try and see if i can pin-point the problem. Thanks for the tip Burn Butt.

Ok; I'd like to figure this stuff out too. I have been complaining of lag for a while as well - and I'm willing to admit some might be on my end; though I have defragged my gw.dat (from 123 frags to 1; I do it from time to time), have a relative fast machine with a fair bit of RAM (1.5 gig IIRC, ~3 gHz AMD64) and lots of disk space (80 gigs free on the 120 gig drive with GW on it). I know that my cable line isn't perfect, and had the cable guys in to check it out; they replaced some wire, put in a new splitter (apparently my old signal splitter might have been an issue) and so on.

Overall performance has improved - but I still get lag.

When I lag it is coincidental with everyone else.
Last night I started rubberbanding in a GvG. The whole team was rubberbanding, unable to get down a staircase (we had just started the match, heading to the front of the base).

So - is it possible that it is on someone's home end? Can a person's connection do that, and affect all the other players?

Later that match we lost a player to an error 7, costing us the game most likely.

Again more lag over the night, lost a monk during VoD, about 33 minutes into a match. Lost the game because of it. Again, all players on our team experienced lag.

So - where can the problem be for this? Can it be server end? Yes, certainly. Can it be in between? Yup. Can it be at someone's house? That I don't know. If anyone can tell me whether that can explain it it would be nice.

As for myself, I want to do this traceroute thing, but I see that 2 different IPs were listed here to check - how do I determine what to check? Can I have it set up, and when it starts getting wonky do an alt-tab and hit traceroute? I'd like to get to the bottom of this, as it is rare that we'll go through a night of GvG without a player disappearing. One night I believe every match we played had an error 7 on one end or the other (sometimes enemy teams were suffering).

So is c:\>tracert 192.168.168.168 >c:\traceresults.txt this the command then? The other trace route is to another IP it seems.

In our Urgoz group we just had 5X similtaneous Err 7's from multiple parts of the world within 1 min of the event starting..

Seems Unlikely to be coincidence.

I've done a traceroute. PlayNC Support asked me to use Ping Plotter, which you can run multiple times. But they didnt see anything wrong >.>.

Of cource, since the lag happens to everyone at the same time, even people in seperate groups in diffrent towns, so its not going to show up all the time I would think.

Thankyou God for Servants of Fortuna, and thankyou expecially Heist23 for pointing it out - the Sysinternals Defrag tool mentioned above worked like a charm. 200 Fragments per file down to 1, and the Lag has vanished! I've played for three hours now without any lag or disconnects, which is a minor miracle lately, given that I was disconnecting every half hour or so before. THANKYOU!!!!

If you missed Heist23's post, I'll copy the link the he provided (hope you don't mind)
http://forum.sof-guild.com/showthread.php?t=5100

192.168.168.168 is a bogus IP address. I just used it as an example. Instead of that, try running:

"C:\Program Files\Guild Wars\Gw.exe" -diag

Look in there, when it tests it's connection. Try tracert to those.

Yes, my ping goes high up after crossing the atlantic. GW is surprisingly playable even at that high response time (ok, trying to interupt with mesmer is problematic).
I play on US servers since the european summer of lag. This whole situation is a deja vu for me. In summer 2005 many people on the european server cluster experienced lag spikes and mass err7s. At first Anet denied any problems, but after the complaining crowd grew bigger they admitted problems with a provider closer to their side and they finally fixed the problem. (Too late for me, i had already switched realms and met some nice people i still play with.)

The current problem concerns players from different locations and in different instances of the game.

So this doesn't look horrible, but it jumps going to "Frankfurt", and before that on a rogers jump.

Tracing route to 206-127-145-228.plaync.com [206.127.145.228]

over a maximum of 30 hops:



1 * * * Request timed out.

2 6 ms 5 ms 6 ms
3 7 ms 7 ms 5 ms
4 10 ms 11 ms 9 ms
5 51 ms 51 ms 51 ms igw01.chfdrl.phub.net.cable.rogers.com [66.185.81.1]

6 51 ms 51 ms 51 ms if-4-0.core2.CQW-Chicago.teleglobe.net [216.6.16.1]

7 52 ms 51 ms 52 ms if-7-0.core1.CT8-Chicago.teleglobe.net [66.110.27.77]

8 57 ms 55 ms 55 ms so-1-2-0.e1.Chicago1.Level3.net [65.59.88.193]

9 57 ms 58 ms 57 ms ae-2-54.bbr2.Chicago1.Level3.net [4.68.101.97]

10 142 ms 144 ms 143 ms as-2-0.bbr2.Frankfurt1.Level3.net [4.68.128.169]

11 138 ms 138 ms 137 ms ge-11-1.ipcolo1.Frankfurt1.Level3.net [4.68.118.105]

12 147 ms 139 ms 139 ms 62.67.38.74

13 139 ms 141 ms 140 ms 206-127-156-82.plaync.com [206.127.156.82]

14 139 ms 137 ms 139 ms 206-127-145-228.plaync.com [206.127.145.228]



Trace complete.

I'll try doing one when I'm err=7, to compare. Does this look reasonable to you?

Totally forgot about this flag...addendum to my traceroute:

11 tge2-3.fr3.lax.llnw.net [69.28.171.117]
12 ncsoft.ge5-11.br01.lax05.pccwbtn.net [63.218.73.2]
13 216-107-255-70.plaync.com [216.107.255.70]
14 216-107-246-36.plaync.com [216.107.246.36]

Apparently hop 12 isn't responding to icmp packets (thus my traceroute timeouts from there on), but now i know i don't have any problems until i reach NCSoft's area of responsibility...
(apart from having a ping of 180ms on us compared to 20ms for the euro severs *sniff*)

no more lag?


hey, no lag, rubberbanding, err 7's or other issues tonight =)
perhaps something was finally fixed somewhere along the way to anet

just for the record, i made no changes to anything on my computer, local network or otherwise. just loaded up the game, logged in and played while the game updates downloaded in the background.


after a full week of multiple err 7's per night, i'm glad something finally seems back to normal

damn.. i spoke too soon apparently

yet another err 7

its the double fame event
so many people trying to go on, prob jus the servers being overloaded
i remember something like this happened at the double faction event
half of everyone was complaining about lag, just like now
crazy because on the double faction event i was lagging like crazy like everyone else, but on this double fame event im not lagging at all

I just want the reconnects/no error=7.

That does look very reasonable... Even good. What to watch for isn't even high numbers (but they don't help). Look for mass fluctuation up and down with lots of high numbers.. That would indicate a bad route.