Deactivating reaper tree and the lag

[draven1]

Everytime when someone(including me) exit from a reaper quest, the public instance has a freeze.

It seems it is from deactivating reaper tree of players(Dungeon instance -> public instance). It gives freezes even for non-party members. Whoever in the instance that is affected by those reaper players.

Can you implement those deactivation of reaper tree smoother? Like asynchronous way to deactivate?

Or you can change the time to deactivate reaper tree, no deactivate when you exit(entering public instance, because it doesn't matter whatever you have reaper AP on public instance).

You can make it to deactivate when you enter non-reaper dungeon instances, so, you can make the people who was in public instances have less lag from these deactivation.

[boredGamer]

Everytime when someone(including me) exit from a reaper quest, the public instance has a freeze.

It seems it is from deactivating reaper tree of players(Dungeon instance -> public instance). It gives freezes even for non-party members. Whoever in the instance that is affected by those reaper players.

Can you implement those deactivation of reaper tree smoother? Like asynchronous way to deactivate?

Or you can change the time to deactivate reaper tree, no deactivate when you exit(entering public instance, because it doesn't matter whatever you have reaper AP on public instance).

You can make it to deactivate when you enter non-reaper dungeon instances, so, you can make the people who was in public instances have less lag from these deactivation.

Or as others have said, just go ahead and leave reaper bonuses on the whole time. Recalculate only if you switch reaper->non-reaper?

[LurkingVeteran]

Or as others have said, just go ahead and leave reaper bonuses on the whole time. Recalculate only if you switch reaper->non-reaper?

I don't understand why there even is visible lag for changing some numbers. A modern CPU can do about a billion calculations per second. Here we are talking about a few hundred. This wouldn't be a problem on any 80ies home computer. I'm guessing there is some very silly architecture here, perhaps involving a very overloaded database somewhere. I also don't really understand why this would lock up the entire instance. Since the player is leaving the instance anyway, there is no need to synchronize this with instance state.

If the entire instance routinely has to wait to synchronize with character, or even worse, client-side state, it would actually explain a lot of why DDO is lagging. Maybe those claiming that having one lagger can cause an entire group to lag were actually on to something, if the entire instance has to pause to wait to synch with client-side state over a poor connection...

[draven1]

Thank you for devs to fix this kind of lag finally