Raid problem

[zork]

I have already registered UNIT_HEALTH and UNIT_MAXHEALTH. Like evil posted that will help you nothing under certain circumstances.
FrequentUpdates is a nogo for raidunits.

[Talyrius]

UNIT_HEALTH and UNIT_MAXHEALTH are going to be firing constantly for every unit in a raid. FrequentUpdates couldn't be much worse.

[zork]

UnitHealth gets only triggered for each unit on it's own. Some raidunits will not loose a single hp in a complete raid. The unly unit that get's massive unithealth events are tanks. If it would be one onUpdate for the whole raid that my be another story but up to 40 onUpdates...uuuuuuh.

[Monolit]

Originally Posted by zork UnitHealth gets only triggered for each unit on it's own. Some raidunits will not loose a single hp in a complete raid. The unly unit that get's massive unithealth events are tanks. If it would be one onUpdate for the whole raid that my be another story but up to 40 onUpdates...uuuuuuh.

uhm would really 2 updates every second on each of the raid unit hit performance that bad?

[drakull]

I never saw raid frames behaving like this before with any oUF's layout i tried. So the problem is: this is not an old bug. This started to happen to all oUF's layouts a few days ago, right?
I think it's better to find what caused it (a change in some event, maybe?) than keep guessing workarounds for it.

[Talyrius]

There is definitely something amiss. When this happens on my layout, the health/power bar colors aren't updated either. When someone disconnects, it looks like they are still online. Targeting them gives me their real status.

[yj589794]

I've not done any testing, so this is just a guess...

Is the UNIT_CONNECTED event being fired?
Have the parameters on UNIT_CONNECTED been changed?
Is the UNIT_CONNECTED event passed incorrect parameters? (e.g. wrong unit)

[zork]

I don't think that this is a oUF bug. I think it has to do with the updated SecureHeaderTemplate that gave us party-/raidframes without the flickering.

Maybe that is because no-one noticed that behaviour before. Header units updated like crazy before patch 4.0.3.

What would be interesting to notice is if the problem persists if we spawn headers without the visibility argument.

http://www.wowinterface.com/forums/s...ad.php?t=36747

[drakull]

I think Zork is right. Some things changed when they corrected the flickering, this changes have to be reflected inside oUF's code.
Tags not updating correctly is just one of the problems I've noticed:
- My HealthPostUpdate function changes the Healthbar's color to black when someone disconnects, to white if the unit is a ghost and to red if the unit is dead. After the patch the unit must be in range for the color to be changed.

Seems to me that the post update function is not even being triggered if the unit is not in range, so it *must* be a change in some event. Looking at oUF's code, it hooks the following events for the Update function:
- UNIT_HEALTH
- UNIT_MAXHEALTH
- UNIT_CONNECTION
- UNIT_POWER
- UNIT_FACTION

I'll try to test this events when I get home.

[zork]

update.

Just tested a group without the visibility argument and a toggle function. Same result. Header units get not updated properly after someone leaves.

But still testing. Maybe I'm blind. Will take some set of screenshots.



Only getting this bug if someone leaves.

[Tobbe8716]

Btw Im still getting this error, just noticed it today but its just when someone leaves. When I had the other custom visility it happend when someone joined the raid/party aswell sometimes.

[Sauerkraut]

I noticed this on my raid frames on Tuesday night. Happened a couple times. I haven't noticed it in a party at all yet, but definitely in a raid.

[Dawn]

Happens for me on party frames, too.

[Talyrius]

Has anyone figured out an efficient way to workaround this problem as of yet?

I'm hoping haste has been following this thread. He must have a better understanding of what is going on here than we do.

[haste]

Should be solved with 4a37d25caf6eebd36571. I still have one more item on my TODO list before I push 1.5.5.

[Dawn]

Originally Posted by haste Should be solved with 4a37d25caf6eebd36571. I still have one more item on my TODO list before I push 1.5.5.

Which is secure player auras?! *cough*

[haste]

Originally Posted by Dawn Which is secure player auras?! *cough*

It actually is. I have a potential hack which might allow me to implement it how I want to, but I have to to actually test it first.

[zork]

Tested the party fix. Bug is gone. Thx.

[Luzzifus]

Updated to 1.5.5 yesterday but names in raids / bgs are still not updating correctly.

[haste]

Give me a small test case.