Err... I *should* have the combat log to accompany my error report, but I don't. My apologies. We'll be heading back tomorrow evening and I'll be sure to get that information for you.
I know there is probably a lot of stuff being posted in here. I just wanted to make a little suggestion. If you find yourself with free time, could you possibly add a 'classic' version of omen. I dont really like the new look/ui and I find many options do not work correctly with the new version. Options not working correctly would be:
I noticed tonight when raiding MH that omen was taking up 10+MB of data!?!? the old omen was less than 1MB. Omen was lagging our raid group out so we forced everyone to turn it off after 5 people DC'd at the same time. After omen was turned off everything was fine. Is this going to be fixed?
I noticed tonight when raiding MH that omen was taking up 10+MB of data!?!? the old omen was less than 1MB. Omen was lagging our raid group out so we forced everyone to turn it off after 5 people DC'd at the same time. After omen was turned off everything was fine. Is this going to be fixed?
I'll definitely be looking at this - I didn't get a chance to do any raid testing on the PTR, so these are relatively new issues. However, I certainly don't want this thing eating up a ton of my frame time, so you can bet your britches I'll be figuring out what's going on. :)
Regarding the disconnects, that's a very high priority, and I'll have it fixed ASAP.
Warning have just been fixed - there was a bug. What's Auto-collapse doing (or not doing)?
Quote from: PAusten on Yesterday at 04:55:21 pm
After updating to 65853, omen just doesn't show up at all in my screen, same with it's fubar button and it's entry on the rock config window.
Bugsack does't show any errors.
Ace3, Threat-2.0 and libsink-2.0 are installed.
Having this exact same issue although i have tried /omen toggle and well as every other command i can think of. I even did a /ace2 list all option and it shows omen as active and using memory. Omen2 shows up in my addons list at login, yet i cannot access or control omen in any way. It doesnt pop up in combat or anything. No / commands are registering, i just get the Type"/help" for a listing of a few commands. It's like it exists and doesnt exist at the same time.
I remedied this issue on my own. I think it might be a buggered up No externals option in WAU. I went thru all my mods and manualy downloaded the individual mods with libs in each mod, cleaned up my Addons folder in the process and everythign is working fine. and with the exact same memory footprint as external libs. Im beginning to debate if the "without externals" option is really a memory saving thing, or is it just a hard drive space reduction.
Im beginning to debate if the "without externals" option is really a memory saving thing, or is it just a hard drive space reduction.
All duplicates of loaded libs gets thrown away so, no, "without externals" doesn't help at all for in-game memory used. But as I like to say: "Why load it at all if it's going to get thrown away?" ;)
It only affects load times, the ability to get more accurare performance monitoring (so that the first addon to load a lib don't get the blame for all that libs usage) and, as you said, a few megs or so of hard drive space :)
Omen\Modules\Healer\Healer.lua:163: attempt to perform arithmetic on global 'lastUpdateTime' (a nil value)
<in C code>: ?
AceEvent-2.0-63812 (Ace2):299: in function `TriggerEvent'
oRA2\Core.lua:206: in function <Interface\AddOns\oRA2\Core.lua:203>
oRA2\Core.lua:214: in function <Interface\AddOns\oRA2\Core.lua:211>
oRA2\Core.lua:221: in function <Interface\AddOns\oRA2\Core.lua:218>
<in C code>: ?
AceEvent-2.0-63812 (Ace2):299: in function `TriggerEvent'
AceEvent-2.0-63812 (Ace2):920: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:913>
Thanks Antiarc for all you hard work, don't let all the people that complain get you down. Omen is a great mod probably used by hundreds of thousands of people, they just gotta understand that it takes a while for someone to work out the bugs. Especially when that someone isn't getting paid for it.
Thanks Antiarc for all you hard work, don't let all the people that complain get you down. Omen is a great mod probably used by hundreds of thousands of people, they just gotta understand that it takes a while for someone to work out the bugs. Especially when that someone isn't getting paid for it.
Seconded. Thanks from all of us for helping to keep our repair bills down! :)
Hello!
Love the new Omen look and feel, just miss a few crucial features:
pull-out bars - usually you just need to compare your threat to the tank's, so I used to pull out the aggro-gain bar and look at it! Can you please put the pullout functionality there again?
custom bar colors - right now all the bars are colored after class which makes it quite hard to find yourself among them in a raid. I used to assign some bright color to MY bar so it was easy to see. No longer posible??
[2008/03/26 21:58:24-66-x3]: Omen\Libs\Threat-2.0\ThreatUtils.lua:212: attempt to index local 'guid' (a number value)
Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:214: in function <...\AddOns\Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:213>
Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:244: in function `ActivateModule'
Threat-2.0\Threat-2.0.lua:443: in function `?'
Omen\Libs\Threat-2.0\ThreatUtils.lua:184: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...tus\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[4]":4: in function <[string "safecall Dispatcher[4]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[4]":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
AceComm-3.0\AceComm-3.0.lua:244: in function <...terface\AddOns\Omen\Libs\AceComm-3.0\AceComm-3.0.lua:233>
---
[2008/03/26 22:21:51-66-x5]: Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:457: attempt to call method 'ScheduleTimer' (a nil value)
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...tus\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
AceEvent-3.0\AceEvent-3.0.lua:70: in function <...Ons\aX_RaidStatus\libs\AceEvent-3.0\AceEvent-3.0.lua:69>
---
EDIT: 2 more when starting/ending a Lurker fight.
[2008/03/26 22:36:18-66-x4]: Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:372: attempt to index field 'Attacks' (a nil value)
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...tus\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[20]":4: in function <[string "safecall Dispatcher[20]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[20]":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
AceEvent-3.0\AceEvent-3.0.lua:70: in function <...Ons\aX_RaidStatus\libs\AceEvent-3.0\AceEvent-3.0.lua:69>
---
[2008/03/26 22:45:23-66-x1]: Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:457: attempt to call method 'ScheduleTimer' (a nil value)
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...tus\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
AceEvent-3.0\AceEvent-3.0.lua:70: in function <...Ons\aX_RaidStatus\libs\AceEvent-3.0\AceEvent-3.0.lua:69>
Always show self
Auto collapse
Thanks.
I'll try that, thank you.
I did this, trying different combinations as well as unchecking every single box. Still the annoying flash.
Yep same.
Edit: removed the flash - 'glee'
I'll definitely be looking at this - I didn't get a chance to do any raid testing on the PTR, so these are relatively new issues. However, I certainly don't want this thing eating up a ton of my frame time, so you can bet your britches I'll be figuring out what's going on. :)
Regarding the disconnects, that's a very high priority, and I'll have it fixed ASAP.
Warning have just been fixed - there was a bug. What's Auto-collapse doing (or not doing)?
After updating to 65853, omen just doesn't show up at all in my screen, same with it's fubar button and it's entry on the rock config window.
Bugsack does't show any errors.
Ace3, Threat-2.0 and libsink-2.0 are installed.
Having this exact same issue although i have tried /omen toggle and well as every other command i can think of. I even did a /ace2 list all option and it shows omen as active and using memory. Omen2 shows up in my addons list at login, yet i cannot access or control omen in any way. It doesnt pop up in combat or anything. No / commands are registering, i just get the Type"/help" for a listing of a few commands. It's like it exists and doesnt exist at the same time.
I remedied this issue on my own. I think it might be a buggered up No externals option in WAU. I went thru all my mods and manualy downloaded the individual mods with libs in each mod, cleaned up my Addons folder in the process and everythign is working fine. and with the exact same memory footprint as external libs. Im beginning to debate if the "without externals" option is really a memory saving thing, or is it just a hard drive space reduction.
All duplicates of loaded libs gets thrown away so, no, "without externals" doesn't help at all for in-game memory used. But as I like to say: "Why load it at all if it's going to get thrown away?" ;)
It only affects load times, the ability to get more accurare performance monitoring (so that the first addon to load a lib don't get the blame for all that libs usage) and, as you said, a few megs or so of hard drive space :)
<in C code>: ?
AceEvent-2.0-63812 (Ace2):299: in function `TriggerEvent'
oRA2\Core.lua:206: in function <Interface\AddOns\oRA2\Core.lua:203>
oRA2\Core.lua:214: in function <Interface\AddOns\oRA2\Core.lua:211>
oRA2\Core.lua:221: in function <Interface\AddOns\oRA2\Core.lua:218>
<in C code>: ?
AceEvent-2.0-63812 (Ace2):299: in function `TriggerEvent'
AceEvent-2.0-63812 (Ace2):920: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:913>
when switching to heal mode
/omen skin load classic
to load it. Hope that's more comfortable for ya'll. :)
Seconded. Thanks from all of us for helping to keep our repair bills down! :)
I saved money by switching to Omen2. LOL!! Great mod, keep it up.
Omen won't show up on the bar, stays attached to minimap, and when I try to place it in center from Omen config I get-
Error: attempt to call methot 'SetPluginSide' (a nil value)
File: Interface\AddOns\Omen\Config.lua
Line: 203
Count: 1
Omen2 version 66077
Love the new Omen look and feel, just miss a few crucial features:
Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:214: in function <...\AddOns\Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:213>
Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:244: in function `ActivateModule'
Threat-2.0\Threat-2.0.lua:443: in function `?'
Omen\Libs\Threat-2.0\ThreatUtils.lua:184: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...tus\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[4]":4: in function <[string "safecall Dispatcher[4]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[4]":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
AceComm-3.0\AceComm-3.0.lua:244: in function <...terface\AddOns\Omen\Libs\AceComm-3.0\AceComm-3.0.lua:233>
---
[2008/03/26 22:21:51-66-x5]: Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:457: attempt to call method 'ScheduleTimer' (a nil value)
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...tus\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
AceEvent-3.0\AceEvent-3.0.lua:70: in function <...Ons\aX_RaidStatus\libs\AceEvent-3.0\AceEvent-3.0.lua:69>
---
EDIT: 2 more when starting/ending a Lurker fight.
[2008/03/26 22:36:18-66-x4]: Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:372: attempt to index field 'Attacks' (a nil value)
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...tus\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[20]":4: in function <[string "safecall Dispatcher[20]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[20]":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
AceEvent-3.0\AceEvent-3.0.lua:70: in function <...Ons\aX_RaidStatus\libs\AceEvent-3.0\AceEvent-3.0.lua:69>
---
[2008/03/26 22:45:23-66-x1]: Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:457: attempt to call method 'ScheduleTimer' (a nil value)
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...tus\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
AceEvent-3.0\AceEvent-3.0.lua:70: in function <...Ons\aX_RaidStatus\libs\AceEvent-3.0\AceEvent-3.0.lua:69>
---
If I switch to another stance, everything is peachy and works like a charm. Let me know if you need any other info.
Edit: Fixed! Thank you very much for your work.