Yep, omen seems to be bugged now, we also had numerous players saying they was getting too high threatvalues.
Myself was sitting on 3k+ tps autoattacking on kalecgos, topping out at 5k.. putting myself on about 200% of everyone elses threat

I figured out that it happens if I filter classes.
I usually play with Hunters, Warlocks, Warriors and Druids checked, all other classes filtered. In this case the bug happens described above. Omen works fine if I don't filter any class.

Also always show self is on, but I can't see myself on the list, if my threat is not high enough to be displayed regularly.

Does the Threat1.0 lib work with Omen2? I had several guildies last night saying they were using Threat1.0 and it was working. I thought we should be using Threat2.0 with Omen2. If Threat2.0 is the necessary lib, will Threat1.0 loaded by some other mod cause issues?

Last night on Brutallus our mages commented invisibility did not register a threat drop. Warlocks also mentioned soulshatter caused no difference in Omen2. I do not know whether they were using Threat1.0 or 2.0.

Pretty sure that with the combat log rewrite, it would be literally impossible for Threat-1.0 to be working. Maybe they updated some other mod that installs Threat-2.0 and didn't realize it?

I bet you had Black Wild Magic -> Wild Magic - Spells - World of Warcraft , It's a 100% +threat modifier.

I get this effect between trash mobs but not during actual combat. But, when in Single Target moide, when I swap targets, I'd get the bars extending DOWN from the bottom of the configuration window for a second, then they'd all jump up into their proper place. When this happened, the configuraton window would move upward to the middle of the bar window, and then go back down into it's normal position, and the bar window would dissapear completely until the configuration window was back in it's normal position.

Someone in my raid reported not seeing any bars until the first time they went over 90% of the tanks threat, as well. They got the warning, bars appeared.

Other than that, I didn't see anything particularly unusal, but we're not a deep content guild.

Antiarc,

Any chance of us getting an option to not count pets in regards to the "active when solo" option isn't checked. When I'm soloing on my warlock, I really don't need or want to see my pet's threat. Unfortunatly, with the current revision of Omen2, there's no way to do this (meaning I need to toggle omen off every time my pet spawns from dismounting etc).

[e] clarification

1. After installing Omen 2 and Threat 2.0 - is it safe to delete Threat 1.0 from the addons folder?
2. Inside the Omen 2 folder there is a folder called 'libs' that among other things contain Threat 2.0, but my WOA (dependencies download enabled) still downloads the stand-alone Threat 2.0 - is this intended?
3. Does the current versions of Omen/Threat work with Recount?

Also happened on other stuff than Kalecgos for me, seeing ~double threat. Was also seeing the MT last night doing ~double threat, both on trash and boss (yes, I consider 2.5k-4k tps shown with double threat amount a bit excesive, both on me and on the tank, except when I'm the tank ).

Is there any way to have yourself show up as a different color? I've been fortunate that I'm typically the only hunter in our raids, but I'd still like to see my own bar show up as another color if possible.

What's the point of having 'Active when solo' checked if not for pet interaction? Not trying to be abrasive, I really can't think of a reason to check it if you don't want pets displayed.

Because if you're using a Succubus and drain tanking, your screen is going to be stuck in Ambulance Mode - flashing because you're passing 90% of the demon's threat. Unless the pet is actually tanking, it's just obnoxious.

That is, hunters probably want to see their pets, warlocks probably don't.

From what I was able to see last night during Gurtogg work, FD is detectable, resists and successful ones included will register with the new Omen. Unfortunately after a period of time Omen became so crappy we ended up doing the fight without the use of a threat meter and sort of winged it like the old days when it came to threat management. Tanks threat wasnt registering properly, other people had insane amount of threat when they've simply stood there on the pull but their first on threat list by a long shot and other various things I cannot think of off the top of my head.

Wouldn't unchecking active when solo solve this problem?

Is there a way to make those icons smaller? I'm sure I have to just be dumb and missing the option somewhere but the gigantic icons for switching between modes would be handy to shrink.

Display options > Module Window > Size.

Bingo.


That and I don't typically have omen running while soloing at all, yet for pet classes this isn't an option. If you have omen enabled it is ALWAYS running if you're a pet class, unchecking active while solo does nothing because you have a pet (and thus aren't 'solo').

Is there some way to get the column headings back? I mean the thing that said like Name, TPS, % and whatnot at the top of all the bars.

Yeah major issues with Omen since the patch, despite having the whole raid download updated versions immediately before raiding every day. Soulshatter is not registering at all, ever. Half the time the tanks don't even show up on the meter at all, when they do often their threat is insanely high. I have pulled aggro multiple times even when Omen showed me way under the tanks. We also had the same issue on Bloodboil with nothing being accurate. Basically it is unreliable at best, and useless at worst. I'm just being very cautious and estimating threat myself for now.

Same story here. My feeling that the combination of converting over to the new combat log combined with adding new features at the same time was a mistake.

Omen was simple to learn, and easy to use. Omen2 simply doesn't work in it's current state, and is not intuitive either, raising the frustration level attempting to make it work.

IMO, strip it back down to basics with support for the new combat log.

Yeah, it seems like a good portion of the issues we're seeing are related to the new GUI moreso then the threat parsing. As a lot of the bugs are uncertainty with the display versus actual threat values. The pullout bars and being able to recolor and resize individual bars (namely, my own) were nice features.

For example, killing the trash sentinels in sunwell with the RSTS chain lightnings, Omen was going nuts because it didn't have the delay in changing what it considered the primary aggro target, while I believe the old Omen handled that decently. In addition to the window itself not resizing properly or overlapping bars when you tried to filter things.

It would be interesting if the old Omen would work with the new threat lib though. I'm not sure what would need to change to make that happen.

You've done a great Job Antiarc, but the older GUI was simple and did it's job, and some of its features are sorely missed.

I've noticed a lot of addon traffic generated since patch that start with TL2? Most players have Threat-2.0 and TL2? messages generated, but not all have TL2?. The Threat-2.0 messages behave normally, but TL2 are out of control, sometimes spamming for a long time after there is no combat going on.