Here are a couple of sceenshots illustrating the issue - basically the pet start at an enormous TPS and just build from there.
#1: Morogrim last night - somewhat into the encounter. Fandango is a cat, has no dash and growl is off. Main tank is Psuedo:
#2: Soloing. Panzerpork is a boar - with charge and growl. I have shot about 3-4 times immediately after letting the pet charge:
Dr. Frederick Frankenstein: Igor, help me with the bags.
Igor: Soitenly. You take the blonde, I'll take the one in the turban.
Dr. Frederick Frankenstein: I was talking about the luggage.
I've had similar problems in the past where my pets aggro would never 'clear' on a particular mob name, so if was farming the same mob type (same name) my pets aggro would approach ludicrous speed. I haven't had the problem in several weeks, but this sounds similar. Sorry I can't be more helpful.
I've had similar problems in the past where my pets aggro would never 'clear' on a particular mob name, so if was farming the same mob type (same name) my pets aggro would approach ludicrous speed. I haven't had the problem in several weeks, but this sounds similar. Sorry I can't be more helpful.
This isn't quite the same issue as the pets aggro generally clears well enough inbetween mobs - and there's only one Morogrim mob anyway.
Dr. Frederick Frankenstein: Igor, help me with the bags.
Igor: Soitenly. You take the blonde, I'll take the one in the turban.
Dr. Frederick Frankenstein: I was talking about the luggage.
This isn't quite the same issue as the pets aggro generally clears well enough inbetween mobs - and there's only one Morogrim mob anyway.
Good point, the error seemed similar enough to me upon initial read, though as you point out it's actually different enough to make my 'helpful comment' seem silly :P
The problem we were having with the tank falling off the list appears to have been linked to him running some old version of DoTimer that we didn't realize he was running. Problem solved, it appears.
Hm, it might be related to the pet TPS issue. 2 raids ago I had serious issues with my (older) Recount where others were using newer version, which totally fucked up my memory usage and FPS until I deactivated Recount / edited the lua files to disable synching.
Before that happened (did receive a ton of errors before, but the perfomance issue started later right during Al'ar phase 2), another Recount user with a newer version (and therefore also newer version of libraries) reported a hunter with >1500 DPS on his list, whereas on my list he just had about 700.
Might be that some lib is/was reporting wrong combat information for the pet which is causing higher DPS and correspondingly higher TPS?
Possibly - but in raid my pet is where he should be on Recount - somewhere above the MT but below the player DPS (except for the odd slacker ^^).
And when I solo it should only be my threat lib/Omen who gather information - and I used the latest version available.
I noted last night in raid that the pet TPS was rollercoasting wildly - from +5000 or more to minus several thousands and then back up again in literally seconds. But as I haven't had any complaints from other raid members the possibly corrupt data aren't transmitted to the rest of the raid.
Last edited by Qrt : 09/21/07 at 10:04 AM.
Reason: spelling - and an afterthought.
Dr. Frederick Frankenstein: Igor, help me with the bags.
Igor: Soitenly. You take the blonde, I'll take the one in the turban.
Dr. Frederick Frankenstein: I was talking about the luggage.
I haven't seen this pop up in our raids yet, but I'm still watching out for it. I'm hoping it was just an old library problem, but I won't know for sure without more info.
Have the people with addons tried using the "Reinstall all addons" feature in WAU? It seems to me like it has cleared up some library weirdness before. I may have just gotten lucky. As usual, backup first.
I haven't actually been to Nightbane for a while but I certainly remember Vanish not working there. A few times I remember rogues would be close to pulling aggro, they would vanish and then a few seconds later succeed in pulling that aggro, even if we were halfway through a 'landed' phase (so it wasn't a timing issue with the aggro reset).
This was before our tanks improved their threat generation techniques and we made more widespread use of Blessing of Salvation for the dps (that alone made a lot of difference) so it hasn't been an issue for us for a long time.
My guess is that certain bosses are either bugged, have an unforseen consequence of coding (rather than broken code) or have been designed to prevent such abilities working, rather than Vanish itself being bugged (well, not bugged more that is...)
I got called in to help out with an Alts run in Karazhan on Saturday at Nightbane.
I had to Vanish in the last landed phase and got killed a few seconds later, he didn't move from the tank, the tank did not move Nightbane about at all and my position was the same it had been for that phase (we had Nightbane on ~10% when I died).
I checked what it was that killed me, a Cleave. No way this should have happened.
that is much more likely to be an issue with cleave than vanish. i have gotten cleaved while in normal, hind quarter position before. it's either buggy or finicky.
Apologies if this was answered, I did my best to skim and wasn't sure what to search on.
I have updated Omen and Standalone libs multiple times, am not using updated versions of cartographer/pitbull that are using Rock libs (and was having this problem before Rock was even around I think).
On my elemental shaman I am constantly seeing myself around 60% threat (after building up) or so on the main Omen table, but getting 90% warnings and eventually pulling agro. This happened in a Kara raid on prince (didn't pull but had to rely on other people's tables/vent to not get over the tank), in 5 mans, etc.
I think the threat warnings are working just fine since I get the 90% multiple times before pulling agro, but I never see myself that high on the table. If I pull out the tank bar, that doesn't show me as being anywhere near above him either.
I have a screenshot at home but not here at work at the moment.
I've tried to keep omen and libs updated and this has been pretty persistent.
Has anyone else had or reported similar problems? Is there something I can do to try to fix? Again this has persisted through a number of updates. I suppose I could try using a non-externals version of Omen, is there anything special I need to do since I still have the standalone libs, or will it sort itself out?
Apologies if this was answered, I did my best to skim and wasn't sure what to search on.
I have updated Omen and Standalone libs multiple times, am not using updated versions of cartographer/pitbull that are using Rock libs (and was having this problem before Rock was even around I think).
On my elemental shaman I am constantly seeing myself around 60% threat (after building up) or so on the main Omen table, but getting 90% warnings and eventually pulling agro. This happened in a Kara raid on prince (didn't pull but had to rely on other people's tables/vent to not get over the tank), in 5 mans, etc.
I think the threat warnings are working just fine since I get the 90% multiple times before pulling agro, but I never see myself that high on the table. If I pull out the tank bar, that doesn't show me as being anywhere near above him either.
I have a screenshot at home but not here at work at the moment.
I've tried to keep omen and libs updated and this has been pretty persistent.
Has anyone else had or reported similar problems? Is there something I can do to try to fix? Again this has persisted through a number of updates. I suppose I could try using a non-externals version of Omen, is there anything special I need to do since I still have the standalone libs, or will it sort itself out?
Thanks
The warnings might come because the other people are using ktm with multi targets, i get that alot in raids since i'm the only one using it and i always get 90% warnings on other targets
That may be a possibility; I'm pretty sure it has happened in groups where nobody had KTM though (I can try to verify next time I see it). It also happens on single targets (5 man bosses as a good example).
However, I know I have pulled agro (beyond just getting warnings) on mobs when Omen has shown me significantly under the tank (~60% or so). Other people in the group saw me at the top on their meters.
Weird, i did have some weird problems back when i used recount, it used up so much of my bandwith my whole threat resetted to 0 while i was 105% at other people. Did you try to play abit with the settings? Like making the percentage it warns you a bit higher
Here are a couple of sceenshots illustrating the issue - basically the pet start at an enormous TPS and just build from there.
I've been having this same problem for the last few weeks and it is very annoying to myself and the raid. I finally decided to play around with my addons and I found that By switching over from Pitbull to Ag_Unit frames I no longer have this problem anymore. Probably not the same for everyone, but if you are using Pitbull and encountering this problem I would suggest disabling it and checking your results.
I've been having this same problem for the last few weeks and it is very annoying to myself and the raid. I finally decided to play around with my addons and I found that By switching over from Pitbull to Ag_Unit frames I no longer have this problem anymore. Probably not the same for everyone, but if you are using Pitbull and encountering this problem I would suggest disabling it and checking your results.
Yes I do use PitBull so perhaps Antiarc and CkKnight ought to get their heads together over this... The problem does persist after deleting all saved variables for Omen and reinstalling, but I guess it's just a display bug as Omen show the proper MT as having aggro even if the pet is incredibly high over the aggro gain bar - and the erroneous data doesn't seem to be transmitted to the rest of the raid.
Edit: my erroneous pet data did get transmitted to the rest of the raid; it wasn't a raid-wiping issue so they didn't tell me...
Last edited by Qrt : 09/26/07 at 2:25 PM.
Dr. Frederick Frankenstein: Igor, help me with the bags.
Igor: Soitenly. You take the blonde, I'll take the one in the turban.
Dr. Frederick Frankenstein: I was talking about the luggage.
I use X-perl for unit frames, I'm not a pet class, and I still saw the hunter's pet with thousands of TPS with the version as of last night at ~7PM Eastern US time. Others on TS saw the same thing.
I use other addons which I believe have moved to the Rock framework.
I use pitbull and i have the problem aswell, went on a random mob in terrokar and it had the problem, turned of pitbull and the problem dissapeared. turned back on pitbull again and it came back in 2-3 mobs.
This makes me believe the problem is related to the player who owns the pet having pitbull and thus sending alot more aggro generation then really takes place.
I two have seen the sky high pet threat, was running some coilfang heroics with our mt's hunter alt the other day in crappy blues cause he just hit 70 and his pet was at like 9k+ tps the whole time.
I've also been getting aggro warnings (set at 100% of a tanks threat) a lot lately while showing me way down at the bottom of my 10 or so visible on the threat list by a huge margin, with my tps at rougly 650-700 on my lock in raids, previously I'd be a lot closer to 800-900 tps (Still doing same kind of dps) and my aggro would be way closer to where the MT was, I got yelled at cause I was close to pulling a couple times without even realizing it =/ I also just switched to pitbull recently from xperl. This had happened to one of our warlock officers a little while ago too.
In all three situations the person who's omen was fucked uninstalled, deleted the omen info in wtf folder and reinstalled and they seem to be working properly
09/20/07, 1:26 PM
Similar Threads
