Omen - Ace Threat Meter - Page 89

koaschten · 04/01/08, 4:26 PM

My general approach is, without externals and with automatic dependecies. This keeps you from having like 369 lib folders in your addons embedded that all use "LibHealComm" or one of the Babble ones. It clutters your interface a little more but saves you hdd space and the game doesn't have to iterate through redundant files on login.

Gearknight · 04/01/08, 5:06 PM

Without externals definately saves downloading and loading time if you have a lot of Ace addons. More importantly, I've had compatibility issues at times where addons have included outdated externals, causing other addons that depend on the same library to fail. Since going external-free, it has been smooth sailing, so I recommend it for everyone.

Mikari · 04/01/08, 6:08 PM

Not really sure if this is a bug or just an oversight, when I'm soloing with my pet, I'll send my pet in then start with an arcane or multi-shot, if either shot crit this will spike my tps up to between 20-40k, which brings my threat bar higher than the pull aggro bar momentarily, this quickly evens out and starts showing my real tps. Is it supposed to spike so high at the beginning?

Roberto · 04/01/08, 7:33 PM

Tongiht on Gurtogg we were told to use KTM (half of the guild wasnt happy, to say the least), after having issues with Omen2. After the raid we realized KTM wasnt working correct too, but some people insisted that we should stick to it, for a reason unknown to me.

So what I would like to know is (hasnt been mentioned yet I think, if it has though, sorry for asking), will there be an option in Omen2 to send threat information to KTM? Like it was in the first version of Omen? I mean I really dont wanna use KTM again, should the guild decide to use it...

Big thanks for this mod Antiarc, you're doing a great job...

nutteh · 04/02/08, 12:04 AM

Originally Posted by Antiarc

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

Seeing I was also having this problem, no class filters, not real setting changes other then having it showing the "classic" skin.

that being said, that was during sunwell on monday night, so 2 days ago

Dralmoo · 04/02/08, 3:49 AM

Same stuff on BB tonight. People dissapearing from threat, people not showing up, people zooming to the top of the meters arbitrarily. Had some problems on other bosses too - a mage pulled on Najentus without being anywhere near the top of the meter.

Everyone downloaded (and reported, via version check) 67499 before the raid.

Daboran · 04/02/08, 5:04 AM

Originally Posted by Dralmoo

Same stuff on BB tonight. People dissapearing from threat, people not showing up, people zooming to the top of the meters arbitrarily. Had some problems on other bosses too - a mage pulled on Najentus without being anywhere near the top of the meter.

Everyone downloaded (and reported, via version check) 67499 before the raid.

There was a big change to Threat 2.0 very recently and it's Threat 2.0 thats the important bit. You may find that everyone had the correct version of Omen installed, but those using wowaceupdater downloaded a newer version of Threat 2.0.

To fix this you also need to ask your raid to search \WoW\Addons\ and all subdirectories for "Threat*" and delete all old instances then download the latest version of Threat 2.0

This is one of the biggest things that messes up Omen imo - some people just don't configure properly (or even use) wowaceupdater and have multiple copies of the Threat 2.0 folder in the "Libs" subdirectory of every addon. Everyone else automatically updates to the latest version of Threat through wowaceupdater and it all ends up a mighty mess.

songster · 04/02/08, 9:20 AM

Yesterday we had a mass game crash - as in, everyone in the raid just froze, had to kill task via Task Manager just to exit. Someone claimed it was an infinite loop in Omen, but I don't know what evidence they had.

Is this a known issue? Bear in mind we're EU, so we were accidentally using the 2.4.1 Omen version on a 2.4 client/server.

Krag · 04/02/08, 9:35 AM

Originally Posted by songster

Yesterday we had a mass game crash - as in, everyone in the raid just froze, had to kill task via Task Manager just to exit. Someone claimed it was an infinite loop in Omen, but I don't know what evidence they had.

Is this a known issue? Bear in mind we're EU, so we were accidentally using the 2.4.1 Omen version on a 2.4 client/server.

We had this happen about 3 times yesterday too. Everyone totally froze. Looking at FuBar_AddonSpam it looked like we got a load of messages labeled CTRaidAssist right when we had lag spikes, but whether that was the true reason for the freezes wasn't verified either.

nutteh · 04/02/08, 9:43 AM

Must say we are using r67658 through blacktemple tonight, other then the fact half the time misdirects seem to go hunter not the tank, it seems to be right on.

I love it

Ulise · 04/02/08, 11:13 AM

Originally Posted by nutteh

Must say we are using r67658 through blacktemple tonight, other then the fact half the time misdirects seem to go hunter not the tank, it seems to be right on.

I love it

Lol but this is a major pain in the neck (like we've seen at Bloodboil last night; we still one shoted him though and two nights ago at our first Illidan kill).

So any thoughts on the misdirects not being reported?

Could it be, that some people had old Threat 2.0 libraries, or is it an Omen bug?

Or is actually a wow bug, since this what the wws logs seem to capture (I just checked and yeah at Bloodboil one MD went to the hunter)?

/cheers

Archonyx · 04/02/08, 12:29 PM

Originally Posted by songster

Yesterday we had a mass game crash - as in, everyone in the raid just froze, had to kill task via Task Manager just to exit. Someone claimed it was an infinite loop in Omen, but I don't know what evidence they had.

Is this a known issue? Bear in mind we're EU, so we were accidentally using the 2.4.1 Omen version on a 2.4 client/server.

We had the exact same crash last night - happened on Supremus at 1%. Massive raid-wide client crash. Not sure what other data we can provide that might help narrow down the issue, but let me know if we can provide logs/etc. to help.

♦ Bass · 04/02/08, 12:31 PM

Originally Posted by Archonyx

We had the exact same crash last night - happened on Supremus at 1%. Massive raid-wide client crash. Not sure what other data we can provide that might help narrow down the issue, but let me know if we can provide logs/etc. to help.

I believe this is a Blizzard issue, unrelated to Omen. There are reports of this happening from people without Omen, as well as people without any addons whatsoever.

Dralmoo · 04/02/08, 12:41 PM

Most people in my guild don't use WoWAceUpdater - I have them download the Omen zip with embedded Threat-2.0 from files.wowace.com. This SHOULD be fine, right?

When I do an Omen version check in game, does it check the version of Threat-2.0? If not can it be made to do so?

Fendryl · 04/02/08, 1:16 PM

I noticed last week that the MD on Gurtogg didn't take either. I haven't seen it on any other fights, since then though. This occured at the same time of some other Gurtogg fixes, and I had just attributed it to those other changes.

KraxisSingular · 04/02/08, 1:16 PM

Originally Posted by Daboran

There was a big change to Threat 2.0 very recently and it's Threat 2.0 thats the important bit. You may find that everyone had the correct version of Omen installed, but those using wowaceupdater downloaded a newer version of Threat 2.0.

To fix this you also need to ask your raid to search \WoW\Addons\ and all subdirectories for "Threat*" and delete all old instances then download the latest version of Threat 2.0

This is one of the biggest things that messes up Omen imo - some people just don't configure properly (or even use) wowaceupdater and have multiple copies of the Threat 2.0 folder in the "Libs" subdirectory of every addon. Everyone else automatically updates to the latest version of Threat through wowaceupdater and it all ends up a mighty mess.

Interesting... Being somewhat of an Omen noob (I have only used it and updated it), I noticed that my wowaceupdater didn't notice Threat 2.0 installed, so I installed it. Mind you I almost update every day (especially now) with externals. Was it redundant, or even counterproductive to install Threat 2.0 directly?

• Adoriele · 04/02/08, 1:32 PM

Originally Posted by KraxisSingular

Interesting... Being somewhat of an Omen noob (I have only used it and updated it), I noticed that my wowaceupdater didn't notice Threat 2.0 installed, so I installed it. Mind you I almost update every day (especially now) with externals. Was it redundant, or even counterproductive to install Threat 2.0 directly?

At worst it's redundant. Chances are if you only have Omen installed, and no other mod that would include Threat-2.0, you'll have the same exact code loaded twice. At best, (not incredibly sure how WoW loads redundant addon code) you'll load the right version of Threat-2.0 and override any others by including it as a standalone library. So it's not bad to cover your bases that way, unless you're really worried about the amount of memory your UI uses.

That said, the best way bar none to set up your UI, assuming you don't care how cluttered the folder/addons list are, is to update all your mods WITHOUT externals, and turn on automatic dependency downloading in WAU, then reinstall all of your addons. Gives you exactly the code you need, all libraries only show up once, and they're always the most up-to-date.

Marroc · 04/02/08, 2:11 PM

Originally Posted by Dralmoo

Most people in my guild don't use WoWAceUpdater - I have them download the Omen zip with embedded Threat-2.0 from files.wowace.com. This SHOULD be fine, right?

When I do an Omen version check in game, does it check the version of Threat-2.0? If not can it be made to do so?

The issue with downloading the embedded version is one of load times.

For example, say you have an addon named "Ahhh!" which loads Threat-2.0 as a dependency, and also run Omen. "Ahh!"'s copy of Threat-2.0 is the one that is used (as they're loaded alphabetically), and if the copy of Threat-2.0 in that addon is out of date, Omen will still use it because that's the one that's loaded.

Amosh · 04/02/08, 2:55 PM

Adding my voice to the chorus who crashed last night (04.01.08).

However I would like to add that we had probaly 9 out of 10 crash not everyone. I think it might be an issue of just the alot of mobs reporting at once. This happened on morogrim at the first earthquake (when the murlocs came out, not when the physical earthquake mechanic was used) and everyone just locked up. Now me and a few others who run the runits series of mods and have good to great computers, recovered after just a drop to single digit fps for 3-4 seconds. This was not the case with the people who aren't as good with addons (the type who run pitbull with all modules enabled and wonder why they use so much memory), most of them had to exit via a manual computer restart.

I believe this is a Blizzard issue, unrelated to Omen. There are reports of this happening from people without Omen, as well as people without any addons whatsoever.

I don't mean to sound insulting or demeaning by any stretch of the imagination, but, do you know of any of these people personally? I have only been able to find reports from people who were using that version (forget the number, it was the newest version at around 8:00 pm on 04.01.08) and were actively killing mobs/bosses in a raid when it spiked. If it is a blizz thing, then I am really interested in knowing what actually happened on their end.

By the way, everyone in our raid was running the latest version of omen and threat2.0 if that would help antiarc out.

Mikari · 04/02/08, 3:16 PM

Everyone using the latest version, one of our rogues always showed as highest threat, even if I changed target.

Another bug when I targeted a mob.

I also got a LibGUIDRegistry-0.1 error when I turned into a ghost on Teron but didn't manage to record it.

Also noticed there isn't a pull aggro bar anymore.

Supremus seems pretty buggy also, threat isn't being reset properly on a phase change I think, we have locks way above the tanks on threat but still not pulling aggro.

Could we have the title window act like Omen1? Only show text if a mob is marked, otherwise have it blank and not display Omen2?

♦ Bass · 04/02/08, 3:19 PM

Originally Posted by Amosh

I don't mean to sound insulting or demeaning by any stretch of the imagination, but, do you know of any of these people personally?

Certainly, a post in the BB from Anias:

Originally Posted by Anias

It's not omen, it's the client mishandling information provided by the server. Without access to blizzards code I can't track down what's being passed incorrectly, but I had a lock with no UI enabled at all beyond the blizzard core, and as my machine has all my normal bugcatching on it I can get tantalizing hints of unhandled exceptions floating around in memory after I kill the process and force a cleanup.

Blizzard is aware of the issue, hopefully it's something they can hotfix on their end. If you're thinking that the combat log was well tested on the ptr, you're horribly misinformed. Lots of client/server stuff this patch wasn't tested thoroughly due to player malaise, but content needed to go out to prevent death.

Pay your 12bux today! (Gogo free advertising.)

[e] Anias was not the only one supporting this belief, there are at least 2-3 other posters who can confirm it is, at least, not related specifically to Omen. Take from this what you will.

Amosh · 04/02/08, 3:29 PM

That makes me feel better about omen, but also alot worse thinking that a crash can happen at any time. PM me if you find out about any fixes to this and I'll do the same if I find anything.

Bunnyz · 04/02/08, 5:41 PM

Sorry if this is repost, but my Omen (was r67732 if I recall correctly) got a bug today (it actually happened to me back in last week at Bloodboil but after updated my Omen I thought it was fixed). It had worked well since the beginning of our run, but somewhere between Supremus fight I got d/c, then when I logged back it started bugging. Everyone's names (yes, everyone) except mine were "<Unknown>" althought their threat / class-color was correct, the warning about overagro still display their name well though. When I checked party Omen version all of them became Unknown/Unknown or incompatible to me (I had done another version check when we started, it was fine back then).

Daboran · 04/03/08, 6:31 AM

Originally Posted by Mikari

Everyone using the latest version, one of our rogues always showed as highest threat, even if I changed target.

Had a Warlock get this in our ZA run last night too, though I see there's a new version of both Threat and Omen out now.

KraxisSingular · 04/03/08, 9:23 AM

Originally Posted by Adoriele

At worst it's redundant. Chances are if you only have Omen installed, and no other mod that would include Threat-2.0, you'll have the same exact code loaded twice. At best, (not incredibly sure how WoW loads redundant addon code) you'll load the right version of Threat-2.0 and override any others by including it as a standalone library. So it's not bad to cover your bases that way, unless you're really worried about the amount of memory your UI uses.

That said, the best way bar none to set up your UI, assuming you don't care how cluttered the folder/addons list are, is to update all your mods WITHOUT externals, and turn on automatic dependency downloading in WAU, then reinstall all of your addons. Gives you exactly the code you need, all libraries only show up once, and they're always the most up-to-date.

Thanks a lot.
Did what you suggested, and what a truckload of libraries I got, a lot for addons I don't use. For instance I got both Ace2 and 3. I assume that they will not affect me negatively as long as I have lot of memory, which I do.