Cel

I had the whole guild switch over to Omen last night for our TK raid, since the mod has hit stable beta. (Was getting jumpy waiting for final release... too excited to replace KTM maybe. :P) We'll be using it from now on unless some severe problem crops up and forces us to go back to KTM.

Few things I noticed:

Two trash pull, at least, threat values were very off. A Warlock should have been tanking according to the mod, but that was certainly not the case. Every other pull of that same mob was accurate, but that one particular pull something strange happened. One of the pulls was one leading up to Void Reaver with the Crystal Forge Devastators... the Devastator's threat list had Warlocks and priests at the top of the list with no warriors anywhere close, yet a warrior was tanking. It looked remarkably like what the global threat meter should have looked like, now that I think of it, though it didn't occur to me at the time so I didn't compare the values. The other pull, I don't remember well enough to give you anything worthwhile about it.

Boss fights the mod is solid... not a single problem there in any of the first three encounters in the zone (it was accurate for Kael'Thas phase 1 too, on our only pull of the night after our first Solarian kill last night too, for what it's worth), except one thing which isn't really a bug, it's just a result of the mod's design: Because threat values are displayed when you target something... if you can't target the mob, you can't get the threat list. For Al'ar if we didn't know the threat values ahead of time (which I suppose it's not a huge problem just to remember for a few seconds who was on top), when Al'ar died after the first phase, we wouldn't know who Al'ar would be going after following the transition. Maybe having an arrow you can click to cycle through active threat lists would be cool, though I suppose this isn't a huge deal. (Maybe this will be overcome by the sticky targets you mentioned earlier?)

The % column appears to have problems from time to time. It seemed to fix itself when more and more people installed Omen throughout the night (at the start, ~5 people were running KTM and not Omen... 2 of which were tanks), and, as a result, less KTM data was being processed. Not positive this is the reason, but I only noticed the % column having problems early in the night. It would display either 1.% or some astronomically high number, then revert to accurate data for a bit, then back to 1.% or some high number.

The threat list likes to clear itself then repopulate from scratch. It's not a threat wipe, as the values are still what they were, but often all my bars will disappear and then start filling up (presumably as new data is picked up) without actually resetting the values.

Also: one Warlock reported getting quick FPS lag spikes upon entering and leaving combat. I'll try to get more specifics, but he said it started happening to him after he installed Omen. In addition, a mage couldn't get the Omen gui to show. /omen brought up the menu of options, and he was broadcasting threat values, but could not see the window.

Overall, nice work on the mod.. I'm still trying to convince my guild that the little problems they're finding with Omen are not as bad as the little problems they were used to having with KTM already. Some people are afraid of change, it seems.

"There is much pleasure to be gained from useless knowledge." - Bertrand Russell

Alpha is recruiting... go go.

 

Caligula

Going along with what Cel said, is there any way to set a master target or focus target like in KTM? Maybe an option at least so you can see your threat on a mob without targeting it? I was noticing this last night on Hydross. It would be terrific if you could see your threat on a mob that you are not targeting. Maybe add an option to allow a keybind to set a focus target (like a focus macro).

Other than that the mod seemed to work perfectly. We had a mix of KTM users and Omen users in raid last night and I can definitely say I'm much more happy using Omen than KTM.

I did notice the thing mentioned above about the list clearing itself. Like they would reset but maintain their values and repopulate the bars. Just an oddity.

Great mod.

edit: Ugh nevermind I just saw on the last page that sticky targets are coming, eh I hope my suggestion helps.

 

Malan

That sounds like a conflict with another Ace mod or one of the libraries, I sometimes get that when I updated a few Ace2 mods and some of the changes made to the libraries make the older mods goof up. It results in one or more of the mods not responding to the menu commands.

Shitting up every single thread on EJ since '06

 

Nemaa

"Also: one Warlock reported getting quick FPS lag spikes upon entering and leaving combat. I'll try to get more specifics, but he said it started happening to him after he installed Omen."

I had the same problem but it is not because of Omen only, i'm sure! It must be because of something+omen together. A week ago I noticed heavy fps lags every time when combat ended. Some days ago I deleted some addons like ct_raid, ct_mailmod, ktm, updated some addons like damagemeters and all ace addons I use. I didn't encounter any lags since then.

 

Cel

Yeah, I sent him on a quest to update all his mods, which apparently was quite a list. I showed him where to get WAU, but he got an error every time he loaded it up. Hopefully this will fix the problem, though no word yet as to whether it has or not.

"There is much pleasure to be gained from useless knowledge." - Bertrand Russell

Alpha is recruiting... go go.

 

Cel

With regard to the Master Targets: In Omen, every mob is essentially a Master Target in that all mobs have their own threat list. The purpose of a Master Target was to avoid adding threat to the threat list that wasn't related to the mob you cared about. With Omen, all you do is target something, and that becomes your personal Master Target.

"There is much pleasure to be gained from useless knowledge." - Bertrand Russell

Alpha is recruiting... go go.

 

Bandagraph

Thanks for the work done on Threat/Omen. I have been playing around with Omen and KTM the last few days and am really happy with the functionality and looks of Omen.

I have a request/question that I didn't see brought up earlier in the thread. Now that there is an ACE Threat library, can we be expecting SWstats to incorporate TPS in the drop down menu? This would be a nice tool to see your cumulative TPS for an entire fight rather than the in the moment updates you get from Omen.

 

Zanthor

Would it be possible to have Omen allow you to open a 2nd window to show threat on your Focus at the same time as your target?

As a tank who loves /focus I'd find that VERY useful.

 

Stopokingme

WAU not working can probably be fixed by your warlock installing the .NET 2.0 Runtime.

 

Kier

For us last night Magtheridon + trash, and Hydross + trash the threat values for Druids were WAY low. Bear form was about 30% of what it should have been and cat form threat was almost non existant (like 3k crits were registering as 50). Hope that helps. Versions are up in my last post.

 

Cel

I'll second the thought that druid threat seems low. We use a druid tank on Solarian, and he didn't show up on the threat meter after the very beginning. We were going nuts on DPS, however, and that may have been why.

"There is much pleasure to be gained from useless knowledge." - Bertrand Russell

Alpha is recruiting... go go.

 

Bobtheorange

This was happening for me last night, also, on my paladin tanking Karazhan. Quite often I didn't show up on the threat list at all, or I had some absurdly low number.

Interestingly, PitBull seemed to have valid values, the threat bars on my frames looked right.

 

Antiarc

I saw the threat list/rebuild occur on Magtheridon last night; I'll be tracking that one down ASAP. It's rather annoying. :P

Anyone who updated last night would have seen very odd threat numbers - one of my libraries got broken (the combat log parser, to be specific) which meant that basically the only threat registered was from gains and heals. That was fixed quickly, but a good number of people ended up with that revision. An update should see that particular (very ugly) problem fixed.

demongr: The destruction threat reduction is implemented, and has been working up till now. What spells were you using that were not being reduced?

 

• Sixteenbit

I love this mod! My computer is crumby enough that I actually see a performance difference when I enable and disable KTM.

Anyway, I don't know if this would be too much hassle... but would it be at all possible to have two different versions, one "stable" version for raiding, and one "beta" version for testing? (I'm not sure what you would call the two.) I've been desperately trying to switch my guild over to Omen from KTM. Last night was our first "official" raid where we told everyone to switch over and it apparently was during the time the bugged library was up. Most people (I'm guessing those who had updated earlier in the day.) weren't having any issues with it, but a few were experiencing the wonky threat number bug which is resulting in posts like this on our guild forums:

Sigh.

 

Jandari

I noticed something odd last night... Omen seemed to be sorting threat bars by the TPS column. I'd be tanking with the most threat, but would be jumping from 1st to 5th in Omen's list based on TPS spikes from other players.

I tried clicking on the Threat column to sort by that - didn't work, and I didn't see any kind of "Sort by..." menu option.

Any ideas?

 

Antiarc

*chuckle*

It's still very much in development. If people are expecting it to be perfect right now, I don't know what to tell 'em.

It shouldn't be able to sort by the TPS column, but that sort of rearrangement may be indicative of another problem. I'll add it to the list to look at with the list rebuild problem.

 

demongr

I didnt use destruction, i used affliction spells, with the improved drain life talent..
Specifically i used: corruption, siphon life, curse of agony, drain life
oh, and i use omen r39812 and threat1.0 r39825 if that helps

 

Antiarc

Err, sorry, affliction, right. The code seems to indicate that those spells should be properly reduced; I'll ping my warlock guy about it and see if he can verfiy it.

What locale do you use?

 

demongr

europe english, not sure which it is, think enGB?

 

lazerpewpew

Violation has the ability to 'record aggro', it says "aggro duration".

I am not sure how well it works though.

 

Antiarc

Hrm. My warlock guy says that the 10% reduction seems to be working as expected.

Cast Corruption. Let it tick once, and see if the threat displayed is equal to (damage caused * 0.9). He says it is. Can you identify specific spells that are not receiving the reduction?

 

demongr

hmm, ok, i will do that

Problem is that i go to raid now, so i cant really cast only corruption and let 1 tick

i'll tell you tommorrow

 

Kier

Sure you can. Just make sure Omen is set to always show yourself and just wait 3 seconds before blowing the raid out of the water in DPS.

 

◊ manly

Well, I just wanted to say that EJ officially made the switch, and as a personal opinion I am totally enjoying Omen. Having threat information per target is a really big plus. Plus not having to set/reset a master target is most welcome.

The only minor note I would mention is that I think by default it should show yourself as a red bar (I know you can right click on your name and set it up, but it just feels like the right default to have).

 

Antiarc

Heh, you guys are brave. I wouldn't quite tell my tanks to solely rely on it just yet.

I have a few lingering issues to work out, so it's almost ready for my stamp of tank-worthiness, but I don't know that I'd quite put it there!