Wipe wrote on Sep 5^th, 2014 at 8:44am:

You ... didn't have to reply. But you did. And now you look like a fuckwit.

To distill Flav: You had lag. Odds are that it was neither your machine, nor Turbine's.

DropBear wrote on Sep 5^th, 2014 at 10:06am:


Devs who made Gravity and RGL room REALLLLLLLLY believed there is no LAG at all and everyone has <100ms  and 0% packet loss all the time.

I hope that when they die they'll be send to their personal hell where all they do is to be forced to pass these Puzzle rooms over and over and over and over while failing them at 99% due to LAG and re-spawn at the beginning.

FuckThisShit wrote on Sep 5^th, 2014 at 11:25am:

Alex DeLarge wrote on Sep 5^th, 2014 at 10:27am:

i'd put them in tiles (on a previous version of heroic elite), no teamspeak or whatever, only voice and partychat, while the rest of the hell are waiting impatiently for them

DropBear wrote on Sep 5^th, 2014 at 10:06am:



Ok, I'm going to put fuel on the fire here... Change computer...

you know that my 8+ year old beast died recently... the Super Mario Room was a nightmare for me, It was frustrating ( for me and others ) and in the end most of the time I ended up suing the Bag Lift trick ( thankes for the Guild about that )...

First time in Super Mario Room with the Jump Impaired Cleric on the new computer... ( the specs are in the relevant thread where it belongs )... Lo Behold, I went through the room with the rest of the pack... I was the first surprised... I have yet to reproduce the thing ( On Call this week, not even trying to raid... it's like asking Murphy to show up ), but just how easy it was tells me that the issue was my decrepit dinosaur of a computer and not my lack of skill at Super Mario.

I just got hit with 3 second latency in the end fight of WGU when soloing. That was... unfun. Didn't trace route, I was too busy trying not to die

Wipe wrote on Sep 5^th, 2014 at 2:46pm:

There is lag.

Flav said it. I've said it. Just about everyone here has said it.

Flav described where the lag comes from, and then you herpaderped at him.

Anger makes you stupid.

Flav wrote on Sep 5^th, 2014 at 2:41pm:


Is it easier for Turdbine to do some testing off site, or for all of its customers to get Fibre connections?
I just think they need to either do some testing from home, or get the PC/Lammania players to provide feedback on lag or potential lag issues.
Lag is a broad term, maybe they just need to be aware of latency issues and the impact this can have when it is beyond their control, because players will hold them accountable for perceived lag.

Oh. Also. There is no lag. You need to reset your router. Turn off your AV. And pull your cheeks apart. But there is no lag.

Flav wrote on Sep 8^th, 2014 at 3:39am:


Losing 150-170ms crossing the Pacific - taking the scenic route.
Leaves my island and goes via Hong Kong, bounces around HK for a bit, then visits Taiwan (where it joins the cogent network) and then it next pops up in Wichita Kansas some time later?  Kansas - WTF?  Do they even have internet there??  (just jokes for those Kansas folks).

Flav wrote on Sep 8^th, 2014 at 3:39am:


Fully appreciate that point.

But as you pointed out, they potentially have a weak spot in their trunk access that they cannot mitigate, they could perhaps take measures to compensate for latency issues.  Auto-detect features that modify certain settings....

I do realise the vast majority of their customers are US, so they're not going to design content for 100ms+ latency, but it would appear that many US customers are also being adversely affected by those trunk access issues you highlighted.

DropBear wrote on Sep 8^th, 2014 at 4:32am:


As Wichita falls, so falls Wichita Falls

DropBear wrote on Sep 8^th, 2014 at 4:32am:


Well you could have taken the southern route in the US : from Frisco, to Denver, to Houston, Atlanta, and then Boston. so that bit could have been worse.

But I fully expected a link to Hawai from Oz and Kiwi Country. I know the Frog Lands over there have one.

As for mitigating latencies... the Problem of TCP/IP ( and all the stuff piled on top of it in the stack ) is that it's basically unaware of what happens at a lower layer and how said lower layer works. ( in TCP/IP and UDP it means that the packets have no clue of the medium they are carried on, and as long as they reach destination before the protocol timeout, everything is fine... protocol timeout is.... Long... Think that the stack was designed in the dawn of the seventies, when long distance communication between computers meant 600 bauds modems... ).
and the Ethernet/TCP/IP/UDP suite is not the worst... Take X.25 ( designed more or less at the same time, for Telecoms ).... Time out between a packet and it's retransmission can be up to two seconds ( it's configurable )... and you can retransmit the packet up to 20 times before you go in timeout... so that's basically 40 fucking seconds... Talk about a very long time ( ok, it's way shorter in Ethernet/TCP/IP/UDP, but it's still a matter of several hundred of milliseconds. )
And contrary to X.25, in TCP/IP you cannot configure the timout values...
Add to that the fact that UDP ( that's the protocol used for many things in game ) is basically a connection less, unreliable protocol ( you send the packets with the information and pray that they will reach destination )... So everything is against auto-detecting features to streamline network communication.

100+ms is propagation time expected, 300+ not anymore in modern days... except in Telecoms, because we have protocols that way longer than that to react ( see X.25... default propagation time is 800ms.  ).

Nuckinfutz wrote on Sep 8^th, 2014 at 5:53pm:


So you're a crooked lag midget, thanks for letting us know.

edit: found your pic