If omen is specifically toggled off by the user (by clicking on the omen icon on fubar or the minimap or broker or using /omen toggle), it remains hidden until toggled on again by the user.
The on/off toggling is intended as a user-overriding mechanism to turn on/off omen display irregardless of the "show when ..." options. If you are affected by this, turn it on, and leave it on/showing. And the "show when ..." options would then show/hide omen appropriately the next time you leave a city/join a group/raid, etc.
Forcing it off disables Omen. In this respect, you can consider the show/hide toggle as a on/off switch, when off, it is completely off, when on, it follows the "show when ..." settings. I hope this explanation solves the issue.
Note: Turning Omen on will cause it to always show initially, to allow you to configure how it looks, regardless of "show when..." options. The "show when..." options are still followed when something happens to change whether Omen should show or hide itself.
I noticed something odd happening with Omen in our BT raid tonight. It was showing wildly unrealistic threat generation for myself, such as 2500TPS+ on Supremus. I was even generating close to 1000TPS on targets I wasn't hitting. We also noticed one of our hunters didn't show up on Omen at all. For some reason Omen was showing both my own and the hunter's threat as being mine. This problem lasted continuously for several boss fights and a lot of trash clear, so it wasn't a temporary issue, and the hunter's threat for all those fights was displayed as mine. The problem vanished as mysteriously as it had appeared clearing the trash to Bloodboil, possibly after said hunter had died once. I play a druid tank if it makes any difference.
I was using the 79986.3 version published a day before, and the hunter had a recent version too.
Omen will need to be updated to use the Blizzard threat API instead of the Threat-2.0 library. This has not happened yet, as the API is not finalized. I'm sure Xinhuan or another Omen developer will make an announcement once they have something ready for public consumption in 3.0.
First of, thanks for the work you guys put into making this addon for us.
I guess Wrath and 3.0 patch is more important then my request but I'll post it while still remember it:
On the "Options/Show when..." page, is it possible to get an option for "when in Combat" ("You are in Combat" to keep it consistent)?
To keep my UI clean I try to replace stuff I need OOC with stuff I need in combat, so this would be a "nice to have feature"
Will consider for Omen3, which I just started writing today. Lol.
At the moment, all it has is a non-configurable "SingleTarget" mode, nothing else, no fancy stuff, no combat log parsing., doesn't sync, has no config, and uses pure Blizzard threat events and values.
One problem is that Blizzard's threat events doesn't fire on units you aren't actually in combat with, so if one party member engages a mob, you didn't enter combat yet, Omen3 wouldn't actually display anything because wow would refuse to tell you any threat information on that mob until you start doing damage to it (it doesn't work if you send your pet to attack it, you have to attack it).
In the current beta patch build 8982, if you aren't in combat with a mob, Blizzard's threat API returns all nils. What does this mean?
What this means is, if your main tank starts pulling a mob/boss, you can't see how much threat anybody has on that mob until you do an action that causes threat on it (such as buffing) - sending your pet in doesn't count, you can't even see your pet's threat either until you get on the mob's threat list.
That is UnitDetailedThreatSituation("pet", "pettarget") will return nil until you enter the mob's threat list, as does any other unit you query on any mob with valid unitIDs. Likewise UnitThreatSituation(unit, mob) will return 0, even though your pet or main tank in your raid is clearly in combat with it.
On a side note, if you body pull a mob, you are considered on its threat list and will get every threat update on it even if you remain at 0 threat.
Now I consider this to be "kind of" lacking since this means that syncing via the addon channel will be required if I want to know how much threat the tanks all have (especially some boss fights require multiple tanks fighting for aggro) before I start attacking.
Can we please get threat details on any mob that any member of your raid/party/pet is engaged with (within visible distance), rather than you having to to be specifically on the mob's threat list?
I hope you get an answer Xinhuan, and that it will be "threat is now visible to all who target the mob of the same party/raid". I mean, if I am in group a, I don't need to see group b's threat lists, so that could be how they could minimize work on it - I hope.
I know you're not really doing anything with Omen2, but something that's always annoyed the crap out of me was the fact that I couldn't adjust the font size of the title text. Even when making the title "module" larger, the title text doesn't get any bigger. Assuming you'll use a similar GUI structure for Omen3, please think of us poor visually-impaired and make all text elements resizable! (And/or make the Omen2 title text resizable).
Copied from my post in the help thread:
I've used Omen religiously for months now. I've never had any complaints or problems with it until recently.
Omen's "Single Target" mode works fine for every single one of my characters, except my hunter.
I get the sound and warning across my screen when I'm hitting 90% threat, but the tank, and any other dps (including myself) do not display on the bars on Omen.
It works correctly for my warlock, warrior, druid, mage, priests, and paladin.
Just not the hunter... I've tried resetting my profile and messing around with it on a whole, and I also followed Phanx's instructions in the help thread, but the screen shot below was Omen after deleting the .lua file/omen folder and reinstalling.