Okay, I've done some hacking to increase performance. Mind testing with the latest version of PitBull, LibDogTag-3.0, and LibDogTag-Unit-3.0?
My latest testing on monday/thuesday was done with the latest LibDogTag-3.0 and Pitbull version. I used this versions for nearly one hour until I reverted.
There are several mini lag spikes. They are around 1 second and occur on different events...
- raid player is dying
- raid player releasing corpse
- raid player re-enter instance
- raid player changed group in raid (moved from group 1 to 6 for instance)
If only one (1) event triggers, its like an short "hicks" and you wont experience it if you are lazy. But if you have 3-5 players dying and they release their corpses one after another you get an "freeze chain" of multiple short freezes and this is an real problem.
The current combination of LibDogTag-3.0 and Pitbull is much better than the first release of LibDogTag-3.0 + Pitbull. The freezes where around 3-5 seconds short after the release. They are now 1 second or shorter but still very anoying and an real problem if you heal and must react. Most 25 raid fights are dynamic and fast reaction & movement is crucial. Short freezes can be the reason for an wipe chain and therefore is Pitbull currently no option for 25 raids.
EDIT: I can do further tests and maybe tweak your changes to improve performance, but I need some hints what I can do.
Seeing as you mentioned your testing on Monday, I assume it was before the changes I made. That's why I asked you to update those addons and libraries before testing again. If you could test with those, that'd be useful.
Seeing as you mentioned your testing on Monday, I assume it was before the changes I made. That's why I asked you to update those addons and libraries before testing again. If you could test with those, that'd be useful.
The test was done Thuesday around 21:00 GMT and I updated all ACE modules right before I started.
Anyway, I will do another test tomorrow and will update all modules before I start.
i switched to xperl but it seems that i got it there as well the issues with join/leave/change group raid issues. And as well in xperl as in pitbull i turned of the raid configuration and use grid as raid. Maybe it is grid that is buggie? I have no clue, i just giving the problems what i encounter. I have no idea about libs and so on. What i aslo found strange is that 2 weeks ago the wowaceupdater started to put libs in my addons folder. First you only got grid (example)and then to let it work wowaceupdater put a lot of those libs in my addons folder. Is that normal?
ps:sorry for bad english and keep up the good work you put in the addons
i switched to xperl but it seems that i got it there as well the issues with join/leave/change group raid issues. And as well in xperl as in pitbull i turned of the raid configuration and use grid as raid. Maybe it is grid that is buggie? I have no clue, i just giving the problems what i encounter. I have no idea about libs and so on. What i aslo found strange is that 2 weeks ago the wowaceupdater started to put libs in my addons folder. First you only got grid (example)and then to let it work wowaceupdater put a lot of those libs in my addons folder. Is that normal?
ps:sorry for bad english and keep up the good work you put in the addons
You have for some reason changed from "embeded" (all libs inside each addonfolder)to "disembeded" (Each lib in its own folder in the main stucture), There should be settings for this in the downloader.
From what i have heard Grid has also been effected by this.
Using PitBull for raid frames seems to me like it would be asking for trouble with freezing or framerate issues, since PitBull is such a heavyweight addon.
Do the people having problems have auras enabled for raid frames?
Seeing as you mentioned your testing on Monday, I assume it was before the changes I made. That's why I asked you to update those addons and libraries before testing again. If you could test with those, that'd be useful.
Hey Ck,
Since updating to the latest (r77449), the issue with auras not updating on party frames seems to have been fixed, although I have noticed that occasionally random UFs will show incorrect power/health bar colouring. For example a hunter will have a rogue coloured power bar, or another character might show a blue health bar instead of the global green colour I have set (class coloured health bars is turned off for all UFs). Doesn't happen often, but every now and then. Also, just wondering if you and/or Ellipsis have been able to make any progress on the following issue, thanks again for the time you have put in to this mod!
Quote from Fengor1 »
Hey Ellipsis,
Currently running PitBull 67004, but also noticing this in 65512 (in fact been noticing it back since about 62699). As per the picture included, sometimes aura buff/debuffs will appear momentarily on the wrong frame before switching to their correct positions. This happens so fast that that you have to be really quick to see it happen; in fact the attached pic is a frame from a movie that I captured in game. The very next frame shows the buff in it's correct position. This happens when solo or in party/raid, and I am using split config option to separate buffs/debuffs. Any ideas?
Quote from Ellipsis »
I am aware of this issue, and not exactly sure why it happens or how I can fix it properly. Since it is a rather minor issue (the flicker is annoying, but it fixes itself quickly), other bugs have been taking priority. I do want to take another look at the Aura layout code soon, though, and hopefully fix this along with a few other small bugs.
It's these darn 24-hour days, they're just not long enough... WTB [Time Machine], paying well, PST!
Okay, I've done some hacking to increase performance. Mind testing with the latest version of PitBull, LibDogTag-3.0, and LibDogTag-Unit-3.0?
Ok, the promised test wasnt done on thursday but I was able to join an 25 raid on friday. I used LibDogTag-3.0 r77057, LibDogTag-Unit-3.0 r77434 and Pitbull r77449.
The behavior was the same as on my last tests on monday. I got several mini freezes on different events.
- raid player is dying
- raid player releasing corpse
- raid player re-enter instance
- raid player changed group in raid (moved from group 1 to 6 for instance)
Currently, I use only dogtags which are compatible with LibDogTag-2.0 and most are very simple default versions of pitbull. I have one more advanced dogtag-3.0 with several "HasAura" tags but this text was disabled on all frames at this test raid.
Is there an chance to see an "config switch" to force pitbul using LibDocTag-2.0 instead of 3.0? Most dogtags are compatible to 2.0 and this can help to verify the source of the freeze problem.
Speak for yourself, i converted them all, in fact it was even a complete rewrite, and i'd bet none of them are backward compatible...
Fix 3.0 ok, downgrade to 2.0 no way, better switch to another unitframe in my case.
You have for some reason changed from "embeded" (all libs inside each addonfolder)to "disembeded" (Each lib in its own folder in the main stucture), There should be settings for this in the downloader.
From what i have heard Grid has also been effected by this.
I have looked around in the wowace updater but didnt find a solution to switch of that "disembeded"
I updated with wowaceupdater last night but still having lag issues even i dont use pitbull. It more like when i enter combat or a hughe stream of info is coming to my addons that my screen shokes (hickup/freeze)its more anyoning then not playable and its mostly when i'm in group i have this. What i also see is when all group(raid sunwell, mhj or bt) enter combat its worser. Afther the start of the combat, and still in combat all goes well and at the end of combat when mobs start dying i get other shoke (freeze/hickup). I have no clue where to look or how to start fixing it. Any suggestions?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I'm reverted to Pitbull-65405 and everything is fine.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumMy latest testing on monday/thuesday was done with the latest LibDogTag-3.0 and Pitbull version. I used this versions for nearly one hour until I reverted.
There are several mini lag spikes. They are around 1 second and occur on different events...
- raid player is dying
- raid player releasing corpse
- raid player re-enter instance
- raid player changed group in raid (moved from group 1 to 6 for instance)
If only one (1) event triggers, its like an short "hicks" and you wont experience it if you are lazy. But if you have 3-5 players dying and they release their corpses one after another you get an "freeze chain" of multiple short freezes and this is an real problem.
The current combination of LibDogTag-3.0 and Pitbull is much better than the first release of LibDogTag-3.0 + Pitbull. The freezes where around 3-5 seconds short after the release. They are now 1 second or shorter but still very anoying and an real problem if you heal and must react. Most 25 raid fights are dynamic and fast reaction & movement is crucial. Short freezes can be the reason for an wipe chain and therefore is Pitbull currently no option for 25 raids.
EDIT: I can do further tests and maybe tweak your changes to improve performance, but I need some hints what I can do.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe test was done Thuesday around 21:00 GMT and I updated all ACE modules right before I started.
Anyway, I will do another test tomorrow and will update all modules before I start.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNoticed it very badly last night in BT as we switched people in and out of the groups for different bosses.
It's a nice 2-3 second pause for everything when somebody joins/leaves the raid, goes on/offline but not if they die/rez.
And my dogtag use is 'very' simple
["custom"] = "[RaidGroup] [Name:ClassColor]",
Aside from that all I have is the hp% and powerbar with no other text anywhere.
ps:sorry for bad english and keep up the good work you put in the addons
You have for some reason changed from "embeded" (all libs inside each addonfolder)to "disembeded" (Each lib in its own folder in the main stucture), There should be settings for this in the downloader.
From what i have heard Grid has also been effected by this.
Do the people having problems have auras enabled for raid frames?
I have no auras enabled on my raid frames.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHey Ck,
Since updating to the latest (r77449), the issue with auras not updating on party frames seems to have been fixed, although I have noticed that occasionally random UFs will show incorrect power/health bar colouring. For example a hunter will have a rogue coloured power bar, or another character might show a blue health bar instead of the global green colour I have set (class coloured health bars is turned off for all UFs). Doesn't happen often, but every now and then. Also, just wondering if you and/or Ellipsis have been able to make any progress on the following issue, thanks again for the time you have put in to this mod!
Ok, the promised test wasnt done on thursday but I was able to join an 25 raid on friday. I used LibDogTag-3.0 r77057, LibDogTag-Unit-3.0 r77434 and Pitbull r77449.
The behavior was the same as on my last tests on monday. I got several mini freezes on different events.
Currently, I use only dogtags which are compatible with LibDogTag-2.0 and most are very simple default versions of pitbull. I have one more advanced dogtag-3.0 with several "HasAura" tags but this text was disabled on all frames at this test raid.
Is there an chance to see an "config switch" to force pitbul using LibDocTag-2.0 instead of 3.0? Most dogtags are compatible to 2.0 and this can help to verify the source of the freeze problem.
Speak for yourself, i converted them all, in fact it was even a complete rewrite, and i'd bet none of them are backward compatible...
Fix 3.0 ok, downgrade to 2.0 no way, better switch to another unitframe in my case.
I have looked around in the wowace updater but didnt find a solution to switch of that "disembeded"