Looking at all the asterisks in there I see a lot of people using KTM, Omen simply displays the values it received from KTM in this case, so I doubt this is an issue with Omen.

KTM doesn't keep a separate threat table per target, but Omen can only display the total threat value KTM sends out.

I think you may not have the master target set on KTM; every player above Hexem has an asterisk.

That just won't help on multiple mob fights, though. You'll be ignoring the tank's threat until you get to the new target and reset master target.

I downloaded the latest version from http://files.wowace.com/Omen/Omen.zip and discovered my OWN threat doesn't appear on the meter when I'm in a group. I can see the other members threat, but not my own, which seems very strange.

got the same issue vice versa..

i grouped with a warrior last night for questing. havent seen him once displayed in omen the whole time..according to that i got a few questions:

does omen only show data from players which have installed omen too ?
does that mean that if i group with someone that doesnt have installed any threat meter i wont be able to see his threat in omen ?

Correct.

They need to be running either Threat or KTM for Omen to show their threat.

A common answer: update ALL your ace2 addons (with wowaceupdater it's just a click), it should work then.

Not always, if something goes from an external addon to a library, or something similar happens, WAU may not fix it.

For example, pitbull_barfader used to be a stand alone addon, and when it was moved into part of the pitbull package, it errored everyone still using the stand alone version (Obviously because the addon no longer worked), but WAU didn't realize that this addon was no longer in use, so if you just updated via WAU, it'd never get rid of it.

For the most part though, WAU is very good at what it does :P

Thanks for the correction Marroc.
In my guild as an "advertiser" of Omen I usually say to my guildmates who has this error to update all ace2 addons. It has always solved the problem

Shouldn't be a problem unless they're updating from revision 2x or earlier, I think.

Threat got made a library very quickly, so anything fairly recent should haven no issues updating with WAU.

I've been having a window placement bug for a couple weeks and finally was able to track down what was causing it:
Omen is not using its window placement setting when run in conjunction with AddonLoader. When Omen is loaded through the default settings in AddonLoader, the Omen window and any pulled out bars reset to the middle of the screen when you first log into the game. This problem rears its head when logging in all characters for the first time after starting the WoW client. Reloading your UI appears to properly save the new locations in layout-cache.txt and logging in and out of WoW without quiting retains the window placements. Changing the override in AddonLoader to Always appears to resolve this issue.

Omen r44409
AddonLoader r43492

I'm not really sure what you're going to get out of this or if its fixable with the information I'm giving you.

Basically, my guilds main tank never shows up on Omen. I believe he's using KTM, but he has an older version of Omen installed according to my version check. Is there anything that can be done to solve this?

Tell him to delete Omen or Update it.

Correctamundo.

I know omen currently shows the red "You're out of date" numbers. But if you're running Omen and people are running a newer AND incompatible version, would it be feasible to have it pop up a dialog (similiar to deadly boss mods) one time only during the session that says "Hey! You're not going to be synching with everyone unless you update now!"


Old versions are one thing, but incompatible versions are useless.

There hasn't been a revision that's made things incompatible in a LONG time (somewhere in the r3's). If everyone is running a r4x version, you shouldn't be having this issue :P

Well, the specific reason I haven't made a stable release is exactly that: I don't want to encourage people to install a version and then just forget about it and never update it, until I'm reasonably sure that they can do so and not need to update for a while.

Even if I were to make said incompatibility change, they wouldn't see it...as they'd need to upgrade to see it. The goal is to not have any incompatibility changes once Threat and Omen have a stable 1.0 release.

Edit: To explain the incompatibility flag, it's essentially set any time I make a change to the protocol, or fix a particularly nasty bug that dirties the raid's data, as opposed to only your local data. One example might be the translation fix I made a while back: people were getting the wrong translations for cross-locale groups in situations where someone was rapidly switching targets. Once this was fixed, prior versions were marked incompatible, as one person running that version (or older) would pollute the raid's translation tables, making the entire raid's data unreliable. It will most certainly not be used the vast majority of the time.

For reference's sake, do you have a timetable in mind to move Omen to a stable release?

The last few builds have all seemed relatively bug-free.

As soon as possible, really. It's mostly there, but I'm ironing out a last few bugs. I fixed the one with weird pet threat numbers today (yay!), have a couple of library upgrade issues to look into, some optimizations to version queries, a weird taunt issue on Al'ar, warlock pet scaling, and some GUI issues with Omen left.

my first post here :P

http://img519.imageshack.us/img519/8...7220620rs6.jpg

that happened two times with two different versions of omen, both times i targeted the elementals just when they spawned.
the translation is correct, unbekannt is wrong, it means unknown.

i'm sorry if someone else reported that bug already. >_<

If there's anything we can be specifically doing to help test any remaining issues, let us know.

(I can't help with A'lar just yet. >.<)

Thank you, Seph123. I think I need to special-case "Unknown" (and its localizations).