02/05/2013 10:25 PMThat's what I was afraid of. How is it that something this prevalent has gone unfixed for so long? On a related note, what do you do, Tiriél?
Posted by Jonesie
I reload my UI or try to get out of combat. It's really the only thing you can do. It's frustrating, but there you have it. Normally your raid frames should only have issues if someone leaves or joins the raid while you're in combat, which usually only happens in BGs (where you can easily run away and drop combat) or LFR (where it...probably doesn't matter if you can't see half the raid). However, sometimes it happens in 5 mans. I've actually manually targeted and dispelled someone before when I had the bad luck not to see them.
Normally VuhDo maintains whoever is marked as the tank, and my bar, but one of the DPS will get replaced by the new person. If someone LEAVES the group while I'm in a 5 man, VuhDo normally just puts a blank "DC bar" area where they were, and leaves the rest of the frame alone.
As to how it's gone on this long...I don't know. As was explained to me, the Blizzard UI has an inordinate number of things "hooking" into the raid frames. But the raid frames themselves are "protected," so when those UI elements try to call on something and end up calling on the raid frames for whatever reason (just doing their normal job, mind you), it's returned as a "taint" and you get a bugged out frame. They need to fix it, but so far have refused to acknowledge the problem.
Edited to Add: Kaels found a way around the problem a few months back, utilizing Xperl, if I remember correctly. However, I don't know if the solution he was using still works. Maybe he will comment here and expound!