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.
With the buff/debuff changes in 3.0, you can now see the time left ON all buffs/debuffs on anyone. While I think this is an ok idea (kind of useless) it eats up a lot of resources when a lot of people are attacking a target (for example, a boss) he has a lot of debuffs on him, all with timers constantly being refreshed, this causes a lot of lag.
I just did AV and most of the horde team was on Van. there were at least 35 debuffs on the target, and with pitbull, they all have ticking timers / borders for each one, and they were all being constantly refreshed. This made me have like...5fps for the fight.
Is there any way to change it so only timers/ticking borders show for my debuffs only? I don't have a pic to explain the problem, but it should be simple.
with only Buggrabber/Bugsack/Pitbull on also no aura, no errors either.
I installed the latest version as well.
In fact, the latest version made all my unit frames disappear again =/
All my pitbull frames just disappeared >< Been working fine the last two days.
PitBull-r53016\PitBull.lua:4802: attempt to index field 'colorConstants' (a nil value)
PitBull-r53016\PitBull.lua:4594: in function `UpdateFrame'
PitBull-r53016\PitBull.lua:4551: in function `object_method'
I am having serious issues getting PB to work at all...I updated to the newest update...Everything shows up in my AddOn list. Except ALL the libraries that are listed below Pitbull 3.0 , are red...no matter how much I update it.
When I log on , I get nothing but a black empty frame...Why are all the Lib's not updating ?
They are not libraries, but modules; and if you have downloaded and installed the latest version from Curse, you can disable/delete them all.
When I only enable Pitbull, I can at least see my Pitbull Unitframes, but the Blizzard ones are also there (no option to disable them). When I install Chinchilla e.g. also, I don't get Pitbull to show at all.
Describe this problem more for me. Include any ways to reproduce it.
It happens often any time someone joins the raid during combat. It happens on both my raid frames as well as target and target of target frames. I also saw it happen on the mana bars of my party frames once since 3.0. The only way I've found to fix this problem is to reload UI or go through a load screen.
Basically everything Arkive said except it happens in any raid and can affect my other frames as well.
All my pitbull frames just disappeared >< Been working fine the last two days.
PitBull-r53016\PitBull.lua:4802: attempt to index field 'colorConstants' (a nil value)
PitBull-r53016\PitBull.lua:4594: in function `UpdateFrame'
PitBull-r53016\PitBull.lua:4551: in function `object_method'
Same problem with v3.2.7, Pitbull does not load. I reverted to v3.2.6 and Pitbull loads fine.
It happens often any time someone joins the raid during combat. It happens on both my raid frames as well as target and target of target frames. I also saw it happen on the mana bars of my party frames once since 3.0. The only way I've found to fix this problem is to reload UI or go through a load screen.
Basically everything Arkive said except it happens in any raid and can affect my other frames as well.
Okay if that's what you meant by what you described. You're not going to like the answer. It's a known issue. One that I'm not sure can really be fixed without a rewrite of PitBull. It's a design error that we've tried to find work arounds for. But ultimately the conflict is between the idea of only creating minimal numbers of frames/reusing frames and the templating system only letting us do some things out of combat. We've played whack a mole but frankly, it's a design flaw that would be better resolved with a rewrite. Which is very likely not coming soon.
Believe me I spent a lot of time trying to fix those problems before I finally gave up.
With the buff/debuff changes in 3.0, you can now see the time left ON all buffs/debuffs on anyone. While I think this is an ok idea (kind of useless) it eats up a lot of resources when a lot of people are attacking a target (for example, a boss) he has a lot of debuffs on him, all with timers constantly being refreshed, this causes a lot of lag.
I just did AV and most of the horde team was on Van. there were at least 35 debuffs on the target, and with pitbull, they all have ticking timers / borders for each one, and they were all being constantly refreshed. This made me have like...5fps for the fight.
Is there any way to change it so only timers/ticking borders show for my debuffs only? I don't have a pic to explain the problem, but it should be simple.
Those timers aren't going to kill your frame rate that much. But I can understand the desire to not show that information. Open a ticket on curseforge for this.
Okay if that's what you meant by what you described. You're not going to like the answer. It's a known issue. One that I'm not sure can really be fixed without a rewrite of PitBull. It's a design error that we've tried to find work arounds for. But ultimately the conflict is between the idea of only creating minimal numbers of frames/reusing frames and the templating system only letting us do some things out of combat. We've played whack a mole but frankly, it's a design flaw that would be better resolved with a rewrite. Which is very likely not coming soon.
Believe me I spent a lot of time trying to fix those problems before I finally gave up.
Fair enough. That said, what changed that caused the bug to become so much more prominent? The number of players in BG's and/or the mechanics of people joining/leaving has not changed (that I'm aware of). Is there a way you can add something that caches unit frame additions/deletions when the player is in combat and then commits those changes after the player exits combat? Or would it be possible to allocate some extra frames so if Pitbull finds itself in this position it can deal with it and then trash the old frames after combat? I think most of us would be willing to give up a little extra memory. I know I'm probably drasticaly over-simplifying this :/
I had the same issue (unit frames disappearing, /pitbull not working) until I disabled Auctioneer...looks like there was a problem with the 5.1.3620 Suite they released today.
After having some issues with the patch.. and having to re-do my ui **3** times I've had a lot of time to think. I am a hunter. Pre-patch I was using 3 buttons (using bartender with a ranged, melee, and hunters mark button) above where I had my target to do a small range check.
I was wondering if I could do something similar with Pitbull. Ex: A small bar attached to my Target frame that changes color depending on which range I'm in. Red for too far, white for far enough for Hunters Mark, green for ranged and yellow for melee.
Is such a thing possible? Or do I have to resort to the extra buttons in the center of my screen?
Whenever i mouseover my party frames (only party frames, player/target etc is fine) the tooltip doesnt show up. Any idea what might cause this ?
Thanks in advance.
Noticed a newer of version of pitbull, installed that and now barely anything works correctly.
My unit frames are now filled with text, pretty unusable atm.
I just did AV and most of the horde team was on Van. there were at least 35 debuffs on the target, and with pitbull, they all have ticking timers / borders for each one, and they were all being constantly refreshed. This made me have like...5fps for the fight.
Is there any way to change it so only timers/ticking borders show for my debuffs only? I don't have a pic to explain the problem, but it should be simple.
I installed the latest version as well.
In fact, the latest version made all my unit frames disappear again =/
Same issue, although Target is affected too. Player works fine though.
PitBull-r53016\PitBull.lua:4802: attempt to index field 'colorConstants' (a nil value)
PitBull-r53016\PitBull.lua:4594: in function `UpdateFrame'
PitBull-r53016\PitBull.lua:4551: in function `object_method'
They are not libraries, but modules; and if you have downloaded and installed the latest version from Curse, you can disable/delete them all.
It happens often any time someone joins the raid during combat. It happens on both my raid frames as well as target and target of target frames. I also saw it happen on the mana bars of my party frames once since 3.0. The only way I've found to fix this problem is to reload UI or go through a load screen.
Basically everything Arkive said except it happens in any raid and can affect my other frames as well.
Screenshot of the problem:
http://img395.imageshack.us/img395/5681/wowscrnshot081308000946or5.jpg
Same problem with v3.2.7, Pitbull does not load. I reverted to v3.2.6 and Pitbull loads fine.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOkay if that's what you meant by what you described. You're not going to like the answer. It's a known issue. One that I'm not sure can really be fixed without a rewrite of PitBull. It's a design error that we've tried to find work arounds for. But ultimately the conflict is between the idea of only creating minimal numbers of frames/reusing frames and the templating system only letting us do some things out of combat. We've played whack a mole but frankly, it's a design flaw that would be better resolved with a rewrite. Which is very likely not coming soon.
Believe me I spent a lot of time trying to fix those problems before I finally gave up.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThose timers aren't going to kill your frame rate that much. But I can understand the desire to not show that information. Open a ticket on curseforge for this.
Fair enough. That said, what changed that caused the bug to become so much more prominent? The number of players in BG's and/or the mechanics of people joining/leaving has not changed (that I'm aware of). Is there a way you can add something that caches unit frame additions/deletions when the player is in combat and then commits those changes after the player exits combat? Or would it be possible to allocate some extra frames so if Pitbull finds itself in this position it can deal with it and then trash the old frames after combat? I think most of us would be willing to give up a little extra memory. I know I'm probably drasticaly over-simplifying this :/
Same here (as well as the betas after 3.2.7). Rolling back to 3.2.6 did the trick.
I was wondering if I could do something similar with Pitbull. Ex: A small bar attached to my Target frame that changes color depending on which range I'm in. Red for too far, white for far enough for Hunters Mark, green for ranged and yellow for melee.
Is such a thing possible? Or do I have to resort to the extra buttons in the center of my screen?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOr write a DogTag which shows something different on mouseover?
Had the same problem, tried 3.2.7 and it didn't work at all (throws lots of errors). Besides that, 3.2.7 also makes Chincilla stop working.
Reverted to 3.2.6 and both Pitbull and Chincilla work fine.