Massive Lag pt. 2

bradrap

Senior Member
Joined
Nov 16, 2005
Messages
852
Reaction score
3
I'd like to find out what other peoples experiences have been like in the last 2 weeks in 25 mans. Personally I haven't been able to raid any of the new instance in heroic and only a handful of bosses in Ulduar 25 allow me to stay online during the entire fight.

I use a SAIX/IS based account aswell as Web Africa Verizon prepaid but they all yield the same ****ty results.
 
Well I have an interresting problem I just cant seem to nail down.

I had massive DC problems a while back but managed to stabilize it.
As it is now, I ONLY chain DC on the Beasts of Northrend section of the Collosseum. As soon as the beasts are dead, I am fine.
Disabling combat log, tunneling / proxying / straight direct traffic / different network providers nothing stops it.

Looks like a bad memory leak getting worse and worse till I DC... then I can forget about it, I log in, servers kicks me... I have to wait for the encounter to be finished. Only once that Jarraxxas dude comes into the arena is it fine.

No other instances, bosses, AOE bombardment kicks me off. Only that one encounter.
 
Bradrap, I am having the same problems, we could do 25-man at the same time on a 512mb, unshaped line with Webafrica, but now we can barely do wintergrasp or any 10-25 mans at the same time, we are on Verizon now and seems a bit bitter but still can not do 10 or 25 man at the same time or be at Drek in AV at the same time....I do not know what went wrong where...
 
Well I have an interresting problem I just cant seem to nail down.

I had massive DC problems a while back but managed to stabilize it.
As it is now, I ONLY chain DC on the Beasts of Northrend section of the Collosseum. As soon as the beasts are dead, I am fine.
Disabling combat log, tunneling / proxying / straight direct traffic / different network providers nothing stops it.

Looks like a bad memory leak getting worse and worse till I DC... then I can forget about it, I log in, servers kicks me... I have to wait for the encounter to be finished. Only once that Jarraxxas dude comes into the arena is it fine.

No other instances, bosses, AOE bombardment kicks me off. Only that one encounter.

I doubt it is a memory leak, else it would not be a isolated incident a lot of people would have the same issue. I for one never have any dc's in that fight at all, had 1 in ulduar last night, that was about it.
 
Yea I dont think its a memory leak either, I just described it in the manner it happens... it gets slower and slower till it kicks me off.

Been reading up, there are lots of people experiencing this... specifically only on that fight until Icehowl is dead. Was also mentioned on EJ forums.
 
I was able to do a 5 man heroic with a lot of lag (2k + latency). Dalaran was almost impossible and dc'ed me several times. Went to OS25 and was ok untill the first pull, then again I dc and couldnt get back to the raid.
 
What is the ideal line for 2 ppl to play on? I'm sitting on 512mb unshaped, webafrica as ISP
 
I had massive DC problems a while back but managed to stabilize it.
As it is now, I ONLY chain DC on the Beasts of Northrend section of the Collosseum. As soon as the beasts are dead, I am fine.
Disabling combat log, tunneling / proxying / straight direct traffic / different network providers nothing stops it.

This ^^

Since last night though I've also started to experience massive lag spikes in 5 mans . Sometimes it's fine, and then after a couple of minutes it's horrible.

Did Crusader Colliseum 10 man last night - dc'ed on Beasts of Northrend again (surprise surprise), was able to rejoin before Icehowl spawned, and after that it was little less spiky. Then afterwards I went with a 5 man grp to UK and the lag spikes started again halfway into the instance.

I use WEBAfrica unshaped 384 kb Verizon currently. SAIX is a no-go zone to me.

25 Man raiding was a pleasure before Wednesday. Did the patch change something? I read elsewhere that Verizon / SAIX experienced a problem on Wednesday? Surely that should have been fixed by now...
 
Top
Sign up to the MyBroadband newsletter
X