Starting about 2 weeks ago (and continuing to today) i can't see the tanks threat, although i can see everyone else's just fine.
Both times the tank was a warrior, the first time during a kharazan run and the tank was using KTM.
The second run the tank was using Omen.
Both were using the latest versions of their respective mods.
When i disabled Omen and turned on KTM i could see the tanks threat just fine, but never when using Omen.
An odd thing i noticed, if i didn't have anything targeted i could sometimes see the tanks threat, but never when i had something targeted. This only happened to the tank using Omen.
[2007/07/21 11:25:26-490-x1]: Omen\Omen.lua:11: AceAddon: AceOO-2.0: Library "Soar-1.0" does not exist.
AceLibrary\AceLibrary.lua:100: in function <Interface\AddOns\AceLibrary\AceLibrary.lua:53>
(tail call): ?:
(tail call): ?:
AceAddon-2.0-44196 (Ace2):974: in function `new'
Omen\Omen.lua:11: in main chunk
[2007/07/21 11:25:26-490-x1]: Omen\OmenDisplay.lua:31: attempt to index global 'Omen' (a nil value)
[2007/07/21 11:25:26-490-x1]: Omen\OmenMenu.lua:195: attempt to index global 'Omen' (a nil value)
Starting about 2 weeks ago (and continuing to today) i can't see the tanks threat, although i can see everyone else's just fine.
Both times the tank was a warrior, the first time during a kharazan run and the tank was using KTM.
The second run the tank was using Omen.
Both were using the latest versions of their respective mods.
At first guess I'd say you have warriors turned off in the display options.
[2007/07/21 11:25:26-490-x1]: Omen\Omen.lua:11: AceAddon: AceOO-2.0: Library "Soar-1.0" does not exist.
AceLibrary\AceLibrary.lua:100: in function <Interface\AddOns\AceLibrary\AceLibrary.lua:53>
(tail call): ?:
(tail call): ?:
AceAddon-2.0-44196 (Ace2):974: in function `new'
Omen\Omen.lua:11: in main chunk
[2007/07/21 11:25:26-490-x1]: Omen\OmenDisplay.lua:31: attempt to index global 'Omen' (a nil value)
[2007/07/21 11:25:26-490-x1]: Omen\OmenMenu.lua:195: attempt to index global 'Omen' (a nil value)
Starting about 2 weeks ago (and continuing to today) i can't see the tanks threat, although i can see everyone else's just fine.
Both times the tank was a warrior, the first time during a kharazan run and the tank was using KTM.
The second run the tank was using Omen.
Both were using the latest versions of their respective mods.
At first guess I'd say you have warriors turned off in the display options.
Omen-2.1r44409\Omen.lua:599: invalid option in `format'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:97: in function `func'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:65: in function <...\AddOns\Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:62>
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:82: in function <...\AddOns\Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:69>
<in C code>: ?
AceEvent-2.0-40601 (AceEvent-2.0):269: in function `TriggerEvent'
AceEvent-2.0-40601 (AceEvent-2.0):910: in function <Interface\AddOns\AceEvent-2.0\AceEvent-2.0.lua:903>
I have a continuing problem with Omen's display of threat - It seems Omen stops reporting our tank's threat after a certain point. He'll get to around 2.6K threat or so and then stay there for the rest of the fight, even though we (obviously) don't pull aggro.
Is this a combat bug having to do with Furor? Like, combat is initiated but because the boss has not been engaged it doesn't register threat correctly? I can't think of any other reason it would happen.
Any idea why Omen keeps appearing in the middle of my screen instead of where I left it? I tend to log off or switch toons in rested areas if that has any bearing on it.
Anyone have any ideas on this? It happened again last night.
Any idea why Omen keeps appearing in the middle of my screen instead of where I left it? I tend to log off or switch toons in rested areas if that has any bearing on it.
Anyone have any ideas on this? It happened again last night.
When i get problems like this I tend to try and 'uninstall' the addon before updating.
I think I had that problem a few weeks ago, and yeah, uninstalling the mod, deleting the saved vars, logging in without Omen, then exiting and reinstalling fixed it for me.
Any idea why Omen keeps appearing in the middle of my screen instead of where I left it? I tend to log off or switch toons in rested areas if that has any bearing on it.
Anyone have any ideas on this? It happened again last night.
I think I tracked it down to Omen loading on demand via AddonLoader. When I removed AddonLoader, the issue went away and Omen remembered it's settings. Also, changing it's LoD settings via: "/addonloader overrides omen always" to always load Omen seemed to clear it up as well. Perhaps a dev could see why Omen is appearing to not load all of it's settings when it is invoked from AddonLoader?
Any idea why Omen keeps appearing in the middle of my screen instead of where I left it? I tend to log off or switch toons in rested areas if that has any bearing on it.
Anyone have any ideas on this? It happened again last night.
I think I tracked it down to Omen loading on demand via AddonLoader. When I removed AddonLoader, the issue went away and Omen remembered it's settings. Also, changing it's LoD settings via: "/addonloader overrides omen always" to always load Omen seemed to clear it up as well. Perhaps a dev could see why Omen is appearing to not load all of it's settings when it is invoked from AddonLoader?
Good catch. I'm sure you're right since I too use AddonLoader and am having the same problem with Omen's window always appearing in the center.
Date: 2007-07-22 00:25:58
ID: 52
Error occured in: Global
Count: 1
Message: ..\AddOns\Omen\OmenDisplay.lua line 31:
attempt to index global 'Omen' (a nil value)
Debug:
[C]: ?
Omen\OmenDisplay.lua:31: in main chunk
and
Date: 2007-07-22 00:25:58
ID: 53
Error occured in: Global
Count: 1
Message: ..\AddOns\Omen\OmenMenu.lua line 195:
attempt to index global 'Omen' (a nil value)
Debug:
[C]: ?
Omen\OmenMenu.lua:195: in main chunk
Omen-2.1r44409\Omen.lua:599: invalid option in `format'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:97: in function `func'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:65: in function <...\AddOns\Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:62>
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:82: in function <...\AddOns\Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:69>
<in C code>: ?
AceEvent-2.0-40601 (AceEvent-2.0):269: in function `TriggerEvent'
AceEvent-2.0-40601 (AceEvent-2.0):910: in function <Interface\AddOns\AceEvent-2.0\AceEvent-2.0.lua:903>
I think I tracked it down to Omen loading on demand via AddonLoader. When I removed AddonLoader, the issue went away and Omen remembered it's settings. Also, changing it's LoD settings via: "/addonloader overrides omen always" to always load Omen seemed to clear it up as well. Perhaps a dev could see why Omen is appearing to not load all of it's settings when it is invoked from AddonLoader?
Good catch. I'm sure you're right since I too use AddonLoader and am having the same problem with Omen's window always appearing in the center.
Am I missing something here... Why is AddonLoader even needed for Omen? I've been removing the code from the ToC file for a while now, never really connected it to the positioning stuff. Just never seemed to do anything for Omen. Is there any benefit?
Just tried Omen after a guildie recommended it but I'm having a problem with it. I cant see my own or my pets (hunter) threat on the list. Works fine with everyone elses threat but doen not show mine. Tried solo aswell with just the pet out and nothing shows - I see the test bars just fine and both myself and my pet is shown there, have the allways show self option clicked.
Any ideas/suggestions, I'd really like to switch from KTM to this addon.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Both times the tank was a warrior, the first time during a kharazan run and the tank was using KTM.
The second run the tank was using Omen.
Both were using the latest versions of their respective mods.
When i disabled Omen and turned on KTM i could see the tanks threat just fine, but never when using Omen.
An odd thing i noticed, if i didn't have anything targeted i could sometimes see the tanks threat, but never when i had something targeted. This only happened to the tank using Omen.
WoWAceUpdater says: Omen: r44410/44413, Threat-1.0: r44369.
At first guess I'd say you have warriors turned off in the display options.
Install Soar-1.0, nothing more simple
No, i did check on that.
Elbereth.
Is this a combat bug having to do with Furor? Like, combat is initiated but because the boss has not been engaged it doesn't register threat correctly? I can't think of any other reason it would happen.
Anyone have any ideas on this? It happened again last night.
When i get problems like this I tend to try and 'uninstall' the addon before updating.
Have you tried that?
I think I tracked it down to Omen loading on demand via AddonLoader. When I removed AddonLoader, the issue went away and Omen remembered it's settings. Also, changing it's LoD settings via: "/addonloader overrides omen always" to always load Omen seemed to clear it up as well. Perhaps a dev could see why Omen is appearing to not load all of it's settings when it is invoked from AddonLoader?
Good catch. I'm sure you're right since I too use AddonLoader and am having the same problem with Omen's window always appearing in the center.
Date: 2007-07-22 00:25:58
ID: 52
Error occured in: Global
Count: 1
Message: ..\AddOns\Omen\OmenDisplay.lua line 31:
attempt to index global 'Omen' (a nil value)
Debug:
[C]: ?
Omen\OmenDisplay.lua:31: in main chunk
and
Date: 2007-07-22 00:25:58
ID: 53
Error occured in: Global
Count: 1
Message: ..\AddOns\Omen\OmenMenu.lua line 195:
attempt to index global 'Omen' (a nil value)
Debug:
[C]: ?
Omen\OmenMenu.lua:195: in main chunk
Me and others get the same error since 44409.
Am I missing something here... Why is AddonLoader even needed for Omen? I've been removing the code from the ToC file for a while now, never really connected it to the positioning stuff. Just never seemed to do anything for Omen. Is there any benefit?
-> my whole raid had this error with the current version. Very annoying, it pops up from time to time, couldn?t recognize a pattern.
During Incite Chaos or just as it ended hard to say :/
(Shadow Labyrinth heroic)
got the same error with the current version
Any ideas/suggestions, I'd really like to switch from KTM to this addon.