Authors CurseForge

Quote from Shadoweric

Agree with this, though I picked last night because we didn't wipe and there's no trash in ToC (the Ulduar part for the weekly raid quest involved vehicle trash and I'm not 100% sure Recount works well with that or even sees the data anyway).

Regarding what's suggested above, that's kinda why I brought up the DeathTrack plugin. Should it have its own SV? Also, since I was never clear on it, doesn't Recount track some sort of death info without the plugin anyway? I'm not even sure of the differences.

Recount does track deaths and also allows you to see the last 10-15 seconds or so of what happened to a person before they died without any plugins.

To explain, RecountDeathTrack gives you an additional window that shows all deaths that are recorded in chronological order.

This is useful if people want to see who died first in raid. The default death information is only per character and it's hard to quickly find out who died when.

RecountDeathTrack does not store any sizeable amount of extra information. It mostly keeps an extra list of events from data that is already stored.

Death information will indeed be recorded and is viewable without it.

Finally had time to look at this in more detail. Very likely RecountDeathTrack is the main issue here. I'll be working on a fix, but I do recommend turning it off until I can work out a fix if you have persistent memory issues.

If you still have issues afterwards let me know.

Committed a new RecountDeathTrack version that no longer stores information in SV. Note that this does NOT affect standard death data as stored by Recount proper. It means that the extra death track window will for now not show a persistent view through reloadui's, DCs and relogs, but at the same time the accumulation of SV file size should be drastically reduced for any combat situations where recorded deaths occur frequently.

I've been tracking a possible recount issue. It would appear that VT (shadow priest) dps isn't being recorded. I see misses, but no hits, and no dps even though I know VT is up.

I went through the change history and searched on this issue and found no information suggesting this is an issue / known issue. Before I pull my hair out, I figured I would see if this sounded familiar here.

If needed I can do some more testing tonight and post details - if so let me know what things would be useful for debug.

Quote from Elsia

Committed a new RecountDeathTrack version that no longer stores information in SV. Note that this does NOT affect standard death data as stored by Recount proper. It means that the extra death track window will for now not show a persistent view through reloadui's, DCs and relogs, but at the same time the accumulation of SV file size should be drastically reduced for any combat situations where recorded deaths occur frequently.

Interesting. Thanks for looking into that plugin after all. I'll be sure to let you know, though it could be a few days.

@EosPhotog: Just tested VT again, works fine.

Quick question, does anyone how I can change the default color for a player whom's class is unknown?

If you stand by the training dummies with recount open you'll know what I'm talking about.

Hello! Could anyone please tell me if there is a way to not show the realm name of characters, through lua or in-game config?

Quote from Elsia

@EosPhotog: Just tested VT again, works fine.

Hmmm - thanks for the quick sanity check. I am going to take another look.

Quote from Bluebell

Hello! Could anyone please tell me if there is a way to not show the realm name of characters, through lua or in-game config?

I'd be interested in that too.

There is no good way to do this currently. The realm appendix is currently needed to disambiguate between combatants with the same name but different realms.

Re: The memory thing.

Ok, so last time was before the changes to RecountDeathTrack. It was a log of 7 boss kills, with few deaths, zero wipes. Ended up at 35 MB with the results posted previously. WoW crashed on /reloadui, then it couldn't load the SV next time WoW started.

This time, using RecountDeathTrack r31. Made sure to reset the data before raid of course. Only 3 boss kills, but a bajillion more deaths and wipes (Icecrown Citadel), so several attempts on bosses. 10 attempts recorded by Recount altogether. Actually, only 2 bosses since apparently the Gunship Battle isn't recorded by Recount. Some people might ask you for it, though I personally don't think it matters for such a gimmicky fight. Anyway, log file: 20 MB.

So clearly, a lot of data has disappeared with the changes to RecountDeathTrack, since not only do we have more bosses attempts this time around, but we also have a ton more deaths.

So I did a /reloadui again... WoW crashed. Same error as previously again (the memory thing. Exact message is in my previous posts). Now I had WoW running for several hours by then, had switched toons, done things other than raiding... etc. I need to restart WoW, maybe even reboot before a raid next time, because I really think they have memory management issues.

But... and here's the good part: relogging after the crash, this time, the SV loaded properly. All I did was reboot technically: raid was last night, I didn't log back in until tonight after the crash. So I have last night's data still available.

So thanks Elsia, looks like you solved your side of the issue. At least so far. Now it seems like Blizzard needs to look at their code.

Hope that helps.

Thanks for the report. It's very much in line with what I expected to happen.

On the crash, unfortunately if WoW crashes on 20MB addon data there is really very little I can do. I'd call this a blizz issue, especially if the behavior is not consistent (i.e. it's fine to load it if wow is fresh) as you describe.

Totally unrelated, but I just got this:

2x Recount-1115\GUI_Main.lua:1253: attempt to index field 'TimeData' (a nil value)
Recount-1115\GUI_Main.lua:1271: in function `AddAllToGraph'
Recount-1115\GUI_Graph.lua:1249: in function <Recount\GUI_Graph.lua:1249>

Locals:
self = <table> {
 SetMainWindowModeByLabel = <function> @ Recount\Recount_Modes.lua:592:
 ResetData = <function> @ Recount\Recount.lua:851:
 ResetPositionAllWindows = <function> @ Recount\WindowOrder.lua:111:
 modules = <table> {}
 FormatLongNums = <function> @ Recount\GUI_Main.lua:55:
 srcRetention = true
 SpellBuildingDamage = <function> @ Recount\Tracker.lua:234:
 FlagSync = <function> @ Recount\LazySync.lua:492:
 UnregisterTracking = <function> @ Recount\Tracker.lua:1803:
 CheckPartyCombatWithPets = <function> @ Recount\roster.lua:14:
 InitFightData = <function> @ Recount\Recount.lua:986:
 RequestVersion = <function> @ Recount\LazySync.lua:539:
 UpdateZoneGroupFilter = <function> @ Recount\zonefilters.lua:69:
 FightDropDownOpen = <function> @ Recount\GUI_Main.lua:988:
 ScheduleTimer = <function> @ Acheron\Libs\AceTimer-3.0\AceTimer-3.0.lua:270:
 SetStrataAndClamp = <function> @ Recount\WindowOrder.lua:145:
 ShortNumber = <function> @ Recount\GUI_Main.lua:27:
 FreeTableRecurse = <function> @ Recount\Recount.lua:2063:
 FreeComm = <function> @ Recount\LazySync.lua:488:
 db = <table> {}
 SetZoneGroupFilter = <function> @ Recount\zonefilters.lua:48:
 UnregisterAllComm = <function> @ TomTom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:202:
 SetEnabledState = <function> @ Acheron\Libs\AceAddon-3.0\AceAddon-3.0.lua:430:
 ReportVersions = <function> @ Recount\Recount.lua:825:
 ResetFightData = <function> @ Recount\Recount.lua:925:
 SpellMissed = <function> @ Recount\Tracker.lua:322:
 FightingWho = "Ley-Guardian Eregos"
 SetDeathLogDetails = <function> @ Recount\GUI_Detail.lua:447:
 FindTargetedUnit = <function> @ Recount\roster.lua:91:
 NewModule = <function> @ Acheron\Libs\AceAddon-3.0\AceAddon-3.0.lua:247:
 IsBoss = <function> @ Recount\Tracker.lua:178:
 GetLazySyncAmount = <function> @ Recount\LazySync.lua:560:
 CreateFilterWeights = <function> @ Recount\Recount.lua:1535:
 UpdateSummaryMode = <function> @ Recount\GUI_Detail.lua:1269:
 SpellEnergize = <function> @ Recount\TrackerModules\TrackerModule_PowerGains.lua:58:
 AddGain = <function> @ Recount\TrackerModules\TrackerModule_PowerGains.lua:68:
 Deserialize = <function> @ DataStore\libs\AceSerializer-3.0\AceSerializer-3.0.lua:236:
 AddDispelData = <function> @ Recount\TrackerModules\TrackerModule_Dispels.lua:42:
 CheckFontStringLength = <function> @ Recount\GUI_Graph.lua:734:
 GetPetPrefixUnit = <function> @ Recount\roster.lua:67:
 GetName = <function> @ Acheron\Libs\AceAddon-3.0\AceAddon-3.0.lua:290:
 SetActive = <function> @ Recount\Tracker.lua:650:
 name = "Recount"
 CreateRealtimeWindow = <function> @ Recount\GUI_Realtime.lua:319:
 GetLazySyncTouched = <function> @ Recount\LazySync.lua:567:
 Print = <function> @ AckisRecipeList\libs\AceConsole-3.0\AceConsole-3.0.lua:54:
 SpellCastStartSuccess = <function> @ Recount\Tracker.lua:402:
 SpellAuraDispelFailed = <function> @ Recount\Tracker.lua:1755:
 GuardianOwnerGUIDs = <table> {}
 DeleteGuardianOwnerByGUID = <function> @ Recount\Recount.lua:1252:
 HideRealtimeWindows = <function> defined @Recount\Win
  ---

I clicked on the + button in the graph window for my character. It was after a random 5-man and there was data available.

Issue I saw the other night as a blood DK tank after Oculus it showed my dps the fight on the 3d boss Mage-Lord Urom, as the tank I was registered to have done something like 73% of the damage and 15k dps. A total of 12k DPS for the instance overall and I'd be lucky to pull 1.6k on a good night... So it wasn’t the drakes and the rest of the group showed low under 2k. I thought I took a screen shot but apparently I didn’t. I didn’t pay attention tto the he dps meter until I had logged off that toon for a moment to another for something then back on. So it might be in the logging in /out. Only time I noticed it.

Back to Recount after trying another mod that worked even less well than Recount has been. No further memory allocation error: block too big errors or unexpected data deletion so far with RecountDeathTrack r31 as one of the modules being used. There was that error and an unwanted SV delete after logging on with r30, though.

Will continue to monitor if it happens again.

Quote from Thortok2000

As a Disc Priest, I'd like to see heals + absorbs. I saw the plugin on curse but it doesn't seem to work. Could whoever's supporting that take a look and fix it?

That plugin (RecountHealAndGuessedAbsorbs V1.1) works here without issue. Can access it through both the main Recount frame arrows as well as RecountFu. You also need RecountGuessedAbsorbs active for it to tabulate the data properly.

Hello!

Is there a way to show the highest hit / highest crit?
Maybe with mouseover inforamtion spell on Mob/Boss?

Best Regards

Would there be any reason why Festergut, both on 10 and 25 man, refuses to keep a log. I have Recount setup to only keep Boss segments and every clear (about 7 between 10 man/25 on main/alt) that fight refuses to log. Everyone else in the raid gets a segment for it. Is there a way to fix this?

Thank you in advance.

"Everyone else" probably didn't have "save boss segments only" turned on... Festergut was missing from LibBossIDs-1.0. I've added it, but until the next Recount update you'll have to manually grab the updated lib if you want Festergut to save.