The super quick-and-dirty fix is to install LibBabble-Spell-3.0 and LibBabble-Boss-3.0 from Wowace. That should fix it up until I can figure out what exactly the other fixes I need to make are.
The super quick-and-dirty fix is to install LibBabble-Spell-3.0 and LibBabble-Boss-3.0 from Wowace. That should fix it up until I can figure out what exactly the other fixes I need to make are.
That did not fix it for me. I've done a complete reinstall of all addons through the wowace updater. Don't know if this will help you debug but just thought I would let you know that this fix does not work for everyone.
That did not fix it for me. I've done a complete reinstall of all addons through the wowace updater. Don't know if this will help you debug but just thought I would let you know that this fix does not work for everyone.
Did you clear the Omen .wtf too? I applied Antiarc's solution but on top of that I installed the latest Threat 1.0 as well. Omen works perfectly, but Recount is still facing problems retrieving data from Threat 1.0.
Did you clear the Omen .wtf too? I applied Antiarc's solution but on top of that I installed the latest Threat 1.0 as well. Omen works perfectly, but Recount is still facing problems retrieving data from Threat 1.0.
The manual installing of Threat 1.0 fixed it for me. I guess some other addon is screwing it up?
When do a healer benefit from using a threat meter ?
We have a little debate in our guildforum about using Omen or not.
I have stated that a threat meter is a waste of the comps memory for a healer. with only 1 exception.
Bosses wich the tanks can't taunt. It's really hard for the tank to keep aggro. This is defo where healers can get aggro. When you're with 7 healers in a raid, you do have time to stop healing for a few seconds till you threat goes down.
- This is the only situation i can think of when a threat meter is not a waste of the comps memory.
Are there more situations when a threat meter is a usefull mod for a healer ?
Most bosses are not tauntable, and yet it doesn't matter. Really I don't think healers have anything to worry about with regard to threat, I mean if chain-healing shamans in melee range on Void Reaver and circle-healing priests on Reliquary of Souls don't pull aggro then nothing will. Healers just don't generate a lot of threat compared to how much tanks can put out, especially with threat reduction talents and salvation.
Also may I suggest that if your tanks have trouble holding aggro on taunt immune mobs, you may want to refer them to the appropriate thread here so they can learn to generate threat (if they're a druid or warrior, that would be dukes's feral thread or Quigon's warrior thread).
Healers are somewhat unique in that even if they threat cap, they can't really slow down or let up. We've had our CoH priest nearly pull aggro on Gurtogg before, but what he's supposed to do, stop healing bloodboiled people?
I think the value in a threat meter for a healer is the ability to see things like who is going to need healing soon; this is particularly true in tank-swapping fights like Void Reaver and Gurtogg. Omen2 is also going to have some additional views that will be more handy to healers, as well.
Were the issues with Omen fixed by chance? I'm at work and can't update right now, but was having a major issue last night with Omen not working at all. Went with the most up to date and it wasn't throwing any babel errors, assessment was though. I have been having to revert to a February 17th build for one that wasn't giving all kinds of weird errors or even working at all.
00:59 -!- ChanServ changed the topic of #elitistjerks to: Elitist Jerks | HAPPY BIRTHDAY PROMDATES!!! qtpie | Rules: http://elitistjerks.com/chat.php
[2] [Ardente]: I get to put on a donkey show in dalaran every day now!
We've got a druid off-tank who disappears from the threat list on omen. He's deleted his entire mod folder and reinstalled everything more than once without fixing this problem, and it has persisted through more than one version of the mod. Any ideas?
Bug in the latest revision (was there in past revisions too I believe).
If you have omen standby'd on a character, and logout. Omen will remain in standby mode, but the frame will suddenly be visible again (even if it wasn't when you set omen to standby).
We've got a druid off-tank who disappears from the threat list on omen. He's deleted his entire mod folder and reinstalled everything more than once without fixing this problem, and it has persisted through more than one version of the mod. Any ideas?
All of the feral druids in my guild are suffering/have suffered from this issue. They can see themselves on the threat meter, but as for everyone else, we see them for a second and then they disappear. Are there any known quick fixes to this issue? My guild is considering returning to the awful KTM threat meter because of this problem.
/edit
Upon further discussion, this is not a recent issue resulting from an update, either. The guild says bear threat has always been this buggy since they started using Omen. I quote from one of the druids, "He shows up for like 5 seconds, then his TPS freezes, and his threat bar stops moving. If he's in cat, it shows him, and if he's in bear, no dice." Same thing has happened consistently with every bear they've had raiding with them.
My guild has never mentioned having this problem when I'm tanking, but I run with my libraries disembedded. I have seen people have problems like this (not necessarily just with bears) when they have multiple addons which include Threat-1.0, are running embedded, and some of the mods have older versions of the library.
I've non-existing Omen for a couple weeks, but it took me until now to come here and see if my problems were shared by others. I had been running WoWAceUpdater, but when I looked in my addons folder, it appears that LibBabble-Boss, Spell, and Zone were not being updated. After manually updating those 3, I have working Omen again. Not sure if that was just a hot-fix for me, but maybe something that those of us that rely too heavily on auto-updating can use.
All of the feral druids in my guild are suffering/have suffered from this issue. They can see themselves on the threat meter, but as for everyone else, we see them for a second and then they disappear. Are there any known quick fixes to this issue? My guild is considering returning to the awful KTM threat meter because of this problem.
/edit
Upon further discussion, this is not a recent issue resulting from an update, either. The guild says bear threat has always been this buggy since they started using Omen. I quote from one of the druids, "He shows up for like 5 seconds, then his TPS freezes, and his threat bar stops moving. If he's in cat, it shows him, and if he's in bear, no dice." Same thing has happened consistently with every bear they've had raiding with them.
I'm a warrior but had a similar problem reported to me mid-raid last night. Some light investigation revealed the following:
Help! People say my threat stops sending after a while and I "get stuck". What do I do?
This is caused by some other excessively spammy addon you have installed, which is eating up all of your addon traffic bandwidth. Threat-1.0 uses ChatThrottleLib to ensure that you don't send too much addon traffic and get disconnected, so Threat data gets "stopped up" when another addon is sending too much data. It will usually end up sending after the fight is finished, but of course, it's useless then.
I recommend FuBar_AddonSpamFu (from files.wowace.com) for finding your spammy addons.
Unfortunately, there's no good solution to this other than disabling spammy addons, since sending too much traffic at once will cause you to disconnect, which is even worse than having no threat data!
This is copied directly from the Omen FAQ which can be found at http://www.wowace.com/wiki/Omen. I've not found out which addon is flooding my bandwidth yet but I recently installed 2 new damage meters so they'll be first on my list of mods to check.
Anyone having issues with Omen? We're at the svn bleeding edge and getting lots of errors, plus threat on Bloodboil is totally at odds with whats actually happening. Is there a way for me to capture the error output for later?I can't really take screenshots while tanking him. This is with r66243.
I should add we went to the svn because we were having the same problems with the version people had downloaded yesterday.
We had issues with Bloodboil tonight too. People would stop generating threat on Omen during Insignificance and then just never start again, except for one of the tanks every time. It was really strange.
We had several people dc durring the AE parts of the Hyjal trash, and continue to have performance struggles until they turned it off. Error messages were fairly common, and Soul shatter no longer appears to work. Bummers.
"I have nothing personally invested in my own opinions. I'm just, like, inviting you to join me on the bandwagon of my own uncertainty." -Taylor Mali
We definitely had Omen problems on Gurtogg. Pretty much the same thing people are describing, Insignificance just killed it.
I also happened to notice that Misdirect doesn't always seem to show properly. Specifically, any time I misdirected a warrior, the threat would show up under my name. I'm not sure if it's only warriors, but the one time I had to MD to a druid it seemed to work fine. But every warrior MD didn't respond properly.
Seems to be working ok today but every so often all the threat bars jump up underneath each other and you get 10 names/bars stacked on on top of the other.
No errors, disconnects or graphical problems to speak of -- but the threat is just plain wrong!
As a BM hunter, Intimidate does not seem to generate extra threat.
MD's do not register.
In general, the threat being displayed is wrong.
There was a point where I was over 170% (130% is aggro) of the MT's threat in MGT last night and did not pull aggro. I believe this a combination of MD at the beginning, plus an early FD that did not register.
Apologies for no screenshot, but I'm not able to access my gaming PC at the moment.
02/18/08, 5:03 AM
Similar Threads
