I'm as lost on this as teedog... my guild has been using Omen successfully for about 3 weeks. Only times I notice weird threat numbers is when people that make a great deal of global threat do not have Omen installed. An example: today on Void Reaver trash a few of our healers showed massive threat, they were only using KTM... at a break I made them get Omen and the numbers dropped back to normal values. Not sure if it is something with the inter-comm between Threat-1.0 and KTM or what....
But, yeah.. I notice weird things when people are using KTM, which is why I usually ignore KTM data. :P
Personaly untill both Kenco and Antiarc can get over their CRI, he should remove any cross compatibility with KTM, as more and more of these anomolies that Starinnia has pointed out.
Please excuse if this is a repeat issue, didn't see it in about 10 pages scanned.
Yesterday, we had our first run in The Eye, and it was also the first time we'd actually asked people to download a threat meter (mostly KTM). We've had some running them before, and never had a problem with cross-addon data in smaller 5-mans and raids.
However, this time, from the beginning of the raid, the four people using Omen could only see the data from other Omen users. Then, on perhaps our second wipe (learning trash) when everyone zoned in, we could all see data from all the KTM users. Later in the raid (don't know when the change happened, sorry) it was back to only data from the four Omen users.
This was with some various versions of Omen, from updated yesterday at about 7 PM EST to one maybe 3 days old. Any ideas what caused it?
Our guild is an all-Omen guild currently. Usually it works great but last night we were having several quirks in Karazhan. First off, some of us were getting nasty lua-errors from Threat 1.0. Switching to an older version of Omen fixed it for now. I was having an issue where, if I pulled a bar out, it would stick to my cursor no matter where it went. I would actually have to type /logout to logout because I couldn't press any buttons. Once I re-logged back-in it was fine, though. And on Nightbane, our druid pulled aggro off of the tank and he was well below our MT in threat (This was before he Nightbane took-off, too. It was in the early stages). Everyone was very confused because we had not seen this happen before. It could've been a game glitch, though.
Is it possible to show more than the top 10 threat bars in omen? As raid leader I have no way of checking if people have a threatmeter installed unless I see a bar for them. I know omen has a version checker, but some people are still using KTM and I am not going to force people to switch over until Omen 1.0 is released.
In a recent version of Omen (at least I think Antiarc did this), it checks to see if the raid members are using any meter that works with the Omen/Threat combo. Older versions just spit out the Threat-1.0 revision number, now they give a client and a version number... so maybe it will display KTM xx.xx
And a direct answer, in Display there should be an option for number of bars. 10 is default, not sure what the max is.
Our guild is an all-Omen guild currently. Usually it works great but last night we were having several quirks in Karazhan. First off, some of us were getting nasty lua-errors from Threat 1.0. Switching to an older version of Omen fixed it for now. I was having an issue where, if I pulled a bar out, it would stick to my cursor no matter where it went. I would actually have to type /logout to logout because I couldn't press any buttons. Once I re-logged back-in it was fine, though. And on Nightbane, our druid pulled aggro off of the tank and he was well below our MT in threat (This was before he Nightbane took-off, too. It was in the early stages). Everyone was very confused because we had not seen this happen before. It could've been a game glitch, though.
Thanks!
My guild was likewise seeing some weirdness with Threat-1.0 and Omen last night in Karazhan. While on Prince the main tank would occasionally stop transmitting data to the Threat-1.0 users in the raid(he was running threat-1.0/omen only at that point), the KTM users could still see him. We had him update his install of threat-1.0/omen to the most recent version. He exited out of wow and logged back in, only to be presented with the LUA errors and another round of threat data ceasing to be transmitted mid-fight, with it resuming transmission upon the tanks death(!).
Ultimately we had him log out, disable Threat-1.0/Omen, and had him turn on KTM and ran through the encounter that way without incident(except some Threat-1.0 users had to reload their own UI to get Threat-1.0 to realize he was no longer running a Threat-1.0 client so it could pull his KTM data instead).
I've also seen occasions where Omen/Threat isn't registering the mob making a target change. It's happened on my hunter a few times, here I'd pull aggro from my pet, then the pet would grab aggro back from me, but Omen would continue generating an aggro gain bar for me rather than the pet(which actually had aggro).
Related minor annoyance thing too: On bosses with the RSTG thing going on, it isn't uncommon for Omen to pick up on those target changes, assume it was a change in who had aggro, and immediately begin warning me that I was about to pull aggro from the person getting the TLC of the Random Secondary Target Generator. Not exactly sure how you'd go about telling the difference between an actual aggro-pull versus a momentary retargeting via the RSTG but thought I'd put that one out there as well.
The Omen window appears in the middle of my screen each time I load the game. I move it to my desired location, lock it. Next time I login, the Omen window is back in the center again.
r43550
I'm not sure if this has been requested, or is even possible.
I believe KTM did not reset 'who was tanking' on the meter when a boss uses a RSTS ability, like arcane orb on VR.
With omen, my pullout bar set to 'aggro gain' blinks back and forth because omen shows someone else as having threat. Is there some way to make an educated assumption in the mod that would prevent that from happening? Or maybe not make that information switch unless 2 seconds have passed, givng him time to target the ranged person, and then refocus on the tank?
Also, on Hydross, after each transition, although it reset properly, it takes maybe 5 - 10 seconds for the TPS information to 'settle' down. The MT will show as a 'negative' number, and there will be no'aggro gain' bar. Is it taking the mod this long to figure out who is tanking? I'm not sure what is happening.
Side note, my guild downed Hydross for the first time last night, using essentially an all omen raid. Grats to you guys on making an outstanding mod with a very useful feature set. I love the on screen notification and pullout aggrobar as a shadow priest, and so far the threat information appears to be exteremly accurate.
Will Void Reaver be correct for us? Has his knockback aggro reducing effect been figured out?
Found a bug with priests on the Illidan fight. When they cast Shadow Ward Pain or Vampiric Touch on Illidan himself they will jump to around 25k threat. Omen: 43550 Threat: 43693.
Also I don't think the reset function is working totally correctly, sometimes I need to issue 2 resets for it to really clear.
My guild has killed VR twice now using Omen/Threat-1.0 and we were using older version on our last kill. The reduction from r43327 of Threat seemed accurate. I think it the reduction was .75
Sunday raid we got threat meteres really messed up to the top.
Out of our 25 people, maybe 5 were using Omen, rest KTM.
MainTarget was asked to be set by a promoted KTM user and I was tanking Morogrim, though only been somwhere at 5th position on threat (even before any murlocks).
We will try some more testing during a Karaz raid or so I guess, but as we will have our 2nd evening on Vashj tomorrow, I'll skip it for now. The confusion it causes makes it worse than it would help at all.^^
Boomkin Druid is owning Nr.1 position in threat-list most of the times btw (KTM user)
Cheers
Chew
P.S.: I got a Hunter alt .... and using "Viper Sting" doesnt generate agro at all according to Omen - is that ture ?
It's probably my misunderstanding of how threat generation or how threat is reported, but can someone please advise this crusty old BM Hunter ...
I've noticed that the correlation between the threat displayed on my pet and myself seems to "disagree" with a mobs actions. Sometimes I'll be on 70% threat to my pet and the mob will peel off to attack me (especially early in a battle). Other times (especially late in a battle) the mob will be firmly glued to me while I'm firing away at 140% threat.
My understanding is that Omen is supposed to be more accurately than KLH, but it doesn't seem the case sometimes ... especially when soloing. Admittedly I'm not paying THAT much attention to the meters in instances as I'm more tuned into hitting the feign button when I hear the warning bell telling me I'm getting close to stealing aggro from the tank.
Can someone please explain how threat is reported.
accuracy is part of age.. KLHTM has age.. and plenty of accuracy
best thing to do is turn on the reporting / recording part of threat and post here so we can hash out the details,, well post in the Threat-1.0 thread in teh libs/mixin fourm that is.
I'm as lost on this as teedog... my guild has been using Omen successfully for about 3 weeks. Only times I notice weird threat numbers is when people that make a great deal of global threat do not have Omen installed. An example: today on Void Reaver trash a few of our healers showed massive threat, they were only using KTM... at a break I made them get Omen and the numbers dropped back to normal values. Not sure if it is something with the inter-comm between Threat-1.0 and KTM or what....
I suspect this is correct, actually. Omen threat will nearly always register lower than KTM's, because KTM's threat is basically (sum of threat on all targets + global threat), whereas Omen will show you (single target's threat + global threat).
This is, in the end, why KTM data is specifically noted as such.
Quote from wallix »
Our guild is an all-Omen guild currently. Usually it works great but last night we were having several quirks in Karazhan. First off, some of us were getting nasty lua-errors from Threat 1.0.
Do you have those errors handy?
I was having an issue where, if I pulled a bar out, it would stick to my cursor no matter where it went. I would actually have to type /logout to logout because I couldn't press any buttons. Once I re-logged back-in it was fine, though.
I'm looking at this now, actually.
And on Nightbane, our druid pulled aggro off of the tank and he was well below our MT in threat (This was before he Nightbane took-off, too. It was in the early stages). Everyone was very confused because we had not seen this happen before. It could've been a game glitch, though.
I've had a -lot- of reports of anomalous behavior on Nightbane in the first preflight phase. I'm wondering if he has some kind of deaggro or something that is affecting the charts, because it is consistently only him, and only in the first preflight phase.
Also, on Hydross, after each transition, although it reset properly, it takes maybe 5 - 10 seconds for the TPS information to 'settle' down. The MT will show as a 'negative' number, and there will be no'aggro gain' bar. Is it taking the mod this long to figure out who is tanking? I'm not sure what is happening.
This is a bug that I need to deal with.
Will Void Reaver be correct for us? Has his knockback aggro reducing effect been figured out?
Yup!
Quote from Jam »
Found a bug with priests on the Illidan fight. When they cast Shadow Ward Pain or Vampiric Touch on Illidan himself they will jump to around 25k threat. Omen: 43550 Threat: 43693.
Also I don't think the reset function is working totally correctly, sometimes I need to issue 2 resets for it to really clear.
Is it only the Illidan fight? is it reproducable anywhere else?
P.S.: I got a Hunter alt .... and using "Viper Sting" doesnt generate agro at all according to Omen - is that ture ?
It very likely causes threat, but I haven't measured it yet, and as it doesn't cause damage, you can't really pick it up implicitly.
Quote from Lichbane »
*pet stuff*
I may yet have some inconsistencies in the pet module; pet threat is somewhat tricky to figure out. What spec are you, and what pet are you using?
I think Omen can tell which mobs resist soulshatter, which would mean that if there are multiple mobs but your target does not resist, your threat will be reduced, but Blizzard will still throw up the resist message for the other mobs that did resist soulshatter.
About soulshatter the other night I clearly saw in void reaver's fight (so no add) that if SS is resisted then Omen still takes 50% off. So make pretty hard to know if u'r overaggroing
Can i tbe fixed?
Rot
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBut, yeah.. I notice weird things when people are using KTM, which is why I usually ignore KTM data. :P
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYesterday, we had our first run in The Eye, and it was also the first time we'd actually asked people to download a threat meter (mostly KTM). We've had some running them before, and never had a problem with cross-addon data in smaller 5-mans and raids.
However, this time, from the beginning of the raid, the four people using Omen could only see the data from other Omen users. Then, on perhaps our second wipe (learning trash) when everyone zoned in, we could all see data from all the KTM users. Later in the raid (don't know when the change happened, sorry) it was back to only data from the four Omen users.
This was with some various versions of Omen, from updated yesterday at about 7 PM EST to one maybe 3 days old. Any ideas what caused it?
Thanks!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAnd a direct answer, in Display there should be an option for number of bars. 10 is default, not sure what the max is.
My guild was likewise seeing some weirdness with Threat-1.0 and Omen last night in Karazhan. While on Prince the main tank would occasionally stop transmitting data to the Threat-1.0 users in the raid(he was running threat-1.0/omen only at that point), the KTM users could still see him. We had him update his install of threat-1.0/omen to the most recent version. He exited out of wow and logged back in, only to be presented with the LUA errors and another round of threat data ceasing to be transmitted mid-fight, with it resuming transmission upon the tanks death(!).
Ultimately we had him log out, disable Threat-1.0/Omen, and had him turn on KTM and ran through the encounter that way without incident(except some Threat-1.0 users had to reload their own UI to get Threat-1.0 to realize he was no longer running a Threat-1.0 client so it could pull his KTM data instead).
I've also seen occasions where Omen/Threat isn't registering the mob making a target change. It's happened on my hunter a few times, here I'd pull aggro from my pet, then the pet would grab aggro back from me, but Omen would continue generating an aggro gain bar for me rather than the pet(which actually had aggro).
Related minor annoyance thing too: On bosses with the RSTG thing going on, it isn't uncommon for Omen to pick up on those target changes, assume it was a change in who had aggro, and immediately begin warning me that I was about to pull aggro from the person getting the TLC of the Random Secondary Target Generator. Not exactly sure how you'd go about telling the difference between an actual aggro-pull versus a momentary retargeting via the RSTG but thought I'd put that one out there as well.
r43550
We've now got *everyone* to uninstall KTM and we've turned off all KTM compatability options - seems to have cured the problem.
8-)
I believe KTM did not reset 'who was tanking' on the meter when a boss uses a RSTS ability, like arcane orb on VR.
With omen, my pullout bar set to 'aggro gain' blinks back and forth because omen shows someone else as having threat. Is there some way to make an educated assumption in the mod that would prevent that from happening? Or maybe not make that information switch unless 2 seconds have passed, givng him time to target the ranged person, and then refocus on the tank?
Also, on Hydross, after each transition, although it reset properly, it takes maybe 5 - 10 seconds for the TPS information to 'settle' down. The MT will show as a 'negative' number, and there will be no'aggro gain' bar. Is it taking the mod this long to figure out who is tanking? I'm not sure what is happening.
Side note, my guild downed Hydross for the first time last night, using essentially an all omen raid. Grats to you guys on making an outstanding mod with a very useful feature set. I love the on screen notification and pullout aggrobar as a shadow priest, and so far the threat information appears to be exteremly accurate.
Will Void Reaver be correct for us? Has his knockback aggro reducing effect been figured out?
Also I don't think the reset function is working totally correctly, sometimes I need to issue 2 resets for it to really clear.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOut of our 25 people, maybe 5 were using Omen, rest KTM.
MainTarget was asked to be set by a promoted KTM user and I was tanking Morogrim, though only been somwhere at 5th position on threat (even before any murlocks).
We will try some more testing during a Karaz raid or so I guess, but as we will have our 2nd evening on Vashj tomorrow, I'll skip it for now. The confusion it causes makes it worse than it would help at all.^^
Boomkin Druid is owning Nr.1 position in threat-list most of the times btw (KTM user)
Cheers
Chew
P.S.: I got a Hunter alt .... and using "Viper Sting" doesnt generate agro at all according to Omen - is that ture ?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI've noticed that the correlation between the threat displayed on my pet and myself seems to "disagree" with a mobs actions. Sometimes I'll be on 70% threat to my pet and the mob will peel off to attack me (especially early in a battle). Other times (especially late in a battle) the mob will be firmly glued to me while I'm firing away at 140% threat.
My understanding is that Omen is supposed to be more accurately than KLH, but it doesn't seem the case sometimes ... especially when soloing. Admittedly I'm not paying THAT much attention to the meters in instances as I'm more tuned into hitting the feign button when I hear the warning bell telling me I'm getting close to stealing aggro from the tank.
Can someone please explain how threat is reported.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumbest thing to do is turn on the reporting / recording part of threat and post here so we can hash out the details,, well post in the Threat-1.0 thread in teh libs/mixin fourm that is.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI suspect this is correct, actually. Omen threat will nearly always register lower than KTM's, because KTM's threat is basically (sum of threat on all targets + global threat), whereas Omen will show you (single target's threat + global threat).
This is, in the end, why KTM data is specifically noted as such.
Do you have those errors handy?
I'm looking at this now, actually.
I've had a -lot- of reports of anomalous behavior on Nightbane in the first preflight phase. I'm wondering if he has some kind of deaggro or something that is affecting the charts, because it is consistently only him, and only in the first preflight phase.
This is a bug that I need to deal with.
Yup!
Is it only the Illidan fight? is it reproducable anywhere else?
It very likely causes threat, but I haven't measured it yet, and as it doesn't cause damage, you can't really pick it up implicitly.
I may yet have some inconsistencies in the pet module; pet threat is somewhat tricky to figure out. What spec are you, and what pet are you using?
i mean, if u resist soulshatter, u get still the aggro reduction in omen
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumCan i tbe fixed?
Rot