If at all possible, please SLOW DOWN the release of new versions of Omen. I don't know exactly what is going on, but when there are 3 or more versions of Omen released within an hour, it causes us all many headaches. It seems consistent that we will prepare for a raid, everyone will download the newest version of Omen during the hour prior to raid, and they still won't be compatible.
There's the major misunderstanding. It is not released. It is committed to the development repository.
And everybody that uses WAU sometime accepted that what they download with it is Beta quality software and things may (and will!) break.
The latest released version of Omen is on wowinterface.com and is ~24 hours old.
On another note, may I suggest that you change your raids process of updating addons?
Put up a file that everybody of your raid downloads, so everybody uses the same version. At least that solves your incompatibility issues.
We noticed similar problems tonight with Bloodboil and 68254. After a few wipes because no one could see each other on the list, we all updated and relogged. The next attempt everything was working fine. The attempt after that, the ranged dps could not see any of the tanks (2 warriors, 1 druid). The tank druid mentioned on vent that she could only see herself, not the other warriors. Not sure about the warriors, whether or not they saw themselves.
Okay now we've more or less fixed the problem, at least it seems that way!
First, we made sure ALL raidmembers deleted the Omen addonfolder, AND all the omen.lua and omen.lua.bak files in the WTF folder;
then we all downloaded Omen rev68250.3, and everyone selected 'Blizzard MTs' as datasource in healermode!
All that together made it possible to get an accurate threatlist on the 2rd bloodboil try,
and we got our firstkill ^^
Only at the beginning of the 2nd try, 2 of the 3 tanks were at the bottom of the list, but they got on top after some phases.. the druidtank always was on top, and as I just saw in the video I made, the tank who has the aggro isnt the first on the list!
but at least all 3 tanks were on top after some time ^^
The suggestion to post a direct link to a certain version such as http://files.wowace.com/Omen/Omen-r68561.1.zip is a great idea and is what we do. Problem we also found were some people were using programs that had old threat 1.0 and 2.0 libraries being loaded. Recount and pitbull to name 2. Sure there may be other programs out there causing the same issues. Not everybody updates all their addons sadly.
I'm thinking those leaving a mod like Assessment on (which used threat 1.0 i think) could have probs too?
During the badge runs, i've noticed Omen doesn't seem to reset threat on bosses like Attumen (when he joins up with Midnight, i think the threat should reset?), or Nightbane (threat should reset during each phase right?). On Omen however, the threat doesn't appear to reset. Perhaps its still the issue with people having different versions although most ran the same one. Or Omen may be correct and i'm wrong.
I'm thinking those leaving a mod like Assessment on (which used threat 1.0 i think) could have probs too?
During the badge runs, i've noticed Omen doesn't seem to reset threat on bosses like Attumen (when he joins up with Midnight, i think the threat should reset?), or Nightbane (threat should reset during each phase right?). On Omen however, the threat doesn't appear to reset. Perhaps its still the issue with people having different versions although most ran the same one. Or Omen may be correct and i'm wrong.
17 pages of posts so I'm sure my issues have already been brought up. Also, maybe these issues are in the works and will be resolved shortly.
Primarily as a healer the current implementation of Omen isn't very useful to me. The main problem is that I have to tab around to see threat where I used to see threat even when nothing was selected. As a healer I've got most everything set up to not require me to target things (Click cast for instance), this allows me flexibility in targeting - I don't have time to target around to see the threat. Hoping a better healer view is implemented soon!
Thanks for the great work with this addon and the highly responsive updates!!
Omen worked great tonight in Mount Hyjal. That "ignore mobs that have no death message" must have done the trick. No more lockups. Blame the error on blizz. Will be addressed next patch supposedly. Perfect fix til then.
Sometime in the last 2 days, my Omen seems to have decided that I do not have FuBar installed and is attaching itself to the minimap. Under the options panel, trying to uncheck the "Attach to mini-map" option does nothing, the checkmark will not go away.
I tried removing my SavedVariables/Omen.lua(.bak) files. Both the account-wide and character-specific ones. Didn't fix it. Any suggestions?
Primarily as a healer the current implementation of Omen isn't very useful to me. The main problem is that I have to tab around to see threat where I used to see threat even when nothing was selected. As a healer I've got most everything set up to not require me to target things (Click cast for instance), this allows me flexibility in targeting - I don't have time to target around to see the threat. Hoping a better healer view is implemented soon!
The root of this is that the old Omen wasn't actually showing you threat - it was showing you a guess at threat, based on attempting to combine threat for multiple different mobs and whatnot. Since the new Omen can provide exact data for a specific mob, in single-target mode that's exactly what it does. Since you don't have a mob targeted, it has nothing to show you threat for.
If you want threat for tank targets, try having your raidleaders set up maintanks either in oRA2 or blizzard maintanks, and using Healer mode.
I've also suggested to Antiarc that it be possible to have single-target mode draw its unit id for threat from your focus target if you so choose, so that you could focus on a mob and see threat on that mob without targeting anyone.
prolly been said alreay but OMEN isnt saving settings between sessions, everytime i log in and out I have to reset thisgs like, grow up, Autocollapse basically anything I customize, and yes i created my own profile,
A friend of mine currentyl recieves a backdoor-warning in his omen-directory, claiming that "embeds.xml" has a keylogger attatched to it.
He updated with externals via WAU. I rechecked this file in my directory (I update without externals via WAU) and can't find it.
Actually, this file is present in all other AddOn-Folders and has a size of 1 kB. His file has 2 kB.
Anyone has a clue what happened and if it's really dangerous?
Most likely his AV is just false-flagging it. Its an XML file... a text file... they all do the same thing, which is load the necessary libraries that the addon needs, to function. it is called from the addon's .toc file. If you run disembedded, it should be basically empty.
Omen doesn't use an embeds.xml file currently, so chances are it's an embedded library's embeds.xml that's triggering it. However, those files are just plain text and incapable of carrying a backdoor.
If you can, get the full path of the file to me. I'm curious which library's embeds.xml is causing that.
69623 by charon on 13 April 2008, 15:09:48 -0700 (6 hours ago) Omen: merge changes from my branch
- AOE mode bugfix (69619) - AOE tank mode added (69187, 69613, 69618)
- warn and enable if manually toggled but on standby (69381)
Let's just say, I love you ^^
... there's just one problem: It won't show me any bars in aoe mode.
... thanks for the fix! Now the games shall begin.
There's the major misunderstanding. It is not released. It is committed to the development repository.
And everybody that uses WAU sometime accepted that what they download with it is Beta quality software and things may (and will!) break.
The latest released version of Omen is on wowinterface.com and is ~24 hours old.
On another note, may I suggest that you change your raids process of updating addons?
Put up a file that everybody of your raid downloads, so everybody uses the same version. At least that solves your incompatibility issues.
Okay now we've more or less fixed the problem, at least it seems that way!
First, we made sure ALL raidmembers deleted the Omen addonfolder, AND all the omen.lua and omen.lua.bak files in the WTF folder;
then we all downloaded Omen rev68250.3, and everyone selected 'Blizzard MTs' as datasource in healermode!
All that together made it possible to get an accurate threatlist on the 2rd bloodboil try,
and we got our firstkill ^^
Only at the beginning of the 2nd try, 2 of the 3 tanks were at the bottom of the list, but they got on top after some phases.. the druidtank always was on top, and as I just saw in the video I made, the tank who has the aggro isnt the first on the list!
but at least all 3 tanks were on top after some time ^^
During the badge runs, i've noticed Omen doesn't seem to reset threat on bosses like Attumen (when he joins up with Midnight, i think the threat should reset?), or Nightbane (threat should reset during each phase right?). On Omen however, the threat doesn't appear to reset. Perhaps its still the issue with people having different versions although most ran the same one. Or Omen may be correct and i'm wrong.
Certainly didn't reset on Nightbane last night.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThat feature has not been implemented in Omen2 yet. Be patient, Antiarc has said it will be coming.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWhat is especially curious here are the double messages for failures. Here's another example:
Primarily as a healer the current implementation of Omen isn't very useful to me. The main problem is that I have to tab around to see threat where I used to see threat even when nothing was selected. As a healer I've got most everything set up to not require me to target things (Click cast for instance), this allows me flexibility in targeting - I don't have time to target around to see the threat. Hoping a better healer view is implemented soon!
Thanks for the great work with this addon and the highly responsive updates!!
Great job dudes
I tried removing my SavedVariables/Omen.lua(.bak) files. Both the account-wide and character-specific ones. Didn't fix it. Any suggestions?
The root of this is that the old Omen wasn't actually showing you threat - it was showing you a guess at threat, based on attempting to combine threat for multiple different mobs and whatnot. Since the new Omen can provide exact data for a specific mob, in single-target mode that's exactly what it does. Since you don't have a mob targeted, it has nothing to show you threat for.
If you want threat for tank targets, try having your raidleaders set up maintanks either in oRA2 or blizzard maintanks, and using Healer mode.
I've also suggested to Antiarc that it be possible to have single-target mode draw its unit id for threat from your focus target if you so choose, so that you could focus on a mob and see threat on that mob without targeting anyone.
He updated with externals via WAU. I rechecked this file in my directory (I update without externals via WAU) and can't find it.
Actually, this file is present in all other AddOn-Folders and has a size of 1 kB. His file has 2 kB.
Anyone has a clue what happened and if it's really dangerous?
Most likely his AV is just false-flagging it. Its an XML file... a text file... they all do the same thing, which is load the necessary libraries that the addon needs, to function. it is called from the addon's .toc file. If you run disembedded, it should be basically empty.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIf you can, get the full path of the file to me. I'm curious which library's embeds.xml is causing that.
Let's just say, I love you ^^
... there's just one problem: It won't show me any bars in aoe mode.
... thanks for the fix! Now the games shall begin.
May want to look into that.