Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
Looks good so far, was testing it out in a ZA run last night.
Once you've got boss kill tracking built into it i might have to start using it full time.
On another note, loot exclusion might be handy, but most people are going to be exporting this to things like EQDKP, where you can exclude certain items also, so i guess it's a much of a muchness. One idea for exclusion however i have no idea how you'd go about it, is if you can maybe tag items as being disenchanted, or uh, something, so it ignores items being sent to the enchanter for D/E.
Just pestering again, is there any chance that you could skin the bigwigs "proximity" window at all? It's the little window that pops up during the maiden & curator in kara, shows people that you're too close too.
by default it's some orange ugly thing, wouldn't mind it fitting with the rest of my UI a bit more :)
it's contained in the BigWigs_Extras package, under "proximity", and from the looks of it just uses the texture BigWigs\Textures\otravi-semi-full-border.tga. For some reason i don't have a screenshot of it, but that should be enough information for you to do your thing, hopefully :)
I was just about to report this issue myself. I've been trying in vain to sort out what the problem is, to no avail.
I'm getting the same thing, there's a frame being rendered ontop of the bags, which makes them unusable. Bank frame,oneview and keychain are all working fine however.
oh, by the way, reverting onebag back to r35960 fixes the issue for me.
I'm getting the same hook error as people above when i either use the dotimer skinme file, or the tinytip on. (with revision 38596.1001)
Additionally, i'm getting a frame rendered on top of the onebag frame, even with all addon skins removed. Had to disable skinner to get rid of it :(
Scratch that, was happening with skinner disabled too.
Secondly, the skin for DoTimer, it doesn't actually appear to be skinning the bars according to my skinner texture, assuming of course that's what it's supposed to do. Do i need to set DoTimer to use a specific texture number, or should it just be overriding it automatically? (using version 3.1)
Still doing it for me, slight (3 sec or so) freeze joining an AV, still freezes for about a second when dismounting as a warlock (and having the pet auto-summon).
Froze completely in eye of the storm, had to terminate wow.exe. Haven't tried AB or WSG yet, and now the login server seems to be dead, so i can't get back in to do more testing.
Hey there, I will take a look at fixing it tonight, please hang on :)
Cool, much appreciated.
I've rolled back to 35469.1002, and the problem is reduced somewhat, i still get pauses for about 5 seconds when joining battlegrounds, and i get a half to one second "freeze" when dismounting with my warlock, which i'm assuming has something to do with the pet auto summoning. Not sure if that'll help any or not :)
This is not a bug that's pertaining to any recent build but is it known that DoTs often drop off from Chronometer even though they're still on mobs? This seems to happen really quite often on boss encounters when tons of shit is going on and off the boss. There's another warlock and myself who use Chronometer and we are both noticing this a lot since we've started getting back into raiding in BC.
Yeah i get the same issues, have since i started testing with chronometer ages ago, which was problematic enough to force me back to use DotTimers, which is a shame as i'd much rather use chronometer.
0
Once you've got boss kill tracking built into it i might have to start using it full time.
On another note, loot exclusion might be handy, but most people are going to be exporting this to things like EQDKP, where you can exclude certain items also, so i guess it's a much of a muchness. One idea for exclusion however i have no idea how you'd go about it, is if you can maybe tag items as being disenchanted, or uh, something, so it ignores items being sent to the enchanter for D/E.
Anywho keep up the good work :)
0
0
was doing that for me too, but i uninstalled it then re-installed and that seemed to fix it, now it's working fine.
0
That's cool, i'll just edit the texture itself to a more inviting colour than orange. Thanks for the attempt :)
0
Just pestering again, is there any chance that you could skin the bigwigs "proximity" window at all? It's the little window that pops up during the maiden & curator in kara, shows people that you're too close too.
by default it's some orange ugly thing, wouldn't mind it fitting with the rest of my UI a bit more :)
it's contained in the BigWigs_Extras package, under "proximity", and from the looks of it just uses the texture BigWigs\Textures\otravi-semi-full-border.tga. For some reason i don't have a screenshot of it, but that should be enough information for you to do your thing, hopefully :)
0
0
I'm getting the same thing, there's a frame being rendered ontop of the bags, which makes them unusable. Bank frame,oneview and keychain are all working fine however.
oh, by the way, reverting onebag back to r35960 fixes the issue for me.
0
Additionally, i'm getting a frame rendered on top of the onebag frame, even with all addon skins removed. Had to disable skinner to get rid of it :(
Scratch that, was happening with skinner disabled too.
0
0
Firstly, is it at all possible for you to add skinning to Xcalc? (http://www.wowinterface.com/downloads/info5281-Xcalc.html)
Secondly, the skin for DoTimer, it doesn't actually appear to be skinning the bars according to my skinner texture, assuming of course that's what it's supposed to do. Do i need to set DoTimer to use a specific texture number, or should it just be overriding it automatically? (using version 3.1)
0
Upgraded to r37551 this morning.
Still doing it for me, slight (3 sec or so) freeze joining an AV, still freezes for about a second when dismounting as a warlock (and having the pet auto-summon).
Froze completely in eye of the storm, had to terminate wow.exe. Haven't tried AB or WSG yet, and now the login server seems to be dead, so i can't get back in to do more testing.
0
Cool, much appreciated.
I've rolled back to 35469.1002, and the problem is reduced somewhat, i still get pauses for about 5 seconds when joining battlegrounds, and i get a half to one second "freeze" when dismounting with my warlock, which i'm assuming has something to do with the pet auto summoning. Not sure if that'll help any or not :)
0
Yeah i get the same issues, have since i started testing with chronometer ages ago, which was problematic enough to force me back to use DotTimers, which is a shame as i'd much rather use chronometer.
0
Is there anyway perhaps as a bit of a work-around, it'd be possible to set a gap width between each party/pet rather than globally?
Bit of a pain no doubt, but yeah.
0
essentially what i used to do (and hopefully plan to do in the future), is somewhat like the following:
pet1 pet2 playerpet targetoftarget pet3 pet4
party1 party2 player target party3 party4
much like that, across the whole screen.