It looks like the background color for the title window and the bars window are bound. I can't change one without it changing the other. I was trying to make the title window transparent but leave the bars window background at 100% alpha.
Secondly, I'm having a hard time trying to figure out how to save my settings and then re-applying them to another toon. It seems when I chose the "Load Settings" or whatever its' called, it lists all my saved settings, but it does not change anything. I'm just trying to figure out how to have one template that I can just reuse over and over for all my toons without having to manually do it each time...
Go to the profiles section and select the Default profile. Change any settings that need to be changed.
Log on your other toons and then load the Default profile.
There seems to be a slight litte problem with language of the WoW client. I'm the only one in my raid who uses enGB client, all others have deDE client. They all get their threat shown, but in my Omen there is nothing, really, really nothing. I don't get any bars shown up, and I have always the same version as my raidmatess, we update all together just 1 minute before the raid starts. I don't know why this happens or when, my bugsack doesn't show me any errors with Omen or ThreatLib, so where is the problem? I pulled aggro yesterday when we were fighting Anetheron and that sucks really hard, everybody was blaming me for this.
EDIT: What I found out is that on a version check, my version showes up as Unknown to any other and any other people in my raid show up as Unknown Version when I do a version check.
EDIT2: I checked my Addons folder and found 2 other Addons using Threat 2.0 or they have a threath.lua: DaHud with DaPortrait and Aloft and a third one: CowTip. Maybe any interference by them?
EDIT3: Found errors for Omen2/Threat2, that was in raid yesterday in Mount Hyjal:
[2008/04/04 21:05:07-804-x2]: Omen-Omen r68051 / Threat-2.0 r68050\Libs\Threat-2.0\ThreatUtils.lua:180: Invalid memoization: CLIENT_INFO
Omen-Omen r68051 / Threat-2.0 r68050\Libs\Threat-2.0\ThreatUtils.lua:180: in function `Memoize'
Omen-Omen r68051 / Threat-2.0 r68050\Libs\Threat-2.0\ThreatUtils.lua:213: in function `SendComm'
Threat-2.0\Threat-2.0.lua:718: in function `PublishVersion'
Threat-2.0\Threat-2.0.lua:351: in function <Interface\AddOns\Omen\Libs\Threat-2.0\Threat-2.0.lua:325>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0\AceTimer-3.0.lua:140: in function <...face\AddOns\DaHud\libs\AceTimer-3.0\AceTimer-3.0.lua:114>
---
[2008/04/04 21:10:56-804-x3608]: Omen-Omen r68051 / Threat-2.0 r68050\Libs\Threat-2.0\ThreatClassModuleCore.lua:706: attempt to call field 'inCombat' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceBucket-3.0\AceBucket-3.0.lua:87: in function <...ace\AddOns\Omen\Libs\AceBucket-3.0\AceBucket-3.0.lua:80>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceTimer-3.0\AceTimer-3.0.lua:142: in function <...face\AddOns\DaHud\libs\AceTimer-3.0\AceTimer-3.0.lua:114>
---
I've been having problems with omen - such as it not even showing up even when enabled in addons (I type in /omen for example and only get the "please type in /help ..." stuff). I installed threat 2.0 separately, b/c for my comp, it seems that I need to install every Ace library separately. Now omen shows up, but all I get is this (see screenshot). Any help would be appreciated.
Here are some errors:
Omen\Bar.lua:10: Cannot find a library instance of "LibGUIDRegistry-0.1".
Ace2\AceLibrary\AceLibrary.lua:49: in function `LibStub'
Omen\Bar.lua:10: in main chunk
Omen\Modules\SingleTarget\SingleTarget.lua:7: Cannot find a library instance of "LibGUIDRegistry-0.1".
Ace2\AceLibrary\AceLibrary.lua:49: in function `LibStub'
Omen\Modules\SingleTarget\SingleTarget.lua:7: in main chunk
Omen\Modules\AOE\AOE.lua:7: Cannot find a library instance of "LibGUIDRegistry-0.1".
Ace2\AceLibrary\AceLibrary.lua:49: in function `LibStub'
Omen\Modules\AOE\AOE.lua:7: in main chunk
Omen\Modules\Healer\Healer.lua:6: Cannot find a library instance of "LibGUIDRegistry-0.1".
Ace2\AceLibrary\AceLibrary.lua:49: in function `LibStub'
Omen\Modules\Healer\Healer.lua:6: in main chunk
Omen\Modules\Overview\Overview.lua:6: Cannot find a library instance of "LibGUIDRegistry-0.1".
Ace2\AceLibrary\AceLibrary.lua:49: in function `LibStub'
Omen\Modules\Overview\Overview.lua:6: in main chunk
Omen\Frame.lua:226: attempt to call method 'UpdateBarLayouts' (a nil value)
Omen\Frame.lua:130: in function `CreateFrame'
Omen\Omen.lua:33: in function <Interface\AddOns\Omen\Omen.lua:19>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0\AceAddon-3.0.lua:316: in function `InitializeAddon'
AceAddon-3.0\AceAddon-3.0.lua:404: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:397>
and many more like them...
in fact, 'cause there are soooo many, I attached the error log from !BugSack in .txt form.
can i petition time to be spent on fixing pet threat? i know for one that my voidwalker has far more threat than it shows, with me sometimes getting up to 200%+ of its threat before gaining aggro. my hunter friend said he experiences the same thing with his pet. because of this omen is basically useless to me, even though its quite useful with a pet.
I am unable to access my Omen configuration menu. I have tried updating it, deleting it and the variables, deleteing my interface folder, my WTF folder Cache folder, resinalling WoW and i cannot access the configuration menu at all, i have tried /omen config i have tried the minimpa button and the wrench looking icon.
I have the same problem as Nyke above me and it's not generating an error in bugsack so i really have nothing to go on. r68250 by the way and I've deleted all saved variables for Omen, completely uninstalled it and sworn at my screen quite a lot and nothing makes my config menu appear :(
Every time I start up wow within moments of entering combat for the first time I get this bug. This has only started since 2.4 and i've hoped with every update it would be fixed but it has not yet.
We had a big bug yesterday, but I'm not sure I can provide any useful information.
We were all using recent builds (ie, from this week end. 2 things were wrong
1- on my personnal machine, no menu.
2- worse, the reported treat was very wrong: on akil'zon , the protec-specced warrior that was DPSing showed as high as my protec-specced pally. Pally was doing its utmost to generate threat, warrior was only doing white damage. Checking recount after the fact, the pally did more than 2.5x the damage of the warrior, which, with righteous fury, should have given him almost 5x the treat, not about as much.
Thanks a lot for your hard work... 2.4 really doesn't seem a piece of cak e ^^
Go to the profiles section and select the Default profile. Change any settings that need to be changed.
Log on your other toons and then load the Default profile.
Thanks, actually this seems to have been fixed in one of the weekend updates, so I can now load my profiles. I should really just have them set as default though...
2- worse, the reported treat was very wrong: on akil'zon , the protec-specced warrior that was DPSing showed as high as my protec-specced pally. Pally was doing its utmost to generate threat, warrior was only doing white damage. Checking recount after the fact, the pally did more than 2.5x the damage of the warrior, which, with righteous fury, should have given him almost 5x the treat, not about as much.
I would like to report that I experienced this as well in my ZA group. Pally was tanking, and his reported threat is about 1/2 or 1/3 that of what it actually is on Akil'zon (eagle boss). The remainder of ZA was fine though.
On the topic of incorrect threat reports in Omen, I had a problem in the Prince fight in Kara this weekend, so a simple single target threat fight. I apologize, I don't have the version I was running, but it was the most recent version as of Saturday 7:00 AM pacific time - I updated right before the run that morning.
I was dpsing (feral cat form if that helps) and Omen was reporting me at around 90% of the tank's threat, when Prince aggroed on me. This was still in phase 1, so no axes or anything like that - just straight melee aggro. He stuck to me until I was dead, then went back to the tank for aggro.
Is this a problem caused by people in the raid using different versions, and those versions aren't communicating correctly with each other? or is this a bug intrinsic to Omen/Threat-2.0?
Also, if it happens again, is there any info I can provide to help diagnose (other than remembering the version next time?)
I paged through +/- a half dozen pages on the front/back and didn't see it, so forgive me if it's been asked & answered already - any ETA (or NO!) on the restoration of the customization options? My UI is a scosh busy, so I always had my bar and the aggro-gain bars set at double-size and +50% respectively, using different textures to clearly distinguish them from everything else at a fast glance/periphery.
Hope this hasn't been asked yet, and that it should be in the Omen part of the forum:
Currently if a player dies with insignificance (in the Bloodboil encounter in BT) their Omen will not show threat generation from them until the next Fel Rage phase has finished, and they have survived and the Insignificance debuff has faded.
a player death doesnt fire an event in the combatlog at the moment, blizzard said theyll fix it with the next patch,so do much about it except wait. Correct me if im wrong here anti ;)
Go to the profiles section and select the Default profile. Change any settings that need to be changed.
Log on your other toons and then load the Default profile.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWhat Gil said. (Holy crap, it's Gil!)
Loading other char's profiles does nothing at the moment.
EDIT: What I found out is that on a version check, my version showes up as Unknown to any other and any other people in my raid show up as Unknown Version when I do a version check.
EDIT2: I checked my Addons folder and found 2 other Addons using Threat 2.0 or they have a threath.lua: DaHud with DaPortrait and Aloft and a third one: CowTip. Maybe any interference by them?
EDIT3: Found errors for Omen2/Threat2, that was in raid yesterday in Mount Hyjal:
Here are some errors:
and many more like them...
in fact, 'cause there are soooo many, I attached the error log from !BugSack in .txt form.
Thanks!
uncheck box next to Enable Sound. :)
Date: 2008-04-06 18:59:59
ID: 43
Error occured in: Global
Count: 6
Message: ...terface\AddOns\Omen\Libs\LibSink-2.0\LibSink-2.0.lua line 276:
attempt to call method 'IsEnabled' (a nil value)
Debug:
(tail call): ?
...terface\AddOns\Omen\Libs\LibSink-2.0\LibSink-2.0.lua:276: check()
...terface\AddOns\Omen\Libs\LibSink-2.0\LibSink-2.0.lua:305:
...terface\AddOns\Omen\Libs\LibSink-2.0\LibSink-2.0.lua:296
...terface\AddOns\Omen\Libs\LibSink-2.0\LibSink-2.0.lua:327:
...terface\AddOns\Omen\Libs\LibSink-2.0\LibSink-2.0.lua:316
...terface\AddOns\Omen\Libs\LibSink-2.0\LibSink-2.0.lua:336: Pour()
Omen\Omen.lua:235: Warn()
...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:787: CheckWarn()
...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:656: ?()
...men\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146:
...men\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
[string "safecall Dispatcher[4]"]:4:
[string "safecall Dispatcher[4]"]:4
[C]: ?
[string "safecall Dispatcher[4]"]:13: ?()
...men\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire()
Omen\Libs\Threat-2.0\Threat-2.0.lua:321: ThreatUpdatedForUnit()
Omen\Libs\Threat-2.0\Threat-2.0.lua:301: ThreatUpdated()
...ddOns\Omen\Libs\Threat-2.0\ThreatClassModuleCore.lua:1086: AddTargetThreat()
...ddOns\Omen\Libs\Threat-2.0\ThreatClassModuleCore.lua:877: parseDamage()
...ddOns\Omen\Libs\Threat-2.0\ThreatClassModuleCore.lua:548: ?()
...men\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146:
...men\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
[string "safecall Dispatcher[20]"]:4:
[string "safecall Dispatcher[20]"]:4
[C]: ?
[string "safecall Dispatcher[20]"]:13: ?()
...men\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire()
...rface\AddOns\Omen\Libs\AceEvent-3.0\AceEvent-3.0.lua:70:
...rface\AddOns\Omen\Libs\AceEvent-3.0\AceEvent-3.0.lua:69
AddOns:
AdvancedTradeSkillWindow
AspectsBar, v0.61
Atlas, v1.11.0
AtlasBattlegrounds, v1.11.0
AtlasBattlegrounds, v1.10.3
AtlasDungeonLocs, v1.11.0
AtlasDungeonLocs, v1.10.3
AtlasEntrances, v1.10.3
AtlasEntrances, v1.11.0
AtlasFlightPaths, v1.10.3
AtlasFlightPaths, v1.11.0
AtlasOutdoorRaids, v1.11.0
AtlasOutdoorRaids, v1.10.3
AtlasLoot, vAtlasLoot Enhanced v4.04.00
AtlasLootBCInstances, v4.04.00
AtlasLootCrafting, v4.04.00
AtlasLootOldInstances, v4.04.00
AtlasLootRepFactions, v4.04.00
AtlasLootSetsandPvP, v4.04.00
AtlasLootWorldLoot, v4.04.00
AucAdvanced, v5.0.PRE.2963
AucFilterBasic, v5.0.PRE.2963 (BillyGoat)
AucStatClassic, v5.0.PRE.2963 (BillyGoat)
AucStatPurchased, v5.0.PRE.2963 (BillyGoat)
AucStatSimple, v5.0.PRE.2963 (BillyGoat)
AucStatStdDev, v5.0.PRE.2963 (BillyGoat)
Auctioneer, v5.0.PRE.2963
AutoProfitX, v2.03
BeanCounter, v5.0.PRE.2963 (BillyGoat)
BigWigs, v2.0 r66723
BonusScanner, v3.4
BulkMail2Inbox, v2.3
BulkMail2, v2.3.1
CensusPlus, v4.1.3
Chronometer, v0.10
CooldownTimers2, v2.5
CooldownCount, v2.1
CritRecord, v2.0.10.beta1
DamageMeters, v5.8.1
diMapCoords, v1.09
diMapCoordsOption, v1.09
Earth
EarthFeatureFrame
Enchantrix, v5.0.PRE.2963
EnchantrixBarker, v5.0.PRE.2963 (BillyGoat)
EnhTooltip, v5.0.PRE.2963
epgp, v3.3.2
FluffyQuestLevels, v0.91
Gatherer, v3.1.1
Informant, v5.0.PRE.2963
Ace2
LittleWigs
MobInfo2, v3.48
MrPlow, va/R.6.2.56614
myAddOns, v2.7
Omen, vOmen r68250 / Threat-2.0 r68324
Outfitter, v4.0.1
PreformAVEnabler
Proximo, v1.3
QuestHelper, v0.39
RatingBuster, v1.3.7 (r66013)
Recount, v68331
sct, v5.7
Sea, v1.32
Stubby, v52
SunwellEventProgress, v0.3
Swatter, v5.0.PRE.2963
TitanAmmo, v3.2.2.20400
TitanBag, v3.2.2.20400
TitanClock, v3.2.2.20400
TitanCoords, v3.2.2.20400
TitanGoldTracker, v3.2.2.20400 (2.3.2)
TitanHonor, v3.2.2.20400 (1.13)
TitanItemBonuses, v3.2.2.20400
TitanLootType, v3.2.2.20400
TitanPerformance, v3.2.2.20400
TitanRegen, v3.2.2.20400
TitanRepair, v3.2.2.20400
TitanRider, v3.2.2.20400
TitanStanceSets, v3.2.2.20400
TitanXP, v3.2.2.20400
Titan, v3.2.2.20400
WeaponQuickSwap
WIM, v2.3.65
RelicSays
AllInOneInventory
We were all using recent builds (ie, from this week end. 2 things were wrong
1- on my personnal machine, no menu.
2- worse, the reported treat was very wrong: on akil'zon , the protec-specced warrior that was DPSing showed as high as my protec-specced pally. Pally was doing its utmost to generate threat, warrior was only doing white damage. Checking recount after the fact, the pally did more than 2.5x the damage of the warrior, which, with righteous fury, should have given him almost 5x the treat, not about as much.
Thanks a lot for your hard work... 2.4 really doesn't seem a piece of cak e ^^
Thanks, actually this seems to have been fixed in one of the weekend updates, so I can now load my profiles. I should really just have them set as default though...
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI would like to report that I experienced this as well in my ZA group. Pally was tanking, and his reported threat is about 1/2 or 1/3 that of what it actually is on Akil'zon (eagle boss). The remainder of ZA was fine though.
I was dpsing (feral cat form if that helps) and Omen was reporting me at around 90% of the tank's threat, when Prince aggroed on me. This was still in phase 1, so no axes or anything like that - just straight melee aggro. He stuck to me until I was dead, then went back to the tank for aggro.
Is this a problem caused by people in the raid using different versions, and those versions aren't communicating correctly with each other? or is this a bug intrinsic to Omen/Threat-2.0?
Also, if it happens again, is there any info I can provide to help diagnose (other than remembering the version next time?)
Thanks!
Currently if a player dies with insignificance (in the Bloodboil encounter in BT) their Omen will not show threat generation from them until the next Fel Rage phase has finished, and they have survived and the Insignificance debuff has faded.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium