Please correct me if I'm wrong, but old Omen automatically defaulted to global threat if you had nothing targetted while new Omen requires you to click on the AoE mode or single target mode. Seems like a giant step backwards in functionality.
There isn't any concept of global threat in ThreatLib anymore; since we have true per-target tracking, global (healing) threat is aggregated per target.
You shouldn't have to select a target in AOE mode (but that's having issues right now). If you want and old-style global threat display, so you can gauge your healing threat, AOE mode is the way to go. The nice thing is, it'll show your relative threat per GUID, rather than only showing who has how much cumulative healing threat, which is infinitely more valuable.
The new omen looks very cool.
A few polish remarks however, which probably have been mentioned already.
1: i can't hide the icon. It's either in fubar, or on the minimap. but i can't hide it completely.
2: Scaling issue, when i logged in my alts, i found that the omen window was screwed up. After some experimenting i found that when i clicked the resize tag it snapped back to normal size.
3: No way to save profiles. As with version 1, you still have to do all settings for each character individually it seems.
4: Class colors? Can't seem to customize these on a per-player basis anymore.
5: Bar color styles seem nice, but making these selectable will be a cool feature.
6: You still get warnings, even if you disable warnings. Only when you actually disable the individual warnings do the warnings stop.
2 question's, and sorry if there is an obvious answer to them
1' in older version i could get the agro bar from omen, wich represent my agro vs tank, and put somewhere in the screen, and close omen, cause i dint care to much about the others.
i canot seems to do it now.
2' i miss the ... "ching" or "ding" sound. a melodious beep, canot really tell you how it sounds.
i dint find any sound in the curent list good for my ears :(
Gonna bea greeing with most of the posters here - the new Omen2 is bulky, less customizeable, and gives far more "numerical information" than *I* at least care to know about..
I shall look again to turn off the warnings (the red screen was driving me nuts, and actually started blinking whenever I was OUT of combat - lol) - I couldn't find the option last night.
Also I miss where we USE to be able to set at what percentage we wanted our threat notification to pop (I just used a text message, no shaking or red blinky). Can we get that back??
I'd also like to just be able to display threat percentage - I don't need four colums of informational numbers (that I have no FRICK CLUE what the heck they are telling me anyway). Other than my rank "near the top" with the graphs, I had no idea what to look at and what numbers were telling me how far my threat was from the tanks vs. all the other numbers.
I agree to have the option where myself is labeled in RED to make ME easier to find (I'm not a raid leader, I only care about ME! :)).
Sounds like from your post above, what I'm looking for is the AOE option (sees my threat on all mobs wether they are targeted or not?) - which didn't work at all for me last night. So eagerly awaiting to try that option out.
It worked fine though on single target (other than our tank not having any aggro meter last night lol) mode - just the complication of all the numbers and being harder to read and tell what I'm looking at makes me miss the simple version.
I really hope you put in these tweaks that the original Omen had - and then it will be great!!
[2008/03/27 01:48:03-1665-x1]: 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 <...mer\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>
---
either it does no longer exist - or I can't find it.
In GOOD OLD OMEN (compact and great) I made a rightclick to choose thing like "Send Data to KTM / Display KTM Data".
Nothing happens with right click - and in the config I can't find such options.
Assumeing the Healer / AOE and so on mode will work - I have to bring up that nasty big button bar to switch mode or go through Fu-Bar / Config and then bring up the bar - choose mode / remove the bar.....
Rightclick - select mode - done - would be great.
I find no longer options to pull out bars also.
Looks like a total new thing - and the old was good - but this?
Yeah for some "style need guys" maybe - I need a fast functional and not to much space consuming thing.
Thats what i am missing the most, over the recent months i really became accustomed to my threat-bar in the middle of my screen.
Any chance that this feature will come back?
After reading the above poster, or in some cases trying to decipher what some people belive is english, and after my guilds own disasterous experience with Omen2 in Hyjal last night I feel these are the top problems.
1: AOE mode and Healer mode are crashing and/or lagging people significantly. I myself had my computer come to a near halt when I went to AOE mode (I play a mage and as such was looking foward to that feature.)
2: Even in single target mode people were still crashing. We wiped once on Anetheron when Omen2 kicked 70% of our ranged DPS offline middle of DPSing an infernal. At that point the raid leader ordered everyone to log out and disable Omen2. Rest of the night went fine with no more crashes or people lagging up beyond the norm.
3: Not so much of a glitch, the lack of your own agro being singled out as a red bar did make tracking ones own threat more difficult.
4: When I enabled the auto collapse so it would shrink to occupy less space between fights and/or targets, it very often would go back to its default size and "hang up" until a new target was selected for it to track.
5: Lack of a FuBar hook or a minimap icon for convient access to both the addon and its config menus. At this time I keep having to use slash commands to access Omen. Edit: After updating to Fubar 3.0 and associated updates, the hook is working again. Fubar just wasn't updated at the time I got the new Omen.
6: Not so much an issue at the moment in my opinion, but has seen concern expressed by the above posters, the cosmetic appearence of the new Omen and the options to adjust and change it leave something to be desired.
Don't know if this helps put a priority on issues with Omen at the moment or not. Patch day is always hell day on addons and their programmers. I did my best to try and list the issues affecting the new Omen starting with top priority and working my way down. :P
I think when people complain about lag or crash because of Omen2. They should first list which mod they are running while use Omen2. Since 2.4 totally changed how combat log works. Most UI that use combat log would need upgrade. IMO wipe all addon do a clean install will be good at this stage. I doubt 90% of user will do that. Since most people been lazy and not really know how UI works. They just do what people told them to do. That's most of problem come from.
If people suffer lag and other issue should first disable all addon but Omen2. If problem still there then report to here. That will be much clear for what's going on.
Also it really doesn't make sense, when people saying only lag and crash in AOE mode. Omen should be only a front application which display threat from threat2.0 library. It doesn't do anything but display info. Those mode just some different way to display threat. Unless there are something else cause problem. Fix me if I'm wrong.
Really hoping we will get a way to actually save a profile and select it in game though. Without that it's impossible to upload a UI that is all layed out including Omen. Before I would just have instructions in my readme file to tell people right click omen on fubar and choose profile X or profile Y depending on if they were melee or ranged. I really don't want to have to explain to them how to edit a .lua file.
I will ship you three thousand pounds of caffeine, Antiarc. The new UI for Omen...oy.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThere isn't any concept of global threat in ThreatLib anymore; since we have true per-target tracking, global (healing) threat is aggregated per target.
You shouldn't have to select a target in AOE mode (but that's having issues right now). If you want and old-style global threat display, so you can gauge your healing threat, AOE mode is the way to go. The nice thing is, it'll show your relative threat per GUID, rather than only showing who has how much cumulative healing threat, which is infinitely more valuable.
A few polish remarks however, which probably have been mentioned already.
1: i can't hide the icon. It's either in fubar, or on the minimap. but i can't hide it completely.
2: Scaling issue, when i logged in my alts, i found that the omen window was screwed up. After some experimenting i found that when i clicked the resize tag it snapped back to normal size.
3: No way to save profiles. As with version 1, you still have to do all settings for each character individually it seems.
4: Class colors? Can't seem to customize these on a per-player basis anymore.
5: Bar color styles seem nice, but making these selectable will be a cool feature.
6: You still get warnings, even if you disable warnings. Only when you actually disable the individual warnings do the warnings stop.
Other than that, seems fine so far.
1 of 2:
Interface/Addons/Omen/Libs/Threat-2.0/ThreatUtils.lua:212 attempt to index local 'guid' (a number value)
2 of 2:
Interface/Addons/Omen/Libs/Threat-2.0/ThreatNPCModuleCore.lua:372 attempt to index field 'attacks' (a nil value)
And by the way it was a lot easier when i could change my Omen Color to Red. Now it seems there's no way to seperate me from others ^^
1' in older version i could get the agro bar from omen, wich represent my agro vs tank, and put somewhere in the screen, and close omen, cause i dint care to much about the others.
i canot seems to do it now.
2' i miss the ... "ching" or "ding" sound. a melodious beep, canot really tell you how it sounds.
i dint find any sound in the curent list good for my ears :(
I shall look again to turn off the warnings (the red screen was driving me nuts, and actually started blinking whenever I was OUT of combat - lol) - I couldn't find the option last night.
Also I miss where we USE to be able to set at what percentage we wanted our threat notification to pop (I just used a text message, no shaking or red blinky). Can we get that back??
I'd also like to just be able to display threat percentage - I don't need four colums of informational numbers (that I have no FRICK CLUE what the heck they are telling me anyway). Other than my rank "near the top" with the graphs, I had no idea what to look at and what numbers were telling me how far my threat was from the tanks vs. all the other numbers.
I agree to have the option where myself is labeled in RED to make ME easier to find (I'm not a raid leader, I only care about ME! :)).
Sounds like from your post above, what I'm looking for is the AOE option (sees my threat on all mobs wether they are targeted or not?) - which didn't work at all for me last night. So eagerly awaiting to try that option out.
It worked fine though on single target (other than our tank not having any aggro meter last night lol) mode - just the complication of all the numbers and being harder to read and tell what I'm looking at makes me miss the simple version.
I really hope you put in these tweaks that the original Omen had - and then it will be great!!
If you go into skins in the new omen config, you can choose the classic skin.
There is a work-around. Looks like this and works fine. You'll change the character-specific profiles to 'global'.
Omen2DB = { ["profileKeys"] = { ["your_character_name_1 - your_realm_name"] = "global", ["your_character_name_2 - your_realm_name"] = "global", }, ["profiles"] = { ["global"] = {-
View User Profile
-
View Posts
-
Send Message
Forum Moderatorbtw for profiles you can use AceDBOptions-3.0
either it does no longer exist - or I can't find it.
In GOOD OLD OMEN (compact and great) I made a rightclick to choose thing like "Send Data to KTM / Display KTM Data".
Nothing happens with right click - and in the config I can't find such options.
Assumeing the Healer / AOE and so on mode will work - I have to bring up that nasty big button bar to switch mode or go through Fu-Bar / Config and then bring up the bar - choose mode / remove the bar.....
Rightclick - select mode - done - would be great.
I find no longer options to pull out bars also.
Looks like a total new thing - and the old was good - but this?
Yeah for some "style need guys" maybe - I need a fast functional and not to much space consuming thing.
Also - pls. special color for own character.
Regards
Manfred
Thats what i am missing the most, over the recent months i really became accustomed to my threat-bar in the middle of my screen.
Any chance that this feature will come back?
1: AOE mode and Healer mode are crashing and/or lagging people significantly. I myself had my computer come to a near halt when I went to AOE mode (I play a mage and as such was looking foward to that feature.)
2: Even in single target mode people were still crashing. We wiped once on Anetheron when Omen2 kicked 70% of our ranged DPS offline middle of DPSing an infernal. At that point the raid leader ordered everyone to log out and disable Omen2. Rest of the night went fine with no more crashes or people lagging up beyond the norm.
3: Not so much of a glitch, the lack of your own agro being singled out as a red bar did make tracking ones own threat more difficult.
4: When I enabled the auto collapse so it would shrink to occupy less space between fights and/or targets, it very often would go back to its default size and "hang up" until a new target was selected for it to track.
5: Lack of a FuBar hook or a minimap icon for convient access to both the addon and its config menus. At this time I keep having to use slash commands to access Omen. Edit: After updating to Fubar 3.0 and associated updates, the hook is working again. Fubar just wasn't updated at the time I got the new Omen.
6: Not so much an issue at the moment in my opinion, but has seen concern expressed by the above posters, the cosmetic appearence of the new Omen and the options to adjust and change it leave something to be desired.
Don't know if this helps put a priority on issues with Omen at the moment or not. Patch day is always hell day on addons and their programmers. I did my best to try and list the issues affecting the new Omen starting with top priority and working my way down. :P
If people suffer lag and other issue should first disable all addon but Omen2. If problem still there then report to here. That will be much clear for what's going on.
Also it really doesn't make sense, when people saying only lag and crash in AOE mode. Omen should be only a front application which display threat from threat2.0 library. It doesn't do anything but display info. Those mode just some different way to display threat. Unless there are something else cause problem. Fix me if I'm wrong.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumReally hoping we will get a way to actually save a profile and select it in game though. Without that it's impossible to upload a UI that is all layed out including Omen. Before I would just have instructions in my readme file to tell people right click omen on fubar and choose profile X or profile Y depending on if they were melee or ranged. I really don't want to have to explain to them how to edit a .lua file.
Would be nice to be able to put the modules bar at the top too.