Now this is one I've not encountered before.
Decided to mow through a wilderness area on my Pally today.
Got about half way thru and then mid-jump, just froze.

Waited a few mins and nothing.
Went away and came back 10 mins later and no progress.... Except the archer plinking away at me was starting to have an effect getting in 1-2 points occasionally.

After 20 mins I quit the game.

Now lag is not anything unusual these days, but I wanted to test some of the arguments.
The facts:
Firstly, solo in a wilderness.
Secondly, another client on another computer was communicating with the server just fine.
Third, the sever and game client seemed to be operating just fine because I was taking damage and the archer was moving around.

So it wasn't my connection, and pretty darn sure it is not my PC.
It wasn't somebody else causing the lag.
It wasn't the connection across the pond or the data centre.
This was instance lag.
Now Sev has said that some of the instance lag is when an instance corrupts and the server tries to re-establish it and move the game data.  Makes sense.

But I'm not sure what running thru the wilderness could do to cause an error?  I wasn't even in combat at the time, although an archer obviously found me at some point.
I was surprised at how bad this lag was - even raid lag clears up after a 3-10 mins in my experience (you're usually dead though).   
And I can think of no plausible explanation for it.
Maybe someone was crafting somewhere on my server (unlikely I know  ) and I ended up in i2049 with them?  Don't know and didn't check.

Have you guys seen much lag in wilderness areas (other than when you're kiting 20 Elementals around etc)?

There is no lag.  Ladders work as intended.  Everyone loves pets.  There's nothing to see here.  Please visit the ddo store.  Buy.  Buy.  Buy.  Buy.

Best way to get rid of your lag is to throw more money at the DEVs  . Featherfall can help . Easy as Bee's Knee's .

Sorry for the wall of wood

blaa blaa and fuck you bla

You're all fools. There is a very easy way to avoid lag. Buy it while its cheap.

You can thank me later.

Lelouch wrote on Jan 26^th, 2015 at 6:04am:


Per instance change, per character.  Some restrictions and limitations apply.

Flav wrote on Jan 26^th, 2015 at 8:12am:


You need more tools in your tool box than the hammer you trot out for this conversation.

Not every problem is a nail.

Flav wrote on Jan 26^th, 2015 at 8:12am:


That kind of depends on how you consider priorities.

In this case, you have a paying customer(Turbine) doing business(providing a service to it's customers, in this case, a kobald genocide simulator) that is being hampered by a poor connection. That sounds like a pretty high priority.

Bad connection = poor service = less business = one less paying customer for the ISP. At this point it doesn't matter what anyone's "opinion" of the service being provided is, this is just the way commerce works.

If you are paying for a service, and your service provider tells you "The way you are using this service isn't very important." and then gives you bad service, you are very promptly going to tell them to go fuck themselves.

noamineo wrote on Jan 26^th, 2015 at 12:32pm:

Unless you are Turbine.


... Or a Turbine customer.

noamineo wrote on Jan 26^th, 2015 at 7:32pm:

Let's not kid ourselves about DDO's quality.

Flav wrote on Jan 26^th, 2015 at 8:12am:


Seen this before when I cared more. Shown in traceroute, there was definitely a hop where this was occurring and prob still is.  But we'd still rather blame Turd bin.

OldCoaly wrote on Jan 26^th, 2015 at 6:48am:


Does not work in raids.