- Registered User
Member for 12 years, 8 months, and 26 days
Last active Fri, Oct, 4 2013 14:29:58
- 0 Followers
- 26 Total Posts
- 0 Thanks
May 14, 2008This is still broken, a month later. Can't get libbabble-spell-3.0 even if it's the only addon loaded. The library is there in the folder (ie: was checked out) and looks correctly referenced in embeds.xml. I don't understand Ace library loading enough to debug the problem further.Posted in: AddOn HELP!
I believe the checkin that broke it is revision 70587. Anyone out there want to take a look and see if there's a simple fix?
Apr 30, 2008Posted in: Raid AddOnsQuote from HunterZ »
I can't believe people are still going on about this.
Me neither. I'm perfectly happy pulling the latest version from WAU (or SVN, for that matter). And I know that it's OK for people to be running slightly different versions of Threat and except for that one bug a few weeks ago, it will work alright. But I'm a software engineer who understands this stuff. All I'm saying is that there's a lot of superstition about software and a lot of people feel it's essential to have everyone on the same version. Which is causing a bit of grief.
I enjoyed Antiarc's interview and was all prepared to point to it for evidence that Omen was stable and we didn't have to stress about versions anymore. But unfortunately he said
The absolute best way to get things running smoothly is to make sure you have the whole raid group running the same revision, the more recent the better.
Which while true, will only encourage folks to drive themselves crazy with updates more often.
I think the best solution is to have occasional stable releases. But as folks point out above, we all love to use WAU to update. Another solution would be to have the Omen versioncheck not check the actual revision ID of Threat, but instead some "compatibility" version number that's only manually incremented on backward-incompatible changes. But that causes other trouble.
Apr 28, 2008Posted in: Raid AddOnsQuote from Zidomo »
That hasn't been a problem for several weeks (with SVN versions at least).
Yeah, but the word hasn't quite gotten out. My guild is currently requiring everyone to update to latest SVN build right before every night's raid, and folks are getting cranky. The big ugly incompatibility bug is gone, but Omen still seems incorrect often enough that people are skittish about it.
Apr 27, 2008Yup, I'm having this problem too. AutoProfitX also recently got a problem with libbabble, although the exact symptoms are different. Maybe someone made a change to some Ace libraries that breaks some of the addons using it?Posted in: AddOn HELP!
Apr 23, 2008Thanks, that's exactly the kind of thing I was looking for! Reading the code it seems a bit heavyweight; OnUpdate is probably not the best place to be retotalling all your threat. But I'll try it out.Posted in: AddOn HELP!
I'm getting tempted to try to add this data right into Recount. I like the way this mod totals threat across all targets. Not the right thing for a healer, but helpful for a tank.
Apr 21, 2008One thing that seemed lost in 2.4 and the shift to Omen2; Recount no longer has an option for displaying Threat. Is that a permanent change? I'm interested in getting better TPS measurements and Recount is currently the best way to do it.Posted in: General AddOns
Apr 18, 2008Posted in: Raid AddOnsQuote from deadmage »
We tried it on Nitebane last nite and it worked fine.
Hmm, Nightbane didn't correctly wipe threat for me last night. I'm running Omen 70123, Threat 69001, US English client. I'm pretty sure most of my raid was running a less than week old version of Omen. The code to wipe Nightbane threat is right there in Threatlib and sure looks simple enough. Could there be a problem with WipeRaidThreatOnMob()?
Apr 16, 2008I play a tank. I'm looking for an addon that will help me optimize my threat per second. Ie: just like all the mages like to show off their awesome damage meters, I want to show off my awesome threat meter. (Really what I want to do is measure my TPS and improve it over time.)Posted in: AddOn HELP!
Of course I use Omen2 and watch its reported TPS like a hawk. But the TPS number reported there is over a very short time window, it doesn't tell you my average TPS for a fight or for a whole raid. It's useful for seeing that I can burst 1500 TPS, but I don't really know from it what my sustained TPS was over the course of killing a boss or clearing trash.
I used to use Recount to produce graphs of Threat over time for a fight; you can see a sample graph. The slope of that line is what I'm interested in measuring. Unfortunately since 2.4/Omen2 Recount is no longer collecting threat data. And Recount never quite had the report I wanted anyway, that graph is awkward to generate.
The original Omen had the E-TPS column for Encounter TPS. The numbers it reported were insane though, I think it got confused by switching targets or threat drops. Any Omen2 doesn't have it, anyway.
So those are all the options I know about for measuring average TPS and none quite right. Anyone know of something better?
Jan 5, 2008_ForgeUser179692 posted a message on Recap by Hawksy - Unofficial Thread of Link GoodnessYeah, I've fixed it on my client. But it seems a bit much to expect the thousands of other WAU updaters to also manually patch their copies.Posted in: General AddOns
I tried to check in a fix but got an error. I've never checked anything into the SVN before so I don't know if it's my own account (username nelson) or a general problem with the repository permissions. The error was
svn: Commit failed (details follow): svn: CHECKOUT of '/wowace/!svn/ver/57844/trunk/Recap/Recap.toc': 403 Forbidden ([url]http://dev.wowace.com[/url])
Jan 5, 2008_ForgeUser179692 posted a message on Recap by Hawksy - Unofficial Thread of Link GoodnessThis has been broken for several days now. If it can't be fixed, maybe the WowAce mirror of Recap should be removed? It's not good for WowAceUpdater to break people's addons.Posted in: General AddOns
Nov 30, 2007Posted in: Raid AddOnsQuote from maniac70 »The aggro seems to "jump" so that one moment I am where I would expect to be aggrowise and the next moment I am very low on threat (or all others are really high).
I'm seeing this bug too. I run WowAceUpdater every couple of days, been a problem for the last week or so.
- To post a comment, please login or register a new account.