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.
I started PitBull recently, which is my very own unit frames implementation.
What sets it apart from other unit frames, such as agUF, is that almost everything is run in a modular fashion.
I have also paid extremely close attention to performance, especially with regards to frame recycling.
For example, if you hide one frame, all its child frames go into a big recycle bin. If you show another frame after that point, instead of making its own new children frames, it will reach into the recycle bin and reuse them. This cuts down on the number of unused frames immensely.
PitBull is made to be extremely modular and extensible, so as it progresses along, I hope you all like it.
Note: do not ask me for screenshots. If you wish to supply your own screenshots and post them here, that's fine.
The options for combo points escape me. Is there no graphical option. I just want huge big obvious something, the number is very elegant, but I'd rather I have something obvious to see at a glance.
Loving this mod with ever additional feature and every new bug fix.
Reposting this here, as it seemed to get buried in the other thread.
Interesting bug, that would be sweet as a feature.
When selecting a different layout. I originally have ABF selected, with the portrait shown. If I go directly to Seerah the portrait looks basically the same. A closeup on the character in questions head. BUT.... if I start with ABF, and then select OUF first (which does not have a portrait) then select Seerah, the portrait is a full body image of the character in question (and man do I love this). Then when going back to ABF it still uses the full body 3D model of the chracter.
upon ReloadUI the image goes back to the image of just the chracters face. (thats on both the ABF and the Seerah).
Now, what I would love to see is the feature / option to display a full character 3D model rather than just the face. As you have probably seen as it goes through its various animations there are times it pans outside of the frame. Id much rather have the full model. Just looks so much better.
Thanks for all your hard work. Your time and insight are appreicated.
added: can anyone else try what I describe above, to see if the same thing occurs for you or if its some sort of conflict with another mod on my system?
The options for combo points escape me. Is there no graphical option. I just want huge big obvious something, the number is very elegant, but I'd rather I have something obvious to see at a glance.
Loving this mod with ever additional feature and every new bug fix.
Good job guys.
Are we gonna be all ckknigt mods soon?
There is a graphical combo point indicator, but due to the new package setup, the path to the graphic is now wrong.
When trying to access the target aura colors via Niagara/Waterfall (works fine via FuBar dropdown though):
[2007/04/28 19:32:04-899-x10]: PitBull_Aura\Aura.lua:734: attempt to index field '?' (a nil value)
Waterfall-1.0-33871 (Waterfall-1.0):253: in function <...AddOns\Waterfall-1.0\Waterfall-1.0\Waterfall-1.0.lua:250>
Waterfall-1.0-33871 (Waterfall-1.0):730: in function `FeedAceOptionsTable'
Waterfall-1.0-33871 (Waterfall-1.0):370: in function `children'
Waterfall-1.0-33871 (Waterfall-1.0):1452: in function `ChangePane'
Waterfall-1.0-33871 (Waterfall-1.0):3462: in function `SetSelected'
Waterfall-1.0-33871 (Waterfall-1.0):3566: in function <...AddOns\Waterfall-1.0\Waterfall-1.0\Waterfall-1.0.lua:3564>
---
Edit: Also, the borders around my auras indicating whether they're a buff or debuff have disappeared. Anyone know how to re-enable that feature?
Noticed recently the castbar on targetframe seems to be sticking sometimes, even if I change targets the old frame is still there, long after the cast is over, and on any target afterwards. It goes away if I try casting something with myself targeted, but still annoying :)
Noticed recently the castbar on targetframe seems to be sticking sometimes, even if I change targets the old frame is still there, long after the cast is over, and on any target afterwards. It goes away if I try casting something with myself targeted, but still annoying :)
Confirmed for r33871, also for target of target's target frame.
Edit: r34013, sorry. Was looking at the wrong previous post for the version number >.>
I just DLed the latest PitBull to test the Druid mana bar.
Now WoW crashes every time I try to switch out of bear.
ERROR#132 (0x85100084) Fatal Exception
Program: C:\World of Warcraft\WoW.exe
Execption: 0xC0000005 (ACCESS_VIOLATION) at 001B:00753634
The instruction at "0x00753634" referenced memory at "0x0000000C".
The memory could not be read.
I don't believe this has anything to do with PitBull. I've gotten this error before (several times), and it's usually caused by something else (file permissions, which is why is "could not be read"). Delete your Cache/WDB folder, and if it still happens, delete Cache/WDB and WTF. If it still happens after that, run the repair utility. (Although just deleting WDB did it for me every time).
With 34041, the first time I repeated the error, I got an access violation and wow crashed, yay.
reloaded wow, tried again,
PitBull-r34041\Spark\Spark.lua:42: attempt to perform arithmetic on upvalue 'energy_lasttick' (a nil value) Upon casting a heal, shift cat, shift back to human.
Edit: Just got the crash again, the crash happens on shifting to cat.
Edit2: Logged back in and was still in cat, got the crash again shifting to human. And again shifting into cat, whee.
Edit3: Disabled the druidmana thingy, not crashing anymore, still getting the spark error though.
If the spark module is still having problems for druids upon shifting, please post _FULL_ errors with the current revision. Thanks :)
Other than that my rogue the spark works even I'm full energy, but for caster like Paladin, Mage, Priest, Shaman anything with Mana.
I don't see it works like the rogue one does but after I cast something like any spell, I started to see the spark but it only did once even I'm not 100% mana yet.
If the spark module is still having problems for druids upon shifting, please post _FULL_ errors with the current revision. Thanks :)
Other than that my rogue the spark works even I'm full energy, but for caster like Paladin, Mage, Priest, Shaman anything with Mana.
I don't see it works like the rogue one does but after I cast something like any spell, I started to see the spark but it only did once even I'm not 100% mana yet.
The rogue energy tick always shows when the next tick will be. Useful for knowing when to use your opener.
The spark for mana regen's only useful to show you when you exit the FSR, past that it doesn't tell you anything
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI started PitBull recently, which is my very own unit frames implementation.
What sets it apart from other unit frames, such as agUF, is that almost everything is run in a modular fashion.
I have also paid extremely close attention to performance, especially with regards to frame recycling.
For example, if you hide one frame, all its child frames go into a big recycle bin. If you show another frame after that point, instead of making its own new children frames, it will reach into the recycle bin and reuse them. This cuts down on the number of unused frames immensely.
PitBull is made to be extremely modular and extensible, so as it progresses along, I hope you all like it.
Note: do not ask me for screenshots. If you wish to supply your own screenshots and post them here, that's fine.
Wiki link: http://wowace.com/wiki/PitBull
Wishlist: http://wowace.com/wiki/PitBull/Wish_List
Loving this mod with ever additional feature and every new bug fix.
Good job guys.
Are we gonna be all ckknigt mods soon?
PitBull_Portrait r31316
Errors on startup after updating from a previous revision, closing the game, and then logging back in on a different toon:
[2007/04/28 17:53:02-896-x1]: PitBull_Portrait\Portrait.lua:76: attempt to call local 'wrap' (a nil value)
---
[2007/04/28 17:53:24-896-x1]: PitBull_Portrait\Portrait.lua:16: attempt to call method 'GetUnitFrame' (a nil value)
---
No noticeable symptoms yet. Tried a UI reload, only the first error re-occurred.
Edit: The second error seems to occur periodically at run-time. I've got 4 in my BugSack atm. Not sure what triggers it.
Getting the same errors.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium:p
PitBull-r34013\Spark\Spark.lua:42: attempt to perform arithmetic on upvalue 'energy_lasttick' (a nil value)
Cast, shift cat, shift back.
Interesting bug, that would be sweet as a feature.
When selecting a different layout. I originally have ABF selected, with the portrait shown. If I go directly to Seerah the portrait looks basically the same. A closeup on the character in questions head. BUT.... if I start with ABF, and then select OUF first (which does not have a portrait) then select Seerah, the portrait is a full body image of the character in question (and man do I love this). Then when going back to ABF it still uses the full body 3D model of the chracter.
upon ReloadUI the image goes back to the image of just the chracters face. (thats on both the ABF and the Seerah).
Now, what I would love to see is the feature / option to display a full character 3D model rather than just the face. As you have probably seen as it goes through its various animations there are times it pans outside of the frame. Id much rather have the full model. Just looks so much better.
Thanks for all your hard work. Your time and insight are appreicated.
added: can anyone else try what I describe above, to see if the same thing occurs for you or if its some sort of conflict with another mod on my system?
Thanks
As posted in the other thread, there is an old mod called Pitbull_Portrait at http://files.wowace.com/PitBull_Portrait/
When the package is split out, WAU is seeing this old mod and overwriting the new one.
A temp fix is to manually download pitbull and copy the files in Portraits into the PitBull_Portrait folder, overwriting whats there.
There is a graphical combo point indicator, but due to the new package setup, the path to the graphic is now wrong.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHey, thanks for reposting this. I missed it in the other thread, and it solves that error like a charm.
[2007/04/28 19:32:04-899-x10]: PitBull_Aura\Aura.lua:734: attempt to index field '?' (a nil value)
Waterfall-1.0-33871 (Waterfall-1.0):253: in function <...AddOns\Waterfall-1.0\Waterfall-1.0\Waterfall-1.0.lua:250>
Waterfall-1.0-33871 (Waterfall-1.0):730: in function `FeedAceOptionsTable'
Waterfall-1.0-33871 (Waterfall-1.0):370: in function `children'
Waterfall-1.0-33871 (Waterfall-1.0):1452: in function `ChangePane'
Waterfall-1.0-33871 (Waterfall-1.0):3462: in function `SetSelected'
Waterfall-1.0-33871 (Waterfall-1.0):3566: in function <...AddOns\Waterfall-1.0\Waterfall-1.0\Waterfall-1.0.lua:3564>
---
Edit: Also, the borders around my auras indicating whether they're a buff or debuff have disappeared. Anyone know how to re-enable that feature?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumConfirmed for r33871, also for target of target's target frame.
Edit: r34013, sorry. Was looking at the wrong previous post for the version number >.>
Now WoW crashes every time I try to switch out of bear.
ERROR#132 (0x85100084) Fatal Exception
Program: C:\World of Warcraft\WoW.exe
Execption: 0xC0000005 (ACCESS_VIOLATION) at 001B:00753634
The instruction at "0x00753634" referenced memory at "0x0000000C".
The memory could not be read.
I don't believe this has anything to do with PitBull. I've gotten this error before (several times), and it's usually caused by something else (file permissions, which is why is "could not be read"). Delete your Cache/WDB folder, and if it still happens, delete Cache/WDB and WTF. If it still happens after that, run the repair utility. (Although just deleting WDB did it for me every time).
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumreloaded wow, tried again,
PitBull-r34041\Spark\Spark.lua:42: attempt to perform arithmetic on upvalue 'energy_lasttick' (a nil value) Upon casting a heal, shift cat, shift back to human.
Edit: Just got the crash again, the crash happens on shifting to cat.
Edit2: Logged back in and was still in cat, got the crash again shifting to human. And again shifting into cat, whee.
Edit3: Disabled the druidmana thingy, not crashing anymore, still getting the spark error though.
Other than that my rogue the spark works even I'm full energy, but for caster like Paladin, Mage, Priest, Shaman anything with Mana.
I don't see it works like the rogue one does but after I cast something like any spell, I started to see the spark but it only did once even I'm not 100% mana yet.
The rogue energy tick always shows when the next tick will be. Useful for knowing when to use your opener.
The spark for mana regen's only useful to show you when you exit the FSR, past that it doesn't tell you anything
-
View User Profile
-
View Posts
-
Send Message
Curse Premium