Lag issues

[AstorPotamus]

So...the ONLY difference I’ve noticed since this new lag patch is that instead of being held in place for several minutes while being attacked, my full party is now only being held in place 2-3 minutes while being attacked.

Yep...all SSG managed to do was apply bactine and a kiss to an amputation, cuz they really didn’t fix much as far as what I’ve seen on Orien.

[Ultinoob]

The lag is still there.

I did von 3 eh solo with hireling. glad i only did it on EH as the lag was pretty bad. I did not capture the first time it lagged but it was about the same maybe longer.

This was on Ghallanda between 17:30 and 19:00 copenhagen time.



And for some reason the ice storm i was in when it lagged the first time persisted even when i was not in it anymore. It even was there when i finished the quest and was in house k.

[palladin9479]

So...the ONLY difference I’ve noticed since this new lag patch is that instead of being held in place for several minutes while being attacked, my full party is now only being held in place 2-3 minutes while being attacked.

Yep...all SSG managed to do was apply bactine and a kiss to an amputation, cuz they really didn’t fix much as far as what I’ve seen on Orien.

I believe Cordovan specifically said that this patch wasn't going to fix lag in any way shape or form, that it was merely to address a few sources they identified. The instance wide Mass Hold Player we've been experiencing is a much deeper issue.

[Damian]

Would it be possible to skip working on a update for one round and address the issue of lag i think its making everyone quit so instead of doing update come on work on the lag please.

I am really getting fed up with these lag spikes as well. Game is in aweful state at the moment, please fix it ASAP. Lagged again 20 secs straight and of course died. NOT WHAT I PAID FOR! (sorry for the caps but I am really ****ed)

[Damian]

Maybe end the hardcore server early to reduce the lag?\

I suspect that they are giving that server more bandwith?

[Torkzed]

I believe Cordovan specifically said that this patch wasn't going to fix lag in any way shape or form, that it was merely to address a few sources they identified. The instance wide Mass Hold Player we've been experiencing is a much deeper issue.

I guess it depends on how you interpret Cordovan's post, which was:

Under no circumstances will tomorrow's work "fix lag". Hopefully it will have a visible improvement, though. We'll see tomorrow.

The way I read this was that he was acknowledging that there was no single solution to the lag problem that would make it all go away. However, given the context of the post to which he was replying, the second sentence almost certainly was referring to an improvement in the phenomenon that most players refer to as "lag".

[Chacka_DDO]

I have been running the 64-bit client since the day it came out and Yester Hill is just as laggy for me with it as it was with the 32-bit client.

The main point was that you should not mix up performance-related graphical lag with server lag.
Also graphical is not always the players' fault but server lag is the only kind of lag SSG is fully responsible for.
And also graphical lag can be affected by SSG but here the player can at least do something with a higher performance system.
Just Yester Hill was/is another story because it runs poorly on any system with the 32-bit client, on a 64-bit client it runs at least good on some systems.

But the question is why your system is not improving with the 64-bit client.
The main advantage of the 64-bit client in comparison to the 32-bit client is that the 64-bit one can use more memory but of course you need to have actually more memory than the 32-bit client can use.
My system sits on 32GByte RAM and an 8 GByte graphic card and I can report a big improvement in Yester Hill.
But every quest should run also on the 32-bit client and should not have serious RAM issues because DDO is supposed to run with the 32-bit client unless they make the 64-bit client the official supported DDO client.
Its a matter of quest design that this quest uses more memory than a 32-bit client can handle.
Of course, if your system is fast enough you may suffer less graphical lag but the lack of RAM can never be fully compensated by faster data transfer (memory bandwidth).

[Phoenicis]

And for some reason the ice storm i was in when it lagged the first time persisted even when i was not in it anymore. It even was there when i finished the quest and was in house k.

My guess is this likely, server desync, the server never got the packet that said you moved out of the area of effect, so never removed the effect from you. Ice storm seems to be one of the effects that doesn't get reset on dungeon exit/rest.

[Epicstorms]

Today I logged in for the first time in months to actually play a bit.
My guildies were raiding, should be fun.

We went in on Too hot to handle, lagged on the very first fight, couldn't move. We reset the instance.
Went in the second time, also insane lag, we reset the instance.
Went in the third time, lag was still there, but it wasn't too bad, but... We lagwiped because we couldn't do a single thing during the boss fight.
We decided to call it and move on to another raid.

Decided to run hard Killing Time because R1 was probably too much with this lag.
We ran through the raid, but had several phases where we could barely move. Stuttering all over the place.
In the end, we finished it. No challenge or fun at all, it was simply done on pure powercreep.

Such a fun game this is... Gosh.