It's nothing I can reproduce. I've now started to write down the raid members whenever it happens again (have only one raid so far though). Also I cannot remember the error messages, I *think* it was something with 'expected value but got nil'. I'll try to catch them whenever they happen again. Of course that means I have to enable syncing again, and I'm not so sure I want to have another freeze during a bossfight...

Ok, I have some error messages now. They are not from me, but from two other players using recount, who don't suffer from the 0.1 FPS issue but still receive about 1 errormessage per second.
Both have the libs in the /libs directory of Recount, while I had them directly in my AddOns folder.

Also the raid is a mix of German and English language pack.


Error messages for revision 52164:

Recount-$Revision: 52164 $\Sync.lua:359: attempt to perform arithmetic on field '?' (a table value)
Recount-$Revision: 52164 $\Sync.lua:372: attempt to perform arithmetic on field '?' (a table value)
Recount-$Revision: 52164 $\Tracker.lua:297: attempt to perform arithmetic on field '?' (a table value)


Error messages for revision 47214:

Recount-$Revision: 47214 $\Sync.lua:359: attempt to perform arithmetic on field '?' (a table value)
Recount-$Revision: 47214 $\Sync.lua:391: attempt to perform arithmetic on field '?' (a table value)
Recount-$Revision: 47214 $\Tracker.lua:297: attempt to perform arithmetic on field 'count' (a nil value)
Recount-$Revision: 47214 $\Tracker.lua:612: attempt to perform arithmetic on field 'count' (a nil value)
Recount-$Revision: 47214 $\Tracker.lua:637: attempt to perform arithmetic on field 'count' (a nil value)
Recount-$Revision: 47214 $\Tracker.lua:471: attempt to perform arithmetic on field 'count' (a nil value)

Recount-$Revision: 47214 $\Libs\ParserLib-1.1\ParserLib.lua:457: in function <... face\AddOns\Recount\Libs\ParserLib-1.1\ParserLib.lua:457>


The ParserLib message occurs on each of these 'count' messages. Maybe something wrong with ParserLib 1.1 (and isn't there PaserLib 3 meanwhile?).

Recount has both ParserLib (1.1) and Parser-3.0 as it's dependancies. Also i have no problems when running with LibParser-4.0 only. Sync disabled though.

Well the first thing that I see are the revisions, the latter one is using an ancient revision.
I suspect that it's a problem with non-updated libraries for the person with revision 47214, rather than Recount itself. He really should use WAU for updating.

Revision 52164 is a bit more interesting though, since it's new enough and only thing it's missing is the "official" sync patch. The patch that jayowen posted was revision 47214 though and mine was 53257, so had he patched stuff manually or? I'm using integrated libs myself ("/libs/") and I don't run into those errors, even in a raid where people are using mixed Recount versions.

EDIT: As for the error messages themself, they aren't that useful I'm afraid. I can see that the Tracker.lua error is in AddSyncAmount(), which means some sort of sync message must be slipping through.

He didn't patch anything, it is the standard addon without any modifications.

If the old version is the problem (it's from august btw and I think Cryect himself hasn't changed it since then) then maybe the MinimumVersion variable (in sync.lua) should be changed to reflect this.

Ahh, I was only interested in versions that was patched to not sync anymore. This is an old bug that never got fixed then?

The patch didn't change anything in the packet structure, so there should be no reason to bump the MinimumVersion number.

The libraries I was referring to are those shared libraries in libs/. You need to do full updates, because if you only up/downgrade one addon, then more recent libraries might overwrite the old one in memory. Hence you can get some funky errors when an addon expects one version of a library, but gets another one.

Recount hasn't functioned me since august now. GUI freeze, crashes etc had to jump ship to assessment for the time being. Someone in #wowace said author had taken a break or something, is that true?

Yep, Cryect (the author) had not be seen since 3 months now.

The synchronization switch only disables sending and receiving messages, your local combat log is still being parsed.
I believe the standby option is a standard Ace2 option, which is optional to implement. Hence it might be ignored by Recount at the moment.
I could probably take a look at it when I get some time, but is it really that big of a problem?

This is certainly something else then, Recount has been working fine except for the rather silly amount of synchronization messages.
And I'm not just talking personal experience, but half the guild and a lot of other people that's still using it.

Not really a big problem, but after 2 or 3 hours of AV Recount uses something like ~60Mb. It just force me to reset recount often, and as I don't look at it during pvp i'd like to disable it.

I've got a bit diferent question about Recount. Does anyone know, if it's possible to remove those 2 "silder" buttons on the right side? So the data list would be controllable only with mouse scroll.

Ive been having issues for about a month now with recount not remembering where the realtime frames should be positioned after I log back in. They tend to be in the top left corner. Does anyone have any ideas on how to fix this or what the issue might be?

Can anyone describe more or less what Recount does that Assessment does not? I ask because last night during SSC, my system dragged to 0.5 FPS about every 30 minutes until I restarted. After three times of that I realized what it was and disabled Recount. Probably the same syncing errors you all have been discussing, except I didn't get any error dialogues.

(If it's worth noting to anyone, I've never once had a problem solo or in 5/10 mans--only in SSC, and only since last night.)

I really appreciate the amount of information Recount provides me, so hopefully Assessment will be a good drop-in replacement.

Right now Assessment doesn't handle per-target information (i.e. you can't look at how much of their damage someone was doing to which targets, or how much of the damage a player took was from a given source). That's the major loss. You also lose pretty graphs.

Ouch, gotta stick with Recount then. While it was working it helped me and others realize that not enough people were moving right away to the Spitfires on Karathress (besides the fact that a lot of volleys were going off, our lowest overall DPS was still significantly higher DPS on the spitfires than the rest of the melee). If assessment can't do that, then that's no good.

I mean I guess WWS can do that sort of ex-post-facto anyway, but still I like to review things while we're wipe-recovering.

Hmm, interesting bugs I see have been popping up. I did change some sync code a few days ago disabling the sending of a lot of the data since decided a lot of it was unnecessary which I hope maybe fixed the issues.

Yeah, I kinda decided to quit cold turkey avoiding WoW altogether (otherwise I know I would see bug reports etc and delve right into coding WoW addons again). Sorry about vanishing like that was kinda a sudden decision. Basically decided I needed to stop being a lazy bum and get a job so been spending the past 3 months job searching. Good news finally got hired which means I won't be having the time to develop Recount 2 like I wanted to a few months ago (besides potential conflict of interests with my new job).

Also Kalman only Aleph Null? Aleph One is so much better (though it might be hard to count bottles of beer in Aleph One).

So will there be any updates to this great addon, or do I just give up and try to find something else that works as well as this (not possible).

Hi,

First off, thanks for creating what I consider the greatest addon in the history of WoW. Its a big loss for the community that you won't be continuing your work with it and also recount 2.

Anyway, good to hear that you have your life back on track because as always, real life > WoW.

Maybe you should send your code to Blizzard so they make it an integral part of the game :P

Hey Recount is a very cool Mod.

I could use some help.
The dps graph for some reason is up in the very top left of my UI. I can't pull it down to move it where i like to. I've tried reseting the windows, only it just moves the main window that keeps stats for the entire raid. I've even tried to remove Recount, then install it again. Anyone have the same problems.

EDIT: I resolved the problem, sorry for any inconvenience.

Perhaps I'm just overwhelmed by the functions and don't find the correct option, but how do I save the data and keep it accessible after the raid when people start to leave? With default options, the players vanish from my recount graphs if they leave the party/raid. So the time for post raid analysis is very limited.

In the settings window, there is a table-like options set. You need to check the 'eyeball' icon option next tp 'ungrouped'. The data is stilll being stored, the default options have it set so that it does not display data for people not currently in your group.