The Ols data is the problem, when we first engaged his damage done was much, much higher than everyone elses, it leveled off towards the end but is still much higher than it should have been. It was present on the whispered report but a lot lower down the list.
Here's a WWS of the same fight to show what I mean.
Do you have a screenie of the detail window for damage of OIs? My guess is that this is a lazysync hiccup and doesn't actually related to the current changes.
I don't seem to have the recount data for tonights raid anymore. Ols was running a pretty old version though around version 939 or so.
Would a lazysync issue cause so much extra damage to be added to my report? Since my friends whisper and the WWS are almost exact in the amount of damage each person did.
LazySync definitely had bugs that caused that effect. Only way to fix it is to either disable sync on your side or have others update recount to something more recent.
You can see LazySync bugs like this in the detail window, because details are not synced. So if details look sane but the totals are not, you know it's someone syncing you trash data.
Consider removing all syncing from Recount (apart from syncing combat status/pet status). I don't really find syncing a feature anymore, and in most cases, does more harm to the data because the details don't match up.
Should the failbot detect "misses the jump on Thaddius"? If so I didn't see it register the people failing that.
Also, the threat part of recount only showed data while I was attacking the mob(s). After I wasn't able to view the overall threat for the past fights (like we do with DPS/Heals).
Other than that everything seemed to work nicely. I didn't notice any lag issues or performance hits. I run with a pretty high end system though (quad core with 4gb memory).
Consider removing all syncing from Recount (apart from syncing combat status/pet status). I don't really find syncing a feature anymore, and in most cases, does more harm to the data because the details don't match up.
The only fights I can see that causing problems with is the fights that use the portal mechanic. e.g Sarth
Maybe syncing can just be enabled for those 1-2 fights it would matter on and disabled for the rest.
@xin,mik: One can already toggle/remove the sync using /recount sync.
I do kind of agree that it's hardly worth it. Good syncing that doesn't clobber bandwidth is just too hard maybe just plainly impossible. And in the few cases where sync would be good the current method doesn't work too well.
As always, the cleanest solution would be to make combat log events raid group wide while in raid instances, but i'm not sure that'll ever happen because it likely is tied to mob instantiation by distance.
On the other hand it is about expectations. People don't understand the differences that the CL can create for different observers and they want those difference to go away... though funny enough WWS and other offline solutions hardly ever get used in full sync mode. There's some psychology to this for sure ;)
That said, I do run with sync (mostly to debug/monitor if it works as intended) and given that people have reasonably up to date recounts I haven't seen sync mishaps.
@rad: Thaddeus jumps are recorded fails. If other fails work as intended my guess is that it's a bug in the library though. I'll have a look.
Hello I have seen in some UI that it is posible to have two windows simultaneously, one with dps and one with threat.
How I can to do it?
Recount does not support multiple windows. The screenshots you see where both a Recount meter and a threat meter are visible are using both Recount and Omen (or some other threat meter addon).
Yes there is, but it's "All you can see" to paraphrase Slouken. For example Kalecgos live/demon side don't share combat logs and my guess is that the same holds for Sarth drake portals.
Also from experience this isn't quite intuitive. People who you would subjectively think of always being visible to each other can have diverging combat logs. Good example is certainly Archimonde where I would regularly see diverging combat logs, but even more compact fights show this effect.
A while back someone did tests and visible was on the order of 250 yards, but it's dynamic and not always the same range. The mechanism is unknown but I think it's liked to when mobs are loaded to be visible to you server-side but I could be wrong.
Fixed the first bug (hopefully). For the second we'll need someone who has access to/knowledge of the russian locale to do the missing ones in LibBabble-Boss-3.0.
Just trying it on PTR, but happens that each time I want to use the config button in the recount main panel, it crashes the game.
To be sur, I did removed all addons but that one, then going by the addon interface, select Recount, and click on the Config button, then crashes to desktop.
Did it 20 times in a row :(
Then I logged on PTR without any addon and played for at least 15min and no crash... hard to say so if it is Recount nor not but thought i would mention it
-----
Just tried on PTR to use the chat command /recount config and crashed to desktop too
Deleted my recount.lua to get access to the initial window with the config button, and as soon as I use the config tool, crashed to desktop :(
[13:08:31] Interface\AddOns\Recount\Recount.lua:1379: attempt to index global 'BB' (a nil value)
(tail call): ?
Interface\AddOns\Recount\Recount.lua:1379: in function `AddCombatant'
Interface\AddOns\Recount\Tracker.lua:1357: in function `AddDamageData'
Interface\AddOns\Recount\Tracker.lua:313: in function <Interface\AddOns\Recount\Tracker.lua:281>
Interface\AddOns\Recount\Tracker.lua:706: in function `?'
...tack\lib\CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...tack\lib\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
[string "safecall Dispatcher[21]"]:4: in function <[string "safecall Dispatcher[21]"]:4>
[C]: ?
[string "safecall Dispatcher[21]"]:13: in function `?'
...tack\lib\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
...AddOns\Bartender4\libs\AceEvent-3.0\AceEvent-3.0.lua:73: in function <...AddOns\Bartender4\libs\AceEvent-3.0\AceEvent-3.0.lua:72>
Removed LibBabble-Boss-3.0 again and replaced it with a mobID table (pain to get it but now it's done.) This means it should work for all locales and not rely on string translations in any way.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Here's a WWS of the same fight to show what I mean.
http://wowwebstats.com/y4fyex4iod1pg?s=734231-779505
[edit]
Performance seemed noticeably better, didn't notice any pauses or freezes when dropping combat that I would sometimes experience.
Does OIs use an oldish recount?
Would a lazysync issue cause so much extra damage to be added to my report? Since my friends whisper and the WWS are almost exact in the amount of damage each person did.
You can see LazySync bugs like this in the detail window, because details are not synced. So if details look sane but the totals are not, you know it's someone syncing you trash data.
http://www.wowace.com/projects/recount/files/1180-r1022/
http://www.wowace.com/projects/recountfailbot/files/11-r9/
http://www.wowace.com/projects/recountthreat/files/70-r42/
http://www.wowace.com/projects/recountguessedabsorbs/files/20-r11/
Should the failbot detect "misses the jump on Thaddius"? If so I didn't see it register the people failing that.
Also, the threat part of recount only showed data while I was attacking the mob(s). After I wasn't able to view the overall threat for the past fights (like we do with DPS/Heals).
Other than that everything seemed to work nicely. I didn't notice any lag issues or performance hits. I run with a pretty high end system though (quad core with 4gb memory).
The only fights I can see that causing problems with is the fights that use the portal mechanic. e.g Sarth
Maybe syncing can just be enabled for those 1-2 fights it would matter on and disabled for the rest.
I do kind of agree that it's hardly worth it. Good syncing that doesn't clobber bandwidth is just too hard maybe just plainly impossible. And in the few cases where sync would be good the current method doesn't work too well.
As always, the cleanest solution would be to make combat log events raid group wide while in raid instances, but i'm not sure that'll ever happen because it likely is tied to mob instantiation by distance.
On the other hand it is about expectations. People don't understand the differences that the CL can create for different observers and they want those difference to go away... though funny enough WWS and other offline solutions hardly ever get used in full sync mode. There's some psychology to this for sure ;)
That said, I do run with sync (mostly to debug/monitor if it works as intended) and given that people have reasonably up to date recounts I haven't seen sync mishaps.
@rad: Thaddeus jumps are recorded fails. If other fails work as intended my guess is that it's a bug in the library though. I'll have a look.
How I can to do it?
Thanks.
PD
Excuse me if I did not search in these pages but my Inglish is not good and is difficult to me to understand all waht I read.
Recount does not support multiple windows. The screenshots you see where both a Recount meter and a threat meter are visible are using both Recount and Omen (or some other threat meter addon).
Also from experience this isn't quite intuitive. People who you would subjectively think of always being visible to each other can have diverging combat logs. Good example is certainly Archimonde where I would regularly see diverging combat logs, but even more compact fights show this effect.
A while back someone did tests and visible was on the order of 250 yards, but it's dynamic and not always the same range. The mechanism is unknown but I think it's liked to when mobs are loaded to be visible to you server-side but I could be wrong.
r1025
Also, there are few errors popped about russian translation missing or something, like that:
The localization link to localization is here:
http://www.wowace.com/projects/libbabble-boss-3-0/localization/
Looks like other languages may also need some translations. The translation should match what the client gives you.
I'll look into mobIDing this to save all of us the pain though... that'll take a little because I'll need to harvest all these IDs somehow.
Version r1026
All working on Live - but not on PTR
Just trying it on PTR, but happens that each time I want to use the config button in the recount main panel, it crashes the game.
To be sur, I did removed all addons but that one, then going by the addon interface, select Recount, and click on the Config button, then crashes to desktop.
Did it 20 times in a row :(
Then I logged on PTR without any addon and played for at least 15min and no crash... hard to say so if it is Recount nor not but thought i would mention it
-----
Just tried on PTR to use the chat command /recount config and crashed to desktop too
Deleted my recount.lua to get access to the initial window with the config button, and as soon as I use the config tool, crashed to desktop :(
The main reason is for the personnal datas:
L["'s DPS"] can not be translated in french that way. You have to use de "DPS of <name>" to do so.
With a string.format we just need do put %s to solve the problem.