Omen - Ace Threat Meter - Page 88

Caven · 03/31/08, 9:01 AM

Looking forward to tonight then, thanks for the work your doing.

Ghiest · 03/31/08, 9:13 AM

Originally Posted by Malan

Threat 1.0 became non-backwards compliant about a day ago. If your raiders had not updated since Thursday none of them will show up on Omen. Force everyone to do a fresh install or update on WAU.

Yer we all update before our raid starts and were running both omen and threat max updates.

Antiarc · 03/31/08, 9:41 AM

As a heads-up, I'll be making another protocol change today late evening (at the end of the US raid week) to correct some issues in the existing protocol and to bring traffic down fairly severely. Be prepared to do raidwide updates. It's a pain in the ass, I know, but it's necessary.

Marroc · 03/31/08, 10:02 AM

Bug: Omen warnings play when omen is not set to show (ie. if I'm solo and have omen enabled, but not set to show while solo I'll still get warning messages/sounds/screenflashes). Perhaps an option to make warnings only play when omen is visible?

Fireye · 03/31/08, 10:06 AM

We forced everyone to update omen before our second night in BT (RoS --> Mother --> Council), we were running 67189, and encountered some oddities:
1) Omen2 still pops up an onscreen error when I soulshatter. I can't seem to replicate this behavior when solo.
2) Heading into phase3, we have our MT taunt the Essence of Anger, and then have a hunter misdirect onto him during the increased aggro period. Our hunter seemed to have the threat shown under his character, instead of the warriors.
3) Threat drops take a little bit to register, though it's quicker than in previous Omen2 builds.

As a feature request, is it possible for people to pull out threat bars anymore? We couldn't find a way.

Malan · 03/31/08, 10:24 AM

Antiarc, last night in BT using a version pulled at around 7pm EST the threat values on Bloodboil were way way off. It seemed ok on the first pull, then after some dumb shit we had to make a 2nd attempt and as soon as we started it showed healers with thousands of threat, never showed any of the tanks, and pets were doing 5 digit TPS.

Chir · 03/31/08, 10:51 AM

You're doing a great job

As a feature request, is it possible for people to pull out threat bars anymore? We couldn't find a way.

This is super useful on the Fames of Azzinoth for good tanking readings, any chance of getting it back?

dylan · 03/31/08, 11:18 AM

Originally Posted by Fireye

As a feature request, is it possible for people to pull out threat bars anymore?

It is not implemented, but Ant has said that it will return. It's probably best to fix the threat calculations first.

grizham1 · 03/31/08, 11:54 AM

I just wanted to thank you for your great work on the original omen antiarc. I'm hoping as time passes and everyone in my guild downloads the newer version of omen, you'll have worked out the kinks the newer version is currently experiencing. Our main tanks are continually not showing up on omen and I'm occasionally I am not showing up either. It's rather frustrating.

◊ Praetorian · 03/31/08, 12:03 PM

Originally Posted by grizham1

I just wanted to thank you for your great work on the original omen antiarc. I'm hoping as time passes and everyone in my guild downloads the newer version of omen, you'll have worked out the kinks the newer version is currently experiencing. Our main tanks are continually not showing up on omen and I'm occasionally I am not showing up either. It's rather frustrating.

Make sure everyone has the newest versions of Omen/Threat and no conflicting libs. If you use WAU, do the following:

1) Open WAU.
2) Go to Prefs. Make sure that "Download Dependencies" is checked. Make sure that "with Externals" is NOT checked.
3) Go to Files-->Reinstall All (near the bottom of the menu).

Have people do that, and update regularly. A couple of the Threat-2.0 updates have been backwards incompatible, and will make people not be able to see other people, which is bad.

chibiusa · 03/31/08, 12:59 PM

So i got omen2 about 2 days ago.
Is there another update of it?
Because it just isnt working for me.

koaschten · 03/31/08, 3:56 PM

Why don't you simply check over at World of Warcraft Addons - WowAce.com or use WowAceUpdater - WowAce Wiki ?

Mikari · 03/31/08, 5:40 PM

Just posting a few more bugs

Pet's are overlapping the other bars somehow

The Pull Aggro bar is acting odd.

Antiarc · 03/31/08, 5:48 PM

Originally Posted by Marroc

Bug: Omen warnings play when omen is not set to show (ie. if I'm solo and have omen enabled, but not set to show while solo I'll still get warning messages/sounds/screenflashes). Perhaps an option to make warnings only play when omen is visible?

Fixed this last night.

1) Omen2 still pops up an onscreen error when I soulshatter. I can't seem to replicate this behavior when solo.
2) Heading into phase3, we have our MT taunt the Essence of Anger, and then have a hunter misdirect onto him during the increased aggro period. Our hunter seemed to have the threat shown under his character, instead of the warriors.
3) Threat drops take a little bit to register, though it's quicker than in previous Omen2 builds.

As a feature request, is it possible for people to pull out threat bars anymore? We couldn't find a way.

1) Fixed this last night.
2) I'm checking into this.
3) Which threat drops in particular? Vanish should be instant; Soulshatter and FD take a bit to register out of necessity.
4) Pullout bars aren't in yet. I'm working on 'em

Originally Posted by Malan

Antiarc, last night in BT using a version pulled at around 7pm EST the threat values on Bloodboil were way way off. It seemed ok on the first pull, then after some dumb shit we had to make a 2nd attempt and as soon as we started it showed healers with thousands of threat, never showed any of the tanks, and pets were doing 5 digit TPS.

I should have fixed this last night.

Originally Posted by grizham1

I just wanted to thank you for your great work on the original omen antiarc. I'm hoping as time passes and everyone in my guild downloads the newer version of omen, you'll have worked out the kinks the newer version is currently experiencing. Our main tanks are continually not showing up on omen and I'm occasionally I am not showing up either. It's rather frustrating.

With any luck, I fixed the "people missing" problem last night (assuming both you and they are updated).

Originally Posted by Praetorian

A couple of the Threat-2.0 updates have been backwards incompatible, and will make people not be able to see other people, which is bad.

Correct. This is really unfortunate, but the alternative is spammy or incorrect traffic, which is worse, IMO.

Originally Posted by Mikari

Just posting a few more bugs

Pet's are overlapping the other bars somehow

The Pull Aggro bar is acting odd.

a) Do you use any class filtering (ie, any classes turned off?)
b) I'm tracking that one down.

Vanadi · 03/31/08, 6:03 PM

My guild has been using this add on for ages now but since the patch we have issues with Gurtogg. It would work fine till the first Fel Rage and then after that Omen wouldn't update threat anymore. I'm not entirely sure if this is a bug in the add on fault or just people being spastics with updating but I thought I'd let you know.

Marroc · 03/31/08, 6:08 PM

Originally Posted by Antiarc

Fixed this last night.

You sure? I just had it happen to me in revision 67322...

[e] Was on my lock. Had it only showing when in party/raid.
[e2] Just tested it again, and I can't get it to reproduce... Might have something to do with manually toggling omen on, and then off first.
[e3] Just went through everything I could think of, and couldn't get it to happen again... Might have just been a fluke, or I had some transitional revision when it happened, and now have a later revision and didn't notice >_< Sorry if you wasted time on it already.

Antiarc · 03/31/08, 6:21 PM

Originally Posted by Marroc

You sure? I just had it happen to me in revision 67322...

[e] Was on my lock. Had it only showing when in party/raid.
[e2] Just tested it again, and I can't get it to reproduce... Might have something to do with manually toggling omen on, and then off first.

This should have been fixed in r67276. If you get any errors, can you grab a stack trace (if you have a bug mod installed) or a screenshot of the error for me?

Mikari · 03/31/08, 6:31 PM

Originally Posted by Antiarc

a) Do you use any class filtering (ie, any classes turned off?)

There was no class filtering enabled, though I did notice in earlier builds that changing filters whilst in combat did mess up the bars.

Also whatever was done in 67322 of threatlib-2.0 makes almost everyone show up as unknown in the version check.

Moshne · 03/31/08, 9:42 PM

running 67378

error

[2008/03/31 18:36:58-934-x18]: Threat-2.0\Threat-2.0.lua:141: bad argument #4 to 'format' (number expected, got no value)
Threat-2.0\Threat-2.0.lua:141: in function <...nterface\AddOns\Threat-2.0\Threat-2.0\Threat-2.0.lua:140>
Threat-2.0\Threat-2.0.lua:367: in function `?'
Threat-2.0\Threat-2.0\ThreatUtils.lua:190: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...edia-3.0\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:246: in function <Interface\AddOns\Ace3\AceComm-3.0\AceComm-3.0.lua:235>

ShadowEric · 03/31/08, 9:53 PM

Antiarc, can you tell us what the minimum version number required for threat-lib compatibility is ? Just want to make sure the whole guild updates to at least that version.

And I know it's hard to foresee, but are you planning more drastic changes to the library which would cause further incompatibility between the various Omen2 versions ?

Thanks for your work.

• Intermission · 04/01/08, 12:45 AM

Originally Posted by Antiarc

As a heads-up, I'll be making another protocol change today late evening (at the end of the US raid week) to correct some issues in the existing protocol and to bring traffic down fairly severely. Be prepared to do raidwide updates. It's a pain in the ass, I know, but it's necessary.

Do what you gotta do mate! Cheers for the warning. We just get everyone to WAU before raid and versions arent a problem. (although there are still the clickers/rehabs that don't have WAU... luckily these same people wouldnt do enough dps to pull aggro!)

Another bug/issue/request report (Im not sure what the version was sorry. It was last nights raid - raid updated on WAU on 31 March ~7:00 Sydney time):
- FD wouldnt register. Successful or resisted, our threat would remain the same.
- Often when nobody was in combat, threat values would remain from the previous fights. Nothing meaningful, and a quick swap back and forth to different modes, then finally back to Single Target would 'clear' the bug, most values anyway. I assume it's just a display error and gets cleared when new combat starts anyway.
- The threat warning during random secondary target abilities is a little annoying. Any way of fixing that? I dont believe Omen1 had that issue.
- And finally another request: for multiple levels of warnings. EG I used to have a warning at 65% and at 90%. Multiple warning levels would also help when the bars have a display errors and you cant see your own bar. Ideally, maybe down the track, have options for different warning levels to have different display properties, eg I *hate* screen flashes normally, but I could have a 120% "wtf are you doing!!!" warning that could have a screen flash, and 60-80-95% warnings might simply be different sounds or Parrot/SCT colours.

Anyway, functionality before extra features I guess

Malan · 04/01/08, 1:12 AM

Second hand report, I didn't see what it was but when I logged in at 10pm with a fresh WAU pull of r67391, everyone in the raid that I hopped in started screaming that my copy of Omen was bugging the shit out of the entire raid, spamming error messages. Eventually the entire raid logged out to disable it. No problems on my end at all, but the rest of the raid said that the moment I joined it caused problems.

koaschten · 04/01/08, 3:41 AM

Originally Posted by Antiarc

As a heads-up, I'll be making another protocol change today late evening (at the end of the US raid week) to correct some issues in the existing protocol and to bring traffic down fairly severely. Be prepared to do raidwide updates. It's a pain in the ass, I know, but it's necessary.

I guess this should be a sufficient answer Malan.

Austin · 04/01/08, 2:14 PM

Originally Posted by Malan

Second hand report, I didn't see what it was but when I logged in at 10pm with a fresh WAU pull of r67391, everyone in the raid that I hopped in started screaming that my copy of Omen was bugging the shit out of the entire raid, spamming error messages. Eventually the entire raid logged out to disable it. No problems on my end at all, but the rest of the raid said that the moment I joined it caused problems.

Same exact problem that we had last night, I updated at ~6:30 pm PDT, and someone updated at ~8pm PDT in between a wipe, it caused everyone else to have a ton of errors pop up on their screen. Unfortunately, I'm at work and I can't tell you the revision numbers that were present.

Bikiniwax · 04/01/08, 2:55 PM

Originally Posted by Praetorian

Make sure everyone has the newest versions of Omen/Threat and no conflicting libs. If you use WAU, do the following:

1) Open WAU.
2) Go to Prefs. Make sure that "Download Dependencies" is checked. Make sure that "with Externals" is NOT checked.
3) Go to Files-->Reinstall All (near the bottom of the menu).

Have people do that, and update regularly. A couple of the Threat-2.0 updates have been backwards incompatible, and will make people not be able to see other people, which is bad.

What worked for us last night was to make sure that we didn't have the Threat 2.0 addon as a separate addon in the addons folder.

We then download the latest Omen WITH Externals. It seems this way Omen would use the Threat 2.0 library that is embedded in it's own subfolders and this stopped people from being "unknown" when doing a version check.

By the way, I always download all my Ace addons WITH Externals and seem to have little or no problems, although I'm still not sure which is better, WITH Externals or WITHOUT Externals.