The "cleric hireling lag" bug is frustrating me - it has nothing to do with TWF...

[My2Cents]

I'm posting this because I want to bring it up before the update comes out and don't have the time to become involved in all the lamania update forum debates, in case there's something useful in my remarks or it spurs a useful discussion. I keep hearing only about "DPS lag" and TWF nerf complaints.

Apparently this happens in the same places each time. One of them is at a certain spot in "A Cabal For One" on normal. I solo'ed it a few times with hirelings and many times when I reach a certain place in the dungeon so many of those little hobgoblin displacers attack and somehow the client gets overwhelmed. Death and health bars appear to be updating but the display goes crazy, often jittery, often not updating. I run S&B (right now.)

I hope this is addressed in the update in addition to the infamous "TWF" adjustments. Even if it can't be fixed right away, maybe some sort of "check" can be put in the client so it can "detect" the overwhelming flow of incoming data and adjust or pause somehow? Or even temporarily disable the hireling if thats the problem?

Last night I was able to detach myself from combat, return to the entry, dismiss and summon a new claric hireling, and continue on. This just happened to me with golems and warforged in the "Pool of Reflection" area. I notice huge spikes in data received during these times. Last night I also noticed that although response was very slow from other hirelings, they do respond. The cleric did not respond at all.

It wouldn't be so bad except after battling with the spike for some time, I lose the hireling(s) I hired, and usually die, having to start all over and buy/hire the same hirelings again. It can get very frustrating.

Thanks for listening. If this has been addressed elsewhere please let me know the result.

[Tymoriel_Ayreweaver]

/signed.

Everytime it happens you lose game time.. i've lost close to 10 minutes at one point. That was 10 minutes of lost hireling time. This is frustrating enough with plat purchased hirelings. However, I purchased one from the store to experience running with multiple hirelings. That was 10 minutes of lost play time with hirelings that only stay in your inventory for 60 minutes. 1/6th of the time lost not to mention the ddo points. Until its fixed, there should be a disclaimer in the ddo store stating that if you buy a cleric, you may experience significant lag spikes.

[Imnisc]

Dont know if related, but theres an odd bug with hirelings in explorer areas:

When I was doing orchard quests the hireling would follow out after finishing, so I parked him there and did a lap of rares etc.
Entering a tomb or cave a certain distance from the parked hireling disabled my mousebuttons, only way I found to get them back was switching weapons. I could still attack using the keyboard.
This happened many times, different days etc. so not a fluke.

[karnokvolrath]

Originally Posted by Imnisc

Dont know if related, but theres an odd bug with hirelings in explorer areas:

When I was doing orchard quests the hireling would follow out after finishing, so I parked him there and did a lap of rares etc.
Entering a tomb or cave a certain distance from the parked hireling disabled my mousebuttons, only way I found to get them back was switching weapons. I could still attack using the keyboard.
This happened many times, different days etc. so not a fluke.

This happens everytime i summon one of them, but a quick right click left click *repeat 3 or 4 times* gets rid of it rather quickly.

[TechNoFear]

This appears to be due to a bug in the hireling combat feedback (causing a loss in client/server sync).

In the 'Options' disable all hireling feedback and you should see much less of the lag.

[Vua]

Originally Posted by TechNoFear

This appears to be due to a bug in the hireling combat feedback (causing a loss in client/server sync).

In the 'Options' disable all hireling feedback and you should see much less of the lag.

This does not stop it. Hireling lag when it hits is game stopping. I've run it with all combat feedback off and it barely makes a dent. If it's an AOE that goes away fairly quickly, or the mob is killed and can't cast it again it can help a little bit. If it's a tougher fight where the mob casts AOE spells multiple times it makes no difference. Well the difference between 10 minutes of lag and 8 minutes of lag. Most people aren't going to survive that long or won't bother trying to survive that long.

[shadosatblackphoenix]

Just to know if its the same thing you're talking about. Last weekend I was running some IQ quests solo with a hireling, all was going well when suddently the client stopped updating completly. I could still hit enemies, though I didn't see their real position (I had to go blind), and would get feedback on it several seconds or minutes late. Client updates were sporadic at best, sometimes seeing something spawn or die, but rarely. Eventually I died without knowing why, and as soon as I respawned, then for a sec I saw a minute worth of combat feedback in about 3 seconds.

Second time this happens.

[hecate355]

Originally Posted by Imnisc

Dont know if related, but theres an odd bug with hirelings in explorer areas:

When I was doing orchard quests the hireling would follow out after finishing, so I parked him there and did a lap of rares etc.
Entering a tomb or cave a certain distance from the parked hireling disabled my mousebuttons, only way I found to get them back was switching weapons. I could still attack using the keyboard.
This happened many times, different days etc. so not a fluke.

this is ages old bug, press t 2x, or whatever key switches off mouse look mode

[Crazyfruit]

Originally Posted by My2Cents

Apparently this happens in the same places each time. One of them is at a certain spot in "A Cabal For One" on normal. I solo'ed it a few times with hirelings and many times when I reach a certain place in the dungeon so many of those little hobgoblin displacers attack and somehow the client gets overwhelmed.

Yup, it's happened to me there too at the end fight.

Luckily the hireling AI managed to kill both the red nameds while I was in lag hell

[Retssel]

That happens to me every time i'm trying to play solo+hireling any quest or wilderness and fight 4-5 monsters (or more) at once. I'm afraid i'm not self-suficient enough to play with no hireling... Is there any chance of this getting fixed? Can anyone point to a thread where we can see any turbine feedback or report of advancements in fixing this bug?

[vmsbass]

Originally Posted by Retssel

That happens to me every time i'm trying to play solo+hireling any quest or wilderness and fight 4-5 monsters (or more) at once. I'm afraid i'm not self-suficient enough to play with no hireling... Is there any chance of this getting fixed? Can anyone point to a thread where we can see any turbine feedback or report of advancements in fixing this bug?

I would like to see such a thread as well. As many others have said, this hireling lag is a well known issue that has been around for a while. Yet, such a paramount problem persists; and I do not see a sticky thread with Turbine communicating with the players at all on it. "How about something like "Hey, we are aware of it. It is one of our priorities to fix. We will keep you updated on our progress." This problem almost defeats the whole point of hirelings in the first place.

[MadFloyd]

Originally Posted by vmsbass

I would like to see such a thread as well. As many others have said, this hireling lag is a well known issue that has been around for a while. Yet, such a paramount problem persists; and I do not see a sticky thread with Turbine communicating with the players at all on it. "How about something like "Hey, we are aware of it. It is one of our priorities to fix. We will keep you updated on our progress." This problem almost defeats the whole point of hirelings in the first place.

There is a duplicate thread that I posted in yesterday stating that it just came to our attention and that we were looking into it.

[RTN]

Originally Posted by MadFloyd

There is a duplicate thread that I posted in yesterday stating that it just came to our attention and that we were looking into it.

Could it be related to this:
http://forums.ddo.com/showthread.php?t=265497

[vVAnjilaVv]

While I love that the hireling auto port bug was fixed, I have been running WW lately and have noticed if ever there is a time I put my cleric on stand still.....

1. when I hit the summon button they stay on stand still so they do not come to u
2. when the situation above happens they stay in the previous part of the quest chain such as TR or they stay in the explorer area...they do not zone into the quest when u do.

Used to be as soon as u hit the summon button it automatically took them off stand still...not so anymore...this is not game-breaking but rather annoying.