If you're updating with WAU, just make sure to grep it again and restart the game. (WAU should fetch all deps on its own)
If you don't use WAU, make sure you have a copy of LibBabble-Boss-3.0 and LibBabble-Spell-3.0.
I suppose all of you are running dis-embedded, because i just tried the embedded version of Omen and it worked fine.
Update all your mods using Threat-1.0, and make sure to restart your game!
(Also, if the error persist, maybe its the addons fault that includes Threat, i see GridStatus* for example here)
how do i know which addons use threat 1.0 or not? i just use the mac version of the wow ace updater and update my addons with it. i never select libs or anything... i just see omen up there with a new update and install it. and now it's broken. do i need to download ALL the ace addons i have to correct this problem?
okay, but i am not using recount. i use assesment :s
Well the way I understand it is that a 3rd party mod (besides Omen) is messing with the Threat-1.0 library. I'm my case it was Recount, but there are also other addons that use Threat-1.0 like, Aloft, Assessment, PitBull, and Violation.
okay, so it should solve once there's a new update on the wowaceupdater thing. i ran the updater again and just checked ALL the ace mods i have so i got fresh copies or everything. i guess that should fix it as well.. otherwise i have to wait for a new omen update. ow well.... can't play tonight anyway.
btw... heroic arcatraz (daily on eu servers) was a bitch as lock without Omen :)
I'm getting this error with any version of Omen I try
[2008/02/18 13:32:08-100-x2]: Omen-2.1r55025\Omen.lua:528: Bad argument #2 to `IterateGroupThreatForTarget`. expected "string", got "nil" (nil)
<in C code>: in function `CameraOrSelectOrMoveStop'
<string>:"CAMERAORSELECTORMOVE":4: in function <[string "CAMERAORSELECTORMOVE"]:1>
I know I've seen this being discussed here, but haven't found any answer which worked for me.
I updated Omen last sunday and it stopped working. The addon shows, can be moved around the screen, customized, etc. There seems to be some minor bugs, for example if I click 'Publish to KTM', I have to toggle showing Omen on/off for the check-mark to appear next to it. The main problem is, like reported earlier, that the bars themselves are not showing, neither for me or anybody else in the raid. I can see test bars if I choose to show them, but real, functional bars never show.
If this can be of any help, I have used MacAceUpdater to make the update. Switching back to an older version of Omen as not worked. Deleting and reinstalling the addon has not worked. Deleting the Omen's SavedVariables file, deleting the addon folder and reinstalling it has not worked. I have installed, for the first time, Decursive and Recount along Omen. I've read Recount could cause a problem with Threat-1.0, but I have deleted Recount, Decursive, installed everything with 'Babble' in it (as proposed on the Recount thread), reinstalled Omen, still not working.
Anybody got an idea on how to fix this?
EDIT : Ok, after further reading/testing, I have found Aloft to be responsible for the conflict with Omen. Hope this helps somebody.
Thank you very much Nevcairiel. I was using WAU and Omen worked, after sunday stopped but when i used your advice and downloaded LibBabble-Boss-3.0, it works perfect again, i didnt have it installed before. Once more thank you.
The problem is that Threat-1.0 uses libraries X, Y and Z. Now a few days ago, Y and Z were upgraded to use A and B.
All these other addons like Recount, Assessment, etc that also include Threat-1.0 in their distribution, their authors did not upgrade their libraries from Y and Z to A and B. Hence you get errors if you use these addons that aren't updated. Simple as that.
i just downloaded the threat separate addon, pull the folder out of it and placed it inside of omen, pitbull and assesment. i am now hoping this will solve my problem until the wuggers of pitbull and assesment fix their stuff. i only hope the shit is caused by different embedded threat libs inside the omen, pitbull and assesment (now all new)... if not.. well then i have to wait for updates.
i now downloaded the threat-1.0 lib from files.wowace.com and installed that one as a normal addon. it's all working now :) i will revert back to the old set-up once problems are fixed, but this is good since we're raiding tonight :)
So, I'm having the following problem, which is shared by some of my guild members: Omen is not tracking threat correctly some of the time.
For example, I pulled aggro off the main tank on Gorefiend on Tuesday (having updated Omen to the latest version as of 7pm EST), while I was showing up at 80% of the main tank's threat. There were people listed above me in threat who did not pull. The DPS were all standing in the same place. I play a hunter, if that's relevant. I mean, maybe Omen didn't pick up that an FD was resisted, but it's happened a few times, and two to three times on Gorefiend in particular.
However, it happened to a feral druid on Rage Winterchill last Sunday, so I don't think it's a problem that's isolated to hunters. I first started noticing this behaviour a few weeks ago. I've grown to depend on this lovely crutch, and now I'm finding that sometimes someone has sawed half way through it and I fall flat on my face.
I realize this post isn't much help for figuring out where the problem is, but I figured recognizing that there is a problem is an important first step.
Unfortunately i have developed a very annoying and quite large problem concerning threat calculation. There are several parts to this issue, and it all stems down to the result of the error code i get. On occasion Omen will work perfectly, but majority of the time my threat is vastly exaderated. For example, a mind blast generating 15k of threat. Sometimes it will only be wrong for the fist few attacks and then over the rest of the fight it'll be correct, but on the other hand at the end of killing a 25man mob i could be on 89k threat and the main tank on 23k. Also my party/raid member can not see me on there meters.
As i said before i believe this all stems down to one error which is most like due to windows vista.
Interface\AddOns\Omen\Libs\Threat-1.0\Threat-1.0.lua:1358: attempt to call method 'SendCommMessage' (a nil value)
Other things you might want to know: I'm a Shadow Priest, i have the full 25% less threat talents. Im running Windows Vista, and have tried several different versions of Omen including getting a mate to send me the one he is using with no issues.
Thank you for your time.
I hope to hear from you soon, and that there is a simple fix. As having to hold back on dps when fighting a boss that can enrage is not good.
I'm having a specific issue where threat by the MT is shown as double what it actually is.. I start getting flashing screens and audible warnings for "passing 90%" (which is what I set it to alarm at..) when I'm at ~45% of the MTs threat.
What might be causing this doubling in visually reported threat?