Antiarc - the drag-out TPS comparison bar needs a couple of features added:
1) Lock it in combat at the very least so we aren't dragging it all over the place
2) or add a menu option to lock it
3) Needs scaling, badly. The thing is frigging gigantic.

I'd like to second this. I don't know if it's since the latest revision or what but two days ago the bar was about 2x the size of a normal threat bar... and now it's the size of the entire window. It literally took up about a 5" by 5" space on my screen and I had to shut it off.

Not sure if this is an OMEN/Threat 1.0 issue really, but I've been noticing lately that on the Kael'thas fight, I get extreme lag when I have my current target selected with Omen visible, but as soon as I click off it or hide omen, it goes away. I have a top of the line machine and this hasn't been a problem until recently so I'm pretty stumped. Am I the only one?

Isn't there a resize corner in the bottom right, or is that just with the ktm skin?

Having a lock option would be nice, additionally it'd be nice to have 1 static comparison bar that always shows you versus the current threat holder. Only other minor issue I've had with it is that the font is exceptionally small w/ no apparent way to change.

I'll add a lock option.

There's a scaling grip in the bottom right corner. It may be getting hidden behind the other textures, though - I'll need to check the strata. Regardless, click+drag in the bottom right should work.

There isn't any way to change font on the pullouts right now, but there will be eventually =)

Very curious issue. I don't see any immediate reason why this would be the case, but if you're able to noticably fix the lag by hiding the Omen window, it very well may be something I'm doing wrong. Does it only happen on Kael, or on all targets? Only in combat, out of combat, both? Can you narrow down the conditions for me?

It may be that there are so many threat updates happening that the draw code is slowing you down. Try turning off bar animation and see what that does for you.

I'll try to narrow this down further for you next time I notice it happening. Thanks for the prompt reply. Glad to know you guys are working very hard at this. It shows!

Yeah, there is. I've seen it get hidden behind the main bar texture, but I haven't replicated the issue since. I'll take a second look.

Ok I've found it now, you're right its behind the texture. Very hard to click right now.

Although I haven't gone quite as far as deleting my Omen SavedVariables, I have this same problem with the latest (as of yesterday) version of Omen. I rather liked the smooth growth from before, but in the new version my bars are really jumpy, even with the TPS updates turned to the fastest setting and "Animate Bars" on. Checking/unchecking "Animate Bars" doesn't seem to be doing anything honestly.

On the MD bug I found... the hunter's name is Chased, and his pet is also named Chased. This could be the problem, cause Omen also colors Chased brown, like he's a pet.

In testing the latest build of Threat/Omen (40787/40570 respectively), I found that the threat generated by torment is now underestimated. I pulled aggro at ~140-143% (pulled at 143%, hard to tell exactly when it was). Same thing happened at 143% when I took my only +shadow piece off.

Putting your pet's name the same as your own or any other player's name is not a smart idea. SWStats doesn't like it, Omen doesn't like it... there's really no "magic" way a combat log parser, etc, can tell the difference between the two.

Tell Chased to abandon and try again with a better name choice.

Bugger. I changed the pet scaling code, and while it's really accurate for hunters now, it would appear that the same scaling formulae don't apply to locks. I'll figure it out.

This is new then. It never did pre-TBC (it didn't show up in Combat Log back then either). You tested this both with and without intensity?

I only test it with Intensity, I think. Do you think that the +10 from Intensity is generating threat, but the rage gained over time isn't?

I seem to remember testing it, and cancelling enrage at different periods granted different amounts of threat.

Not sure what % aggro loss you set for Void Reaver but it's off. Felt like 7.5-10% off too.

The best thing would be for a guild that still has issues on this boss to modify the value in increments of 2.5% until it makes sense.

Was using it all last nite throughout Gruul, Magtheridon, and SSC. One thing I noticed is that I don't know where I am on the charts. Is there an option that will highlight my name in Red or something (i know theres the arrow and all but it's hard to notice).

Furthermore I was noticing that this addon was taking up a larger chunk of memory than before. 1.5mb or so in comparisson to ktms 1mb. i know that's not allot of memory but one of the features was that it would run with a lower overhead.

this was using last night's build of both omen and threat lib.

What was the bug? Did you set Mag as the KTM main target? Was it healing threat issues?

Which direction was it off in? 7.5% too high or too low?

Was Magtheridon set to the master target, or was there no clear done between phases 1->2? If the tank had threat accumulated on Magtheridon from the Summoners, then it'd be off, naturally. However, my main's a rogue and I've not noticed any discrepancies in rogue threat calculations at all.

Do you believe that ThreatLib was off in this case, or that KTM was over-estimating the tank's threat? If you can provide discrepancy information, I'd really appreciate it.

Right click your name and you can set all the settings you want

One of the disadvantages to using embedded libraries is that the first addon to load them gets credited for them. If Omen's the only Ace2 library you're using, then it'll incur more memory overhead due to the fact that it's loading all these various libraries to support it. However, if you're loading multiple Ace2 addons, then all addons can use that addon's copy of the library, which means that your overall memory usage is lower.

You can see the memory usage of Threat/Omen by running them "disembedded" - that is, install without libraries in WAU, then install the required libraries as addons. This causes the libraries to be credited for their own RAM usage, and Threat/Omen to only be credited for the RAM usage they actual incur. I run disembedded for development to speed up UI load time, which also gives me a better picture of Threat/Omen's overall RAM usage. Right now, both addons seem to hang out in the 200-300kb range, which isn't too bad, though there's still likely room for improvement. The ultimate goal, though, is lower CPU usage - Threat's design goal is that it consume only the resources required to handle your current environment, be that idling, in a battleground, in a 5-man, raiding, whatever. Still lots of work to do in that direction, but I believe it's getting there.

It was 25%, then people seemed to think it was 30%, so I don't even know at this point. With luck, my guild will start on on TKE within a couple of weeks, so I can test it firsthand. Any data you can provide would be most welcome, though.

Two possible issues; one, there's something funny going on with Vampiric Touch. I haven't identified the exact cause yet, but I am aware of it and will be tested it extensively to ensure I get proper numbers.

The other was that global threat wasn't being reported properly back to other people after a mob threat clear; I committed fixes to that last night. This particularly affected shadow priests, due to their extremely high global threat generation through VE/VT.

Void Reaver's Knock Away should be a 25% reduction, as opposed to Threat's 30%. Honestly, we simply assumed VR was more like Onyxia, after our first attempt's meter. Executing 25% (instead of 50% default) Knock Away reduction on KTM has appeared accurate ever since, at least to the point where switches are predictable and accurate.

Funny thing is that it was 25%, and was changed due to inaccuracies.

--

Also, Shadow priest threat appears to be over estimated. Any thoughts as to what might be the cause of this? Our shadow priest tends to be over the "aggro gain" line by 10-15% from time to time and still not pull aggro.

Maybe some -threat talents that were supposed to stop work on shadow still do?