Recount - A Graphical Damage Meter/Raid Analysis Tool - Page 39

Bikiniwax · 04/01/08, 2:49 PM

I wish Recount wasn't using up so much memory. Fresh without data, it takes up 13-15MB now, up from the 4MB it used to take pre-2.4

:\

◊ Cadfael · 04/02/08, 6:37 AM

Originally Posted by Bikiniwax

I wish Recount wasn't using up so much memory. Fresh without data, it takes up 13-15MB now, up from the 4MB it used to take pre-2.4

:\

Are you playing WoW on a system with 1GB Ram or less ? If not it is of no problem at all. Static memory consumption has no influence on your running performance what so ever. What has an influence is growth (both in positive as in negative direction) while playing. Active memory consumption can be a problem/factor. Static memory usage does nothing to your FPS, except if you want to include initial loading time upon login.

nutteh · 04/02/08, 9:40 AM

Myself and the majorty of the raid is getting this

r67648, this a client error? or a program error?

Dralmoo · 04/02/08, 12:42 PM

I had the same thing. Deleted all my Recount.lua files from WTF folder, and it seemed to work fine after that.

Machia · 04/03/08, 6:00 PM

Has anyone noticed that recount no longer shows you death information? I pull up who died and it doesn't even count players.. It basically only shows pet deaths. No clue why. It's a feature I miss the most as I use it to determine how/why a tank/player bit the dust so that we can figure out what exactly went wrong.

ravs · 04/03/08, 6:21 PM

It's because the Blizzard combat log no longer shows deaths, it's being fixed in 2.4.2 (or so I've heard).

The feature I'm missing is the network traffic tab. I found it really useful to troubleshoot raid lag, but it seems to have vanished.

Cryect · 04/03/08, 10:44 PM

Originally Posted by ravs

It's because the Blizzard combat log no longer shows deaths, it's being fixed in 2.4.2 (or so I've heard).

The feature I'm missing is the network traffic tab. I found it really useful to troubleshoot raid lag, but it seems to have vanished.

Vanished because it was for aiding with reducing traffic and was really hacked into Recount.

Yes, deaths should be fixed in 2.4.2 (you will notice your combat log doesn't record deaths either).

• Daboran · 04/04/08, 6:43 AM

Originally Posted by Cryect

Vanished because it was for aiding with reducing traffic and was really hacked into Recount.

Yes, deaths should be fixed in 2.4.2 (you will notice your combat log doesn't record deaths either).

Just throwing this out there - there's quite a few "gains" not recorded in the combat log either, Nightmare Seed for one.

Allev · 04/04/08, 12:16 PM

I know the durability loss line is in the combat log, though, so there's at least evidence that you died.

songster · 04/05/08, 2:40 PM

Is there any way to turn of synchronisation for this mod? It's one of the worst offenders on AddonspamFu, and we're having people disconnect from addon spam.

Zaazel · 04/05/08, 2:58 PM

Easy enough. "/recount sync" will turn off syncing.

Cryect · 04/05/08, 3:40 PM

Originally Posted by songster

Is there any way to turn of synchronisation for this mod? It's one of the worst offenders on AddonspamFu, and we're having people disconnect from addon spam.

When are those players disconnecting?

The only time Recount syncs now is out of combat so if its during combat its something else.

NinJOu · 04/08/08, 1:54 PM

Last week, we had all Recount users disconnected from the game while we were on Azgalor @ 20%.

In fact, one player started flooding the addon channel like hell. He didn't do nothing particular really.

Since then, no more problem (maybe a new version ?).

Papajan · 04/09/08, 1:09 PM

Originally Posted by Allev

I know the durability loss line is in the combat log, though, so there's at least evidence that you died.

yeah, that's there and also the PLAYER_DIED Lua event works correctly, but you don't get much of anything for other people in the raid. The only option I've found until 2.4.2 is to compare the damage amount against UnitHealth(unit) and see if it's a fatal blow. The only problem with that is that the UnitHealth updates slower than the events come in, so you don't actually see an HP update until after two or more fast hits sometimes.

Auralin · 04/13/08, 3:05 AM

I wasn't quite sure where to post this, but I keep getting a LUA error from the newest version of recount.

Interface\AddOns\Recount\healbuffs.lua:169: table index is nil
Count: 3

Call Stack:
(tail call): ?
Interface\AddOns\Recount\healbuffs.lua:169: in function `POM_Gained'
Interface\AddOns\Recount\Tracker.lua:420: in function `parsefunc'
Interface\AddOns\Recount\Tracker.lua:556: in function `?'
...rid\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...rid\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
[string "safecall Dispatcher[13]"]:4: in function <[string "safecall Dispatcher[13]"]:4>
[C]: ?
[string "safecall Dispatcher[13]"]:13: in function `?'
...rid\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
...rface\AddOns\Omen\Libs\AceEvent-3.0\AceEvent-3.0.lua:70: in function <...rface\AddOns\Omen\Libs\AceEvent-3.0\AceEvent-3.0.lua:69>

Hope this helps fix any remaining bugs, I love the addon.

Pagarth · 04/20/08, 6:33 AM

Is there a way to adjust it so that the bar that displays what frame youre looking at as well as the buttons is slightly above the damage bars? Also, is there a way to have it so Recount only shows up in certain areas like only in dungeons and raid zones as opposed to me clicking the button to make it display?

Farei · 04/20/08, 4:34 PM

The latest version of recount (r70594) keeps giving me the following error when combat starts:

Date: 2008-04-20 19:18:20
ID: 52
Error occured in: Global
Count: 8
Message: ..\AddOns\Recount\LazySync.lua line 562:
   attempt to call method 'DPrint' (a nil value)
Debug:
   (tail call): ?
   Recount\LazySync.lua:562: AddLazySyncAmount()
   Recount\LazySync.lua:557: AddOwnerPetLazySyncAmount()
   Recount\Tracker.lua:1240: AddDamageData()
   Recount\Tracker.lua:308: parsefunc()
   Recount\Tracker.lua:556: ?()
   ...men\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146:
      ...men\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
   [string "safecall Dispatcher[20]"]:4:
      [string "safecall Dispatcher[20]"]:4
   [C]: ?
   [string "safecall Dispatcher[20]"]:13: ?()
   ...men\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire()
   ...rface\AddOns\Omen\Libs\AceEvent-3.0\AceEvent-3.0.lua:70:
      ...rface\AddOns\Omen\Libs\AceEvent-3.0\AceEvent-3.0.lua:69

Edit: Fixed my other problem :P

Pixen · 04/22/08, 2:09 PM

The latest version of Recount doesn't seem to be recording personal dps.

Malleus · 05/08/08, 8:15 AM

Recount is currently bugging out frequently. For reasons unknown, it sometimes doubles or triples the session stats for random characters. I can only guess that it's sending itself the complete data again, as the averages remain unchanged.

Pelf · 05/08/08, 9:35 AM

Originally Posted by Malleus

Recount is currently bugging out frequently. For reasons unknown, it sometimes doubles or triples the session stats for random characters. I can only guess that it's sending itself the complete data again, as the averages remain unchanged.

I've seen this behavior myself. Sometimes after a fight (now that it only synchs out of combat) one person's bar will double or triple in length and pop up to the top. I haven't tried disabling synching as it's generally a useful feature.

• Ullas · 05/08/08, 12:11 PM

Just out of curiosity,

Has anyone jury-rigged recount to record player deaths? Seeing those combat log excerpts was the most useful part of the mod, especially when trying to figure out the cause of wipes. Is there another mod that I could use in the mean time that will show specific sources of damage and healing (read: not grim reaper)?

koaschten · 05/08/08, 7:27 PM

Unless Elsia who is currently maintaining Recount wrote a workaround to the missing combatlog death event (which will supposedly be fixed in 2.4.2) your best bet is to use another mod like Expiration, which i can assure you is working currently.

Paga · 05/09/08, 12:00 AM

I thought the current maintainer said that it is coming in 2.4.2?

Pelf · 05/09/08, 12:38 PM

Originally Posted by Paga

I thought the current maintainer said that it is coming in 2.4.2?

Iriel posted that a UNIT_DEATH fix is coming in 2.4.2. It's in the 2.4 Upcoming Changes - Concise List thread in the UI & Macros forum if you want to check it out.

Celandro · 05/14/08, 7:21 PM

It looks like the death meter is still not sorted by order of death and its very difficult to get a timeline of who died when and why. Could something be done about that?

A graph that showed number of dpsers + number of healers (lets just say anyone with more hps>dps is a healer) stacked on top of each other would be nice. If it was combined with a list of death times that we could mouse over to highlight the column corresponding to each death, and click on to see the logs, analyzing wipes would be very useful. A lot of fights have 1 or 2 people die and get rezzed no problem and then suddenly a chain of deaths occurs in a very short period of time.

I'm certain that recount stores all the data needed to display this type of graph, so I don't think it would be too difficult to get most of the functionality in.