Hum there is something very weird, it seems like it analyses the data one minute later. I mean, after a complete wipe i would still see like 12k raid dps and numbers increasing on the ddmeter. Happens on overall data and current fight, problem with sync maybe ?
There was some issues with sync I fixed last night which were causing messages not to be read which resulted in everyone trying to send messages for everyone that was fixed. Basically get everyone to update to the latest version and I'm hoping it will go away due to throttling added in but need to do some testing.
I asked one of the officers in my guild to download and use Recount last night. He received the same error referenced in this post. You posted that this error is caused by a buggy version of Omen/Threat- but he doesn't have Omen/Threat downloaded at all.
1) is the syncing done automatically?
2) how can i make pet damage merge to the appropriate user?
3) I seem to be getting different damage result from everyone else?
4) the report button seems to be very small compare to the other buttons, I have to scroll over to this specific spot in order to open it, like the area to click is a lot smaller than the other icons.
Are there plans to parse anonymous pet data from your own events instead of the combat log? If so, will we eventually see a sync that would allow one player running Recount to send his merged damage to another player using Recount and vice versa? I think this would give you accurate merged damage for anonymous pet masters assuming all players with anonymous pets were using Recount.
I am unable to find an in-game method to prevent the graphs from showing up again. I clicked dps on raid and fps a couple times and then closed them all. But when I logged back on the same amount of graph windows shows up. My current solution is to delete the recount files in WTF folder.
Also I tried clicking Damage Done and my dps doesnt show like how SW Stats has your dps at the top. Great addon. Keep up the good work.
There was some issues with sync I fixed last night which were causing messages not to be read which resulted in everyone trying to send messages for everyone that was fixed. Basically get everyone to update to the latest version and I'm hoping it will go away due to throttling added in but need to do some testing.
I updated the addon yesterday afternoon (which therefore should have been after the fix you mentioned) and used it in my raid last night. Unfortunately, I was still having the same issue. After a wipe on Karathress, I would have to wait up to five minutes for everyone's numbers to stop ticking upward. Resetting Recount (/recount reset) would reset previously accumulated data, but there would still be bits ticking in.
This is absolutely amazing Cryect, I haven't used it since around when you first posted here, and it's come a long way.
Just one small tweak to the death details: it autoselects the first death, but 99% of the time what I want to view is acutally the *last* death. I kept confusing my raid last night when I was talking about the wrong death.
I asked one of the officers in my guild to download and use Recount last night. He received the same error referenced in this post. You posted that this error is caused by a buggy version of Omen/Threat- but he doesn't have Omen/Threat downloaded at all.
Any thoughts?
Threat is a part of Recount. (Threat's a library that can be used by other addons).
Originally Posted by Bluesfear
some questions concerning the addon recount:
1) is the syncing done automatically?
2) how can i make pet damage merge to the appropriate user?
3) I seem to be getting different damage result from everyone else?
4) the report button seems to be very small compare to the other buttons, I have to scroll over to this specific spot in order to open it, like the area to click is a lot smaller than the other icons.
1) Yes
2) It tries to automatically do it but few issues with pets of the same name I'm going to address shortly
3) Sync issues seems to be messing it up
4) The click area is the exact same so not sure?
Originally Posted by Vulajin
I updated the addon yesterday afternoon (which therefore should have been after the fix you mentioned) and used it in my raid last night. Unfortunately, I was still having the same issue. After a wipe on Karathress, I would have to wait up to five minutes for everyone's numbers to stop ticking upward. Resetting Recount (/recount reset) would reset previously accumulated data, but there would still be bits ticking in.
Argh, I wish AceComm had a way to expose the queue size :-/ Back to work on that.
Originally Posted by Kyth
This is absolutely amazing Cryect, I haven't used it since around when you first posted here, and it's come a long way.
Just one small tweak to the death details: it autoselects the first death, but 99% of the time what I want to view is acutally the *last* death. I kept confusing my raid last night when I was talking about the wrong death.
Ah, good idea.
Originally Posted by Vonwen
Hum well the verchk tells me everyone has updated today and still the same issue ;x
Bwah once again. Making a slight change that hopefully will fix it a little (I wasn't seeing it yesterday so thought it went away).
Originally Posted by koolfaze
I am unable to find an in-game method to prevent the graphs from showing up again. I clicked dps on raid and fps a couple times and then closed them all. But when I logged back on the same amount of graph windows shows up. My current solution is to delete the recount files in WTF folder.
Also I tried clicking Damage Done and my dps doesnt show like how SW Stats has your dps at the top. Great addon. Keep up the good work.
Yesterday in SSC we've had quite unpleasant issue regarding Recount. All people who were using Recount, had major problems with raid threatmeter Omen. Omen values were either invalid or were just not there (aka players did not see themself or several other players).
When all of us temporarily removed Recount, things started to work normal again.
I love this addon but I'd love to see a feature to disable sync. It's a pita when it auto syncs when you're trying to find out important info Thanks for your hard work on this.
To those having issues or getting errors regarding Threat-1.0, I believe you just need to make sure all your mods that use Threat-1.0 (Omen, Pitbull, Recount, etc) are in sync.
As in, search your addons folder for Threat-1.0.lua, and make sure all occurences have the *exact* same timestamp. Any versions that don't match are likely to be the cause of your errors. I always make sure, when I update, that all Threat-1.0 based mods are in sync, and have never gotten any the the Threat related errors described here.
To those having issues or getting errors regarding Threat-1.0, I believe you just need to make sure all your mods that use Threat-1.0 (Omen, Pitbull, Recount, etc) are in sync.
As in, search your addons folder for Threat-1.0.lua, and make sure all occurences have the *exact* same timestamp. Any versions that don't match are likely to be the cause of your errors. I always make sure, when I update, that all Threat-1.0 based mods are in sync, and have never gotten any the the Threat related errors described here.
I'm having a most peculiar bug with recount (always updated to latest version) where one of our shadowpriests will always get his healing done added as damage. It even keeps adding damage out of combat, its very annoying and completely skews the table. Our other shadowpriests do not cause this to happen, I dont even think the shadowpriest in question has Recount installed. Its very odd.
And for the people that want to change the look of Recount, there is a skin for Recount in Skinner now.
This can actually cause more problems. If you blindly put a version of Threat-1.0 (standalone) in there, it may not be compatible with each of the other addons, as they may have not been built or tested against it.
A more foolproof approach is to download each mod complete, that uses Threat-1.0, and verify they each uses the same verison. Then you know they were built and tested against that version, and it's the same version for each parent.
This can actually cause more problems. If you blindly put a version of Threat-1.0 (standalone) in there, it may not be compatible with each of the other addons, as they may have not been built or tested against it.
A more foolproof approach is to download each mod complete, that uses Threat-1.0, and verify they each uses the same verison. Then you know they were built and tested against that version, and it's the same version for each parent.
Or just update all of your Ace addons at the same time including standalone libraries.
This can actually cause more problems. If you blindly put a version of Threat-1.0 (standalone) in there, it may not be compatible with each of the other addons, as they may have not been built or tested against it.
A more foolproof approach is to download each mod complete, that uses Threat-1.0, and verify they each uses the same verison. Then you know they were built and tested against that version, and it's the same version for each parent.
You are wrong. With mutiply instance of some lib, only one will be loaded and different versions will cause problems 99% of time. What exactly you will achieve by cheking build numbers? Omen and other addons are simply display data from threat lib. Its not possible for them to be uncompatible, unless Antiarc will make some huge change in how Threatlib works. Best way is to use wowaceupdater and download all mods without externals and use standalone libs.
The font replacement addon ClearFont2's default replacement font shifts the details page vertical location by a bit. That is, the crit %, hit%, etc, values. This is the only place I've seen an issue with text placement.
Not sure if its possible to do some sort of relative layout for said values, but briefly installing it would illustrate the issue.
Ok so another issue regarding sync. I'm in a french guild, so people are using recount with frFR locale, and they sync french data, which means I have in my dps "Fireball" and "Boule de Feu" seperately. And still incoming data when ooc ;x
I'll ask again seeing as I got no answer to my previous question.
Recount is using obscene amounts of memory(up to 10-30 MiB) after having a lot of information, say in a raid or in Alterac Valley - Is this normal? I'm thinking of replacing the addon because of this, because it's the addon that uses the most memory, nearly 50%.
I'll ask again seeing as I got no answer to my previous question.
Recount is using obscene amounts of memory(up to 10-30 MiB) after having a lot of information, say in a raid or in Alterac Valley - Is this normal? I'm thinking of replacing the addon because of this, because it's the addon that uses the most memory, nearly 50%.
Clear the data.
or
Set it to collect less data (in the options, reduce the 'time based' data).
No other mod keeps logs of the damage done and timestamps them. That is why it can use a lot of memory. There is absolutely no way to use less memory when you are collecting and recording that data.
Lastly, 30MB? So what. My machine has 2GB or RAM. Unless you are running with 512MB or ram or less, memory shouldn't be your primary concern.
07/22/07, 5:51 PM
Similar Threads
