PitBull Unit Frames 4.0
PitBull Unit Frames 4.0
Woof. Arf. Yip.
Getting Started:
You can help translate PitBull for your language with the localization tool.
Classic
PitBull works with WoW Classic! Classic Era/Vanilla is supported in
v4.3.x-vanilla
releases. Cataclysm Classic is supported in v4.2.x
releases
(the same releases retail use).
Classic Era caveats:
- Aura duration is not available from the API, so PitBull uses LibClassicDurations to show them. The duration can be inaccurate if it's affected by rank or talents.
- Cast info is only available for your spells from the API. PitBull uses LibClassicCasterino to show cast bars for other units, but this can be inaccurate since there is a lot of guess-work involved.
Download
CurseForge: https://www.curseforge.com/wow/addons/pitbull-unit-frames-4-0
Wago: https://addons.wago.io/addons/pitbull4
WoWInterface: https://www.wowinterface.com/downloads/info20021
I guarantee once you figure out the nuances of PB4 you'll wonder how come you wanted to hang onto PB3 for so long. Honestly, the configuration process is that much better. Setups that might take hours to make in PB3 can be done in a fraction of the time with PB4. All I can say is stick with working with PB4, because as Shefki states it's much easier to make a transition early then hope for someone else to support an old addon or even recreate it.
You can apply layouts to multiple frames or to one frame.
You may want to look at the guide linked above if you are having trouble.
@ssstartbr: No
can i copy pitbull3 profile to pitbull4?
I notice that beta 9 is up I'll try it and report back if problems persist.
Solo, just in Tirisfal.
Video is smooth, great, nothing wrong.
Kill a bat, fps shoots to 20fps. Only happening with pitbull on so there is no conflict. It is quite mind boggling actually.
With pitbull enabled: Starts 200-ish FPS as normal.
Get in combat, get out of combat - Drops to 70-50-30-12 then hovers around 20.
Without pitbull enabled: Stays around 200 like it should.
This is with the new beta.
Can you be more specific about how you're reproducing this. Solo play, party, raid? Can you reproduce this with only PitBull4 running and no other addons? There's always the possibility of some other addon is causing an interaction.
For that matter are you possibly moving your camera around? I can make pretty dramatic changes in my frame rates by moving my camera around, especially in the outside world with draw distances turned up.
Can you turn off modules slowly until you can't reproduce it anymore. Perhaps it's something related to a specific module. Start with the ones that are least important like "VisualHeal" and "CastBarLatency" and work your way towards more critical things. Turn one off at a time, see if you can reproduce and continue until you see it stop.
Time: 03/23/10 13:18:08
Count: 1
Stack: Interface\AddOns\PitBull4\Controls\Controls.lua:31: in function `?'
Interface\AddOns\PitBull4\Controls\Controls.lua:63: in function `Delete'
...terface\AddOns\PitBull4\Controls\BetterStatusBar.lua:605: in function `SetIcon'
...erface\AddOns\PitBull4\ModuleHandling\BarModules.lua:456: in function `UpdateFrame'
Interface\AddOns\PitBull4\ModuleHandling\Module.lua:319: in function `Update'
Interface\AddOns\PitBull4_CastBar\CastBar.lua:206: in function `ClearFramesByGUID'
Interface\AddOns\PitBull4_CastBar\CastBar.lua:310: in function `FixCastData'
Interface\AddOns\PitBull4_CastBar\CastBar.lua:63: in function `FixCastDataAndUpdateAll'
Interface\AddOns\PitBull4_CastBar\CastBar.lua:37: in function <Interface\AddOns\PitBull4_CastBar\CastBar.lua:37>
Locals: self = PitBull4_Texture_18 {
0 = <userdata>
Delete = <function> defined @Interface\AddOns\PitBull4\Controls\Controls.lua:49
kind = "Texture"
}
(*temporary) = nil
(*temporary) = PitBull4_Texture_18 {
0 = <userdata>
Delete = <function> defined @Interface\AddOns\PitBull4\Controls\Controls.lua:49
kind = "Texture"
}
(*temporary) = false
(*temporary) = "attempt to call method 'SetTexCoordModifiesRect' (a nil value)"