update on the warlock issue, error occurs without T12. Recount appears to only add 1 pet to warlock damage, and usually picks ebon imp (proc from curse of doom) which contributes less than 1% damage, and does NOT include main pet damage. It occasionally picks the doomguard/felguard to include instead.
Link Removed: http://www.mediafire.com/?9umqrvfnyd4npzz
link is to a combatlog (txt) of me vs a training dummy. Felhunter attacks for the first half before i put him on passive. Felhunter pulls 3.5K dps 142K dmg. fiery imp does 50K dmg 1.7K dps, and ebon imp does 16K damage, .4K dps. Recount shows ebon imp as my pet on mouseover.
Summon Fiery imp occurs on line 61
summon ebon imp occurs on line 118 and reads as follows:
8/18 22:23:49.242 SPELL_SUMMON,0x0680000003FB12B4,"Nonelia",0x511,0x0,0xF130C5F3000C9C84,"Ebon Imp",0xa28,0x0,18662,"Bane of Doom",0x20
The recount showed fiery imp when i checked early on (before an ebon imp spawned) and showed ebon imp as my pet at the end. Felhunter was not rolled in to my damage, though when 'merge pets' was no checked his damage was recorded.
I have recently had the issue with recount recording unusually high melee counts for different types of melee dps (have experienced it with ret paladins and frost dks so far). The report on World of Logs does not show this error, however
I don't know why but something in the memory handling is just causing me to dc on any fight with alot of numbers (aoe fights especially rhyo/even Occular). I really like the interface and options of Recount over skada but i just can't return to it until i can stay online while using it.
I narrowed it down to recount after running nothing else and alternating it between skada/recount on the same fight. When the fight becomes AoE intensive Skada slows client down and Recount forces DC's. I have 8GB or ddr3 ram running in a Core2Quad runing at 3ghz. I just don't see any other real conclusion as to what is causing it.
Recount has extensive controls over what data you collect. It's critical that you do not collect time-data as this is very memory intensive and in general not recommended. Further you can disable collections for certain mob types. If they are of no interest to you disabling their collection helps accumulation.
You can also disable some collection types by renaming/deleting modules in the Recount/TrackerModules directory. I do not generally recommend this because these in typical operation do not accumulate a lot of data, but they still do have some possible impact.
Need some help loading up this add on. I've been downloading every updated and out of date one to able to load up and use it. Yet i cant get thur the "load screen" part. So thats where i'm at. Enable it, wow load up screen (stuck not even have half) and get (not responding error) What am i missing? plz help.
The latest commit should use the fixed AceSerializer-3.0 and another Recount-based division by zero issue. I anticipate that more division by zero errors will surface. Please report. People on PTR should install alphas to get the fixed version. I won't be tagging this for release until PTR4.3 is clearly bound for release.
Not sure if this is fixed in the latest version. But recount for me has been showing my own dps accurately. Matches up close to what world of logs shows. But everyone else is showing much higher damage. Like millions higher.
Not sure whats changed to cause it to be this inaccurate. I'll try the newest version tomorrow night in next raid to see if its fixed.