I gave a preview of Omen 2 awhile back before patch 2.4 hit, and we saw just how popular the addon is the other night. It has become almost necessary in the WoW community, and when it isn't working right, it really has an effect.Everyone that has downloaded Omen 2 has noticed that there are some... issues. The author is aware of most of these, so fixes are on the way, but there's only so many hours in a day. Bugs and issues can crop up in strange places though, so it never hurts to report them. There are some minor things you can do yourself to make sure things work smoothly and be confident the problem isn't on your end, so take a look behind the jump for some tips.
First off, if you're having any issues at all and didn't do this before upgrading to Omen 2, my recommendation is to log off of WoW, go into your Addons folder, and delete the Omen folder entirely. This will be sure that no old files remain in the Omen folder from Omen 1.0. Some things, like the threat library Threat-1.0 are obsolete in patch 2.4. This may not have been removed in your original update, and has been reported to cause issues with Omen 2.0. Just wipe out the folder for now.
To simplify: Threat-1.0 is bad. Threat-2.0 is good. If you have Threat-1.0, kill it with fire.
Next, download Omen if you had to clean out the Omen folder. If you didn't need to clear out that folder, check your version by looking at the upper right hand corner of the Omen box. You automatically get notifications if your version is outdated when someone in your guild or raid has a newer version, but if you're checking on this prior to a raid, you can just compare it to the latest posting on WoW Ace. Make sure you have the most recent version each time you encounter a bug, because there's a possibility that has already been fixed in an update. The author has been working day and night to solve everything he can.


The most crippling bug that has been in Omen 2.0 so far is the immense CPU usage by the AOE and Healer Modes. This has been fixed, and you shouldn't need to worry about that issue anymore. It has been throttled properly now, so no more lockups or crashes. If you still see this issue, report it!
Many of the intended features for the UI have not yet made it into Omen 2.0, but rest assured that many of them are still on the way. It can't hurt to submit suggestions to the author, but many of the old features that we've grown to love simply haven't been implemented yet, though the intent is there. Patience is a virtue.
It may be frustrating to bump into so many bugs, but remain vigilant. If at all possible, do not become frustrated. Document what went wrong, write down any errors, and report them to the author. You can either do so over at WoWAce, or leave them right here for me at WoW Insider in a comment to this post, and they'll be passed along.
Keep in mind that all mods run into bugs, especially when they've just been built from the ground up. Omen and its predecessors had extensive testing on the Live servers before they were put out to the public. Omen 2.0(and Threat-2.0) was built from the ground up and wasn't able to have as much development time or play testing, as it was limited to the Fury of the Sunwell PTR and the content being explored on the PTR. The playtesting we, as a community, are currently doing with the mod will insure bugs are found and solved quickly and easily. Though it's a bit of a pain now, it's all going toward making Omen 2.0 better than it ever was.
Follow the few simple steps above, update Omen 2.0 often, document what goes wrong, and come on back to report it. You'll run into some hitches, but keep at it. Things will settle down, it may just need more than the two days it has had so far.
Oh, right! If you don't like the sound that comes with the threat warning, you can turn that off. Open the Omen configuration menu(click the wrench), go to Modules, then Single Target, then Warnings. Voila!














Reader Comments (Page 1 of 2)
3-27-2008 @ 7:09PM
Awryin.com said...
I had problems with Omen too, turn out it was the Skin.
options, skin, changed to classic and it now works perfect.
Reply
3-27-2008 @ 8:42PM
PeeWee said...
You probably had the same error described above. Just drag up the window a bit (see picture above) and it snaps into a nice fine window.
As far as I've seen, the only bug so far is having a druid tank, who sometimes goes bonanza in the threat generation and pops away to a couple hundred thousand K of threat. ^^
3-27-2008 @ 7:27PM
Slayblaze said...
I also went into my WTF folder and cleared any Omen Saved Variables files out of the Account folder, then took it even a step further and erased the omen files out of each individual character I have. The path looks like this:
(Drive letter) - (Game folder) - World of Warcraft - WTF - Account - (your account name) - SAVED VARIABLES
..and delete "omen.lua" and "omen.lua.bak"
I then progressed using the same path as above only instead of the SAVED VARIABLES folder I went into:
- (Server name) - (Character's name)
...and deleted "omen.lua" and "omen.lua.bak" also
I then reinstalled Omen from the WowAceUpdater and it works perfectly now. I did not delete the Threat 1.0 folder but I'm doing that next too just to be safe.
That solved all my corruption issues with Omen2.
Reply
3-27-2008 @ 11:45PM
Eric said...
Thanks for this. I just switched to Wowmatrix and thought that it had screwed Omen up for me. updated, deleted Threat1.0 and I'm good.
anyone reported issues with Parrot? Ever since the patch, I have no functionality, even though I have the latest version.
Thanks for all the help wowinsider
Reply
3-28-2008 @ 5:14AM
Kees said...
Parrot isn't being developed anymore, check the wowace forums for more info 'bout that.
Bloodboil was very 'interesting' to say the least, without a decent threatmeter :D
3-28-2008 @ 12:40PM
hosehead said...
WHAT NO MORE PARROT? OMFG.
PLZ TO BE REPLACING. GOING TO READ FORUMS NOW. WORTHY OF ALL CAPITALS. I AM QQING.
PARROT WAS TEH SEXYNESS. CAW!! IT ATE MY CRACKERS.
3-28-2008 @ 6:52PM
dan said...
Link please. I find that hard to believe given the current files.wowace.com page has parrot just getting an update a minute ago.
3-28-2008 @ 10:03PM
Eric said...
Checked it earlier, all updates to v1.0 are library updates. The addon itself is out of development :(
3-28-2008 @ 1:54AM
manmeat said...
Anyone know how to turn off that sound effect when u pass 90% threat? Its a huge thundering sound, i have a hunter and this happens very often while soloing when i pass my pet's threat, its like boom boom boom boom while killing a level 9 wolf, and its way loud too T.T ... BOOOM!
Reply
3-28-2008 @ 2:21AM
schwonga said...
The sounds can be altered, turned off or whatever by clicking the little tool icon and going thru the options. I forget what its called exactly, you may have open folders (the plus marks) in the options window and scroll around a bit to find it.
The real question/problem I am running into is why wont my 2.4 dmg meter work! I use recount (perservation) but my roommate who uses a different, all be it simpler, dmg meter says his hasn't been working at all ether. None of the guildies I run a lot of instances/raid with have their dmg working ether.
Anyone know whats going on?
3-28-2008 @ 7:08AM
Xoshe said...
The odds are that your buddies don't have updated versions. Remember that damage meters are reliant on the combat log for info. The combat log is nothing like it was before, so all the old code won't be able to get any information.
3-28-2008 @ 10:59AM
Blackhorn said...
Hey there, Hunter! As mentioned in the post, you can change or disable the warning sound. But you may also want to change the warning threshold to 110%, giving you a less frequent warning. I mean, we're hunters standing at max range. Mobs won't make a run at us unless we hit 130% of our pet's threat. Warning us over and over again because we've exceeded 90% is a bit much for a ranged class fighting world mobs with a pet.
3-28-2008 @ 3:37AM
souvlaki said...
I had an issue with using Sunder Armor on my warrior on Wednesday (EU patch day). Each time i'd use it, an error message would pop up. Yesterday i reinstalled it (don't know it that was a new build) but i played my lock so i can't tell if it has been fixed.
Reply
3-28-2008 @ 4:23AM
evoker said...
The only major problem we've had was with Bloodboil. Threat was completely messed up. When I see the hunters' pets being 4th and 5th in threat after our 3 tanks I can guess pain is coming my way and it did :(
Scorched my way through the 2nd time :D
Reply
3-28-2008 @ 7:53AM
Dakira said...
Just adding my thanks to the Omen developer (please pass that along).
Working for free and developing addon's is not easy. The wow community owes you a huge debt of gratitude for providing cool tools that Blizzard probably didn't even think about in there initial development.
Thanks!
Reply
3-28-2008 @ 9:28AM
MartinC said...
First off, thanks much for developing and putting in all the hard work with Omen. I've done a few small addons myself (nothing near as epic as Omen), so can somewhat sympathize with all the rants and complaints.
One questions, was the party/raid/guild version checking removed for a technical reason, or perhaps just not implemented yet in Omen 2.0? As a raid leader, that's one of the first things I do when people join in - make sure they have Omen and that's it's updated and active. Presently, I have no way of doing that :-(
I think it was "/omen partyrevs" or something like that in Omen 1.0?
Reply
3-28-2008 @ 9:33AM
jst8 said...
The thing I really miss (unless it's there and I just can't find it) is being able to change the colors of each bar separately. Following advice I found on WoW Insider, I made my pet's bar green and my bar red. Green bar on top=good. Red bar on top=bad.
I don't think I can do that in Omen 2. Wah.
Reply
3-28-2008 @ 10:35AM
Fimlys said...
I'm enjoying the new omen, thank you. I cannot get the Healing mode to work though. We use CT_Raid and the only options for that mode are BlizzMT and oRA2 MT. Unfortunately, we can't seem to find where to set the "BlizzMT". We set the MT using CTR and I get no bars at all in there.
Also, make sure everyone in your party/raid has the same version if you can. Seems that some older versions don't communicate with the newer one so you don't get information for those people.
Reply
3-28-2008 @ 5:40PM
Josh said...
You set the blizzMT through the blizzard raid ui.
I don't use it myself, but i think you just right click on the person you want as the tank and set them as the tank.
3-28-2008 @ 12:19PM
Runstadrey said...
It looks like the author has been burning the midnight oil while we were snugly abed. A new version was released just minutes ago - r66694.
Thank you Omen author, whoever you are.
Reply