Strakeln wrote on Jan 3^rd, 2015 at 12:39pm:


I agree about the computers we use and the 4 generations gap... I saw it when my DDO PC fried in August ( It was built a few month before DDO release, and lasted that long ).

Now for the lag issue, the problem is most probably Cogent... But I don't think Turbine has any power of over that.

A few relevant traceroutes from various people all over the world would prove my assertion ( or allow me to say that I'm wrong  ).

It's also good to note that LoTRO seems also to be hit by a lagmonster right now...

Brosef wrote on Jan 3^rd, 2015 at 1:35pm:


Stop whining asshole. Were discussing the lag here as it is the hottest topic as of now.

And if you're one of the idiots who thinks it's the players' computers, well ...  sry I didn't get the sarcasm. Otherwise you're obviously even dumber than your post made you look like.

ok, According to a traceroute I performed during a 'Greek Freeze' on G-Land while gathering for a FoT, the issue is on a router in Boston.
just giving the relevant bit :

  8    25 ms    25 ms    25 ms  be2489.ccr42.lon13.atlas.cogentco.com [154.54.39.113]
  9    98 ms    98 ms    99 ms  be2493.ccr22.bos01.atlas.cogentco.com [154.54.42.97]
 10   278 ms   208 ms   210 ms  te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
 11   101 ms   101 ms   101 ms  38.104.252.70
 12   115 ms   114 ms   116 ms  border1.te8-1-bbnet2.bsn003.pnap.net [63.251.128.107]
 

It would be nice to know if other people ( well people that are not in Europe... all European traffic go through that router ) go through the router :
te4-2.ccr01.bos06.atlas.cogentco.com

As he clearly seems to be the culprit ( at least for European Lag Spikes )
Please note that it can have another name and be the same router...

stuff like te1-4.ccr01.bos06.atlas.cogentco.com has about 99% chances of being the same router.
( the first bit of the name is used to identify the card/interface as in : te card 1 interface 4 or te card 4 interface 2 [ it can be there reverse... te interface 4 card 2 )

Brosef wrote on Jan 3^rd, 2015 at 1:35pm:


Fuck off back to the motherboards you Turbine cock sucking douche.

OldCoaly wrote on Jan 3^rd, 2015 at 5:43pm:



No my hypothesis is that different people from different places over the world will give a different tracert between them and Turbine PNAP hosted datacenters.

From all these traces we can then find all the routers that can have an impact on everything.

I'd be the first surprised if the different servers have a different traceroute. ( they are all on the same /24 network... well even the same /25 )

Strakeln wrote on Jan 3^rd, 2015 at 12:39pm:


The game gets bigger every update. When was the last time you logged in? The "current" recommended specs haven't been updated since '06. If you try to play with that kind of hardware, you are a masochist. The first 2 machines that I played DDO on have fallen so far behind that they can't even log in anymore.

Yea, there was no lag for me before u13, and that is same time that double login bug came.

I still remember cogent, over the last 10-12 years I regularly heard that name when the online games I was playing had serious lag problems.

So it wouldn't surprise me if they are at least part of the lag problem.

And shitty coding is causing more lag than shitty hardware, Black Loch is a very good quest to prove that.

And don't forget the players who pretend to lag because they suck too much.

Also DDO doesnt work well with Raptr with R9 gpus and amd cpus.

Your Usb ports will have a hard time and your keyboard will be stuck.

OldCoaly wrote on Jan 4^th, 2015 at 7:07am:


I've seen weirder things caused by a hardware issue on a router...

Things like : One single IP address on a customer network being unreachable if you came through a given router on the ISP backbone... if you came through any other router in the backbone the issue was not there... in the end it was caused by an issue on the card facing the customer network. ( all the other interfaces on that card worked fine, it was impacting one single interface out of 10. ) All the other addresses on the customer network were reachable from everywhere. ( the customer has a /28 on that network one single address couldn't be reached, all the other addresses were... )

And it depends on how the actual game server ips are advertized in the network ( read : routed ).

If they are advertized as unique /32 then it's quite possible to have a huge issue on one, and no issue on the next address/server.
( or use my above example and instead of a 100% loss for a given IP take a 5 to 50% variable loss, you'll have the Lag effect )

I can't legally check how they are advertized right now... ( I have no reason to connect to my customer nodes on a sunday afternoon while still being in vacation )
but I might be able to steal a few minutes to perform some checks tomorrow once I'm at work.

SwashbucklerHater wrote on Jan 4^th, 2015 at 8:25am:


Smart coding can go a hell of a long way to reducing required system resources,...but graphics lag is still client side.

SwashbucklerHater wrote on Jan 4^th, 2015 at 8:25am:


I think this is way more common than anyone is willing to admit. Especially now that the noobs can't blame the cleric.

remember when they nerfed twf years ago to 'fix' the lag? didn't that have something to do with too many weapon swing calculations? well seems there's a shitton of new stuff that adds doublestrike and offhand attack chance and attack speed. are we gonna get another round of a twf nerf style 'fix'?

the Khyber issue is not a single issue... there's more than just the number of instances.... and that's what's lagging the other servers...

Probably Notwork.