Hi guys, have I missed something or isn't it possible to change the texture of the title in Recount?
If I haven't, would it be possible to add an option to change the texture of the title, or can anyone give me some pointers on how to hack the new texture into the code?
Could that be "otravi-semi-full-border.tga" in the texture folder maybe?
Edit2: I removed the file and the textured header from all Recount windows went missing so it is that file. I changed it slightly first but I guess I failed saving it correct.
I'm running a high end machine, so nothing that even involves wow should be locking my computer up at all. I have also been having another problem when I exit totally from the game, sometimes my system will blue screen. This has only started happening since I installed vista 64 bit. But it also only seems to happen when I have recount turned on. I've had recount off for about a week and I've had zero problems with frame rates and no blue screens on exiting.
Also, when I tab out of wow to end the task, I don't have the frame rate problems there, like I do when the game is up. So whatever the problem is only happens inside the game itself. It doesn't lag up the rest of my processes.
Any clues what could be going on?
Are you running a lot of addons?
Just yesterday on Archimonde I had my UI crash totally - the LUA error that was popping up had the error message "memory allocation block too big". I've had this happen before, and while it's not directly related to Recount (as far as I can tell), I believe it happens when addon memory hits around 160ish MB. This is by no means a fixed limit (I've seen stuff use up to 180 while still running).
Anyway, whenever this LUA error happens, things can go from "bad" (several of my UI elements died; fortunately I didn't wipe us!) to "WoW crashes completely a second after".
Now, Recount with timelines enabled on a longish raid can still consume pretty ridiculous amounts of memory (mine had been hovering at around 25mb), so could this be what's happening to you?
I think I found a bug which caused some of the late reset popups.
I just was invited in a group, no reset popup came because my recount was empty. But then the other char (the group leader if that matters) ported from Shattrath to SW. Just as he arrived in SW the reset popup appeared.
My settings:
Instance deleting: enter checked, new checked, popup checked
Group deleting: new checked, popup checked
Raid deleting: not checked
I have a problem recently with recount and I'm not sure if I'm alone in this situation. I am a resto druid, running recount for healing meters on M'uru. With my gear and my x4 LB stacks I'm averaging 2400 healthpersecond, and slamming the charts. The next healers arn't usually half of what I'm doing for healing, using recount. Yet when I ask other people, my numbers are far skewed. Sometimes I'm in 4th position for healing. The WWS shows me largley in 3rd place and could no way reflect the attempts that I was seeing.
I've used recount for a very long time but havn't had such discrepancies until recently. I am running the latest version as well. I've done nights not using InstantHealth and nights using it and still coming up with vastly different meters.
Anyone have any variables that might account for such different figures? Range? Other Mods? Anything would help.
@garfi: Time data collection is immensely data intensive. I recommend not having it on for all combatant types, ideally only for self unless there is some really good reason to keep it on for someone else.
There is apparently currently a crash problem with memory accumulation, that's discussed in another thread on this forum. It's not Recount specific but likely has to do with the internal workings of Lua within WoW.
In any case I do not recommend going heavy on time data collection.
@cremor: Thanks, I got a possible idea now what's going on, though I'm still not sure. Actually it likely has nothing to do with zoning but with some invite not having gotten accepted (which apparently fires PARTY_MEMBERS_CHANGED, but the wiki seems outdated on it). I'll look into working around that issue.
@atraiyu:
I have heard other reports of healer data discrepancies. I have a hard time reproducing this because I don't often get the chance to compare recount healer data. In any case, here is what I think is happening. Lifebloom, Earth Shield and Prayer of Mending currently use a heuristics to try to match the data to their healer. Unfortunately the method is not 100% because it relies on subsequent data from the combat log that cannot be guaranteed and can differ between combatants. This explains why you see your healing data higher than in WWS which doesn't even try to attribute these healing types. Overall Recount in my experience matches the vast majority of these healing types correctly, certainly for self which I can test the easiest. Now Recount's current sync code relies on a distance check fo trigger a sync, if a mismatch in heuristics happens this will currently not lead to a sync hence such discrepancies are allowed to build up. But this is my theory and I don't have certain confirmation that this causes the differences in meters for healing data, though it's likely.
You can compare healing details with others to check which healing type is different, that should give you an idea if indeed the lifebloom attribution is causing the differences or something else. Or maybe you are actually not seeing the correct attributions of other's LB/ES/PoM to the degree that they actually caused it.
I'll check and see what others say. I know that 97% of my healing is done through the ticks of LB itself and no the final bloom which i realize wouldn't show as my healing, and currently I'm the only resto druid in the raid so the only source of this type of healing.
If you know anything about the M'uru fight, from where one person stands there is usually half of the raid that is always going to be over 40 yards away and out of healing range. This is usually where the person stands who gathers info for our combat logs. I was wondering if this range indeed had some problems with heals.
If i remember correctly the old recount had a increased 200 yard combat log range feature and I was told that recent wow patches made this irrelevant.
Correct; post-patch 2.4, the combat log now shows you "everything that happens in visible range". My guild is also working on M'uru, and the distances involved are not an issue. However, I think Elsia's explanation is generally correct. If any healing priests or shamans in your raid are running Recount, compare their numbers for their own healing with your numbers for their healing. There will likely be a discrepancy, and the biggest difference will be in the amount of healing attributed to Earth Shields and Prayers of Mending. If you ever have a second healing druid in your raid, I suspect he'd see his own healing higher than you'd see his healing, and he'd see your healing as lower than you see. Unfortunately the fancy new 2.4 combat log system still does not address these issues, so addons can only guess, and due to latency and bugs in the combat log (if you look at your raw combat log you'll sometimes see heal successes, without actually healing anyone, or events appearing in the wrong order) addons are best at guessing your own ES/LB/PoM, but not always so great at guessing other peoples'. Syncing can help, but only if eveyrone using these
By the way, I wouldn't worry about WWS too much, if you can avoid it. Any time I've ever compared a WWS report of any given fight to the in-game metrics of the same fight as reported by Recount (or Assessment pre-2.4), I've found WWS to be complete and utter garbage, underreporting the damage and healing of everyone in the raid by wildly varying amounts. I'm not sure why people swear by it and pay money for it. ???
This doesnt really have alot to do with this thread (sorry!) but have you heard anything from cryect in a while Elsia? I'd love some update on Recount 2, but he hasnt been active in ages.
Would it be possible to get "self damage" from "SW:Death" and "Life Tap" included in "friendly fire" damage totals? Does this make sense? Some examples of how they are recorded in the combat log follows:
@Nalle: Check the Recount2 thread. Cryect hasn't been active for a while and I don't really know anything above that.
@Pachel: SW:Death should already be recorded given that it's a standard dot line. I'll check if it works as intended or not and will look to fix it. SPELL_ENERGIZE is another matter. Unfortunately, the combat log does not contain damage entries for drain/leech/energize spells like life tap, only the amount of energy gain. To understand why this is a problem: A lock has talents to change the ratio of energy gained vs life tapped (improved life tap). But the combat log does not display this information hence it's not possible for any locks but self to do this in principle (in lieu of hefty talent parsing and syncing) and even for self it involves talent parsing. Hence I have decided against supporting life tap, as the lack of a damage entry is a combat log deficiency, also because self-damage isn't exactly a frequently important stat hence the gain doesn't really warrant the effort.
The reason there is no damage entry in the combat log for Life Tap is that it doesn't actually do any damage. The health lost is simply the cost of the spell. It's the same as not having a "lost mana" entry for every normal spell that you cast.
Earth shield is a self heal per game mechanics, but people still want it to be attributed to the cast originator. Same with life tap, it's not at all unnatural to consider it self-damage and attribute it to friendly fire even if the game mechanics has a different explanation to the effect.
If there was a sensible way, Recount would display life tap as friendly fire damage, there just isn't a good way to get that done.
What remains is the a target loses health ("takes damage") that one might want to see. If in fact "mana loss" would be visible, one could do very interesting mana efficiency and longevity stats in Recount.
I've looked but I can't find an option to not save data between WoW sessions (e.g. don't save combat data into the savedvariables file)????
I can't think of a case where I'd want to keep this data personally - and the reading/writing of savedvariables is the 'big slowdown' of switching chars (and the reason I don't use mods like Armory or Auctioneer).
Is there an option to clear data at logoff - if not, could there be?? :)
I've looked but I can't find an option to not save data between WoW sessions (e.g. don't save combat data into the savedvariables file)????
I can't think of a case where I'd want to keep this data personally - and the reading/writing of savedvariables is the 'big slowdown' of switching chars (and the reason I don't use mods like Armory or Auctioneer).
Is there an option to clear data at logoff - if not, could there be?? :)
There is allready an option to delete all recorded data before logout, you should find it in the main window.
I've been having a problem with recount lately, probably since 2.4.
The death log is simply wrong. Almost all the time.
Sometimes I'll click on a name, and the log is for another player.
Sometimes I'll click on a name of someone I know for a fact died to Burns while standing behind Brutallus, but the death log will claim they took a 10k Meteor Slash. I assume its getting names mixed up somehow.
I've been having a problem with recount lately, probably since 2.4.
The death log is simply wrong. Almost all the time.
Sometimes I'll click on a name, and the log is for another player.
Sometimes I'll click on a name of someone I know for a fact died to Burns while standing behind Brutallus, but the death log will claim they took a 10k Meteor Slash. I assume its getting names mixed up somehow.
delete all instances of recount, dependencies, and reinstall it all. Recount has been working like a champ, displaying deaths in order, correctly, with pertinent information.
Only thing I'm missing is the ability to do graphs, that's been broken for a while.
There is allready an option to delete all recorded data before logout, you should find it in the main window.
I can see options to clear on new group, new instance and new raid - but not on logout (and certainly some of my toons have large recount.lua files in their savedvariables directories)...
I'm running the latest version available to WAU - 75926 - is there a later version I'm missing perhaps?
If I haven't, would it be possible to add an option to change the texture of the title, or can anyone give me some pointers on how to hack the new texture into the code?
Thank you.
Edit2: I removed the file and the textured header from all Recount windows went missing so it is that file. I changed it slightly first but I guess I failed saving it correct.
Are you running a lot of addons?
Just yesterday on Archimonde I had my UI crash totally - the LUA error that was popping up had the error message "memory allocation block too big". I've had this happen before, and while it's not directly related to Recount (as far as I can tell), I believe it happens when addon memory hits around 160ish MB. This is by no means a fixed limit (I've seen stuff use up to 180 while still running).
Anyway, whenever this LUA error happens, things can go from "bad" (several of my UI elements died; fortunately I didn't wipe us!) to "WoW crashes completely a second after".
Now, Recount with timelines enabled on a longish raid can still consume pretty ridiculous amounts of memory (mine had been hovering at around 25mb), so could this be what's happening to you?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI just was invited in a group, no reset popup came because my recount was empty. But then the other char (the group leader if that matters) ported from Shattrath to SW. Just as he arrived in SW the reset popup appeared.
My settings:
Instance deleting: enter checked, new checked, popup checked
Group deleting: new checked, popup checked
Raid deleting: not checked
I've used recount for a very long time but havn't had such discrepancies until recently. I am running the latest version as well. I've done nights not using InstantHealth and nights using it and still coming up with vastly different meters.
Anyone have any variables that might account for such different figures? Range? Other Mods? Anything would help.
There is apparently currently a crash problem with memory accumulation, that's discussed in another thread on this forum. It's not Recount specific but likely has to do with the internal workings of Lua within WoW.
In any case I do not recommend going heavy on time data collection.
@cremor: Thanks, I got a possible idea now what's going on, though I'm still not sure. Actually it likely has nothing to do with zoning but with some invite not having gotten accepted (which apparently fires PARTY_MEMBERS_CHANGED, but the wiki seems outdated on it). I'll look into working around that issue.
@atraiyu:
I have heard other reports of healer data discrepancies. I have a hard time reproducing this because I don't often get the chance to compare recount healer data. In any case, here is what I think is happening. Lifebloom, Earth Shield and Prayer of Mending currently use a heuristics to try to match the data to their healer. Unfortunately the method is not 100% because it relies on subsequent data from the combat log that cannot be guaranteed and can differ between combatants. This explains why you see your healing data higher than in WWS which doesn't even try to attribute these healing types. Overall Recount in my experience matches the vast majority of these healing types correctly, certainly for self which I can test the easiest. Now Recount's current sync code relies on a distance check fo trigger a sync, if a mismatch in heuristics happens this will currently not lead to a sync hence such discrepancies are allowed to build up. But this is my theory and I don't have certain confirmation that this causes the differences in meters for healing data, though it's likely.
You can compare healing details with others to check which healing type is different, that should give you an idea if indeed the lifebloom attribution is causing the differences or something else. Or maybe you are actually not seeing the correct attributions of other's LB/ES/PoM to the degree that they actually caused it.
If you know anything about the M'uru fight, from where one person stands there is usually half of the raid that is always going to be over 40 yards away and out of healing range. This is usually where the person stands who gathers info for our combat logs. I was wondering if this range indeed had some problems with heals.
If i remember correctly the old recount had a increased 200 yard combat log range feature and I was told that recent wow patches made this irrelevant.
By the way, I wouldn't worry about WWS too much, if you can avoid it. Any time I've ever compared a WWS report of any given fight to the in-game metrics of the same fight as reported by Recount (or Assessment pre-2.4), I've found WWS to be complete and utter garbage, underreporting the damage and healing of everyone in the raid by wildly varying amounts. I'm not sure why people swear by it and pay money for it. ???
SPELL_PERIODIC_DAMAGE,0x0000000000000000,nil,0x80000000,0x0000000000467BD9,"Uberpriest",0x514,32409,"Shadow Word: Death",0x20,2104,32,0,0,0,nil,nil,nil
SPELL_ENERGIZE,0x0000000001F903D6,"Uberlock",0x514,0x0000000001F903D6,"Uberlock",0x514,31818,"Life Tap",0x20,1963,0
Thanks.
-Pach
@Pachel: SW:Death should already be recorded given that it's a standard dot line. I'll check if it works as intended or not and will look to fix it. SPELL_ENERGIZE is another matter. Unfortunately, the combat log does not contain damage entries for drain/leech/energize spells like life tap, only the amount of energy gain. To understand why this is a problem: A lock has talents to change the ratio of energy gained vs life tapped (improved life tap). But the combat log does not display this information hence it's not possible for any locks but self to do this in principle (in lieu of hefty talent parsing and syncing) and even for self it involves talent parsing. Hence I have decided against supporting life tap, as the lack of a damage entry is a combat log deficiency, also because self-damage isn't exactly a frequently important stat hence the gain doesn't really warrant the effort.
If there was a sensible way, Recount would display life tap as friendly fire damage, there just isn't a good way to get that done.
What remains is the a target loses health ("takes damage") that one might want to see. If in fact "mana loss" would be visible, one could do very interesting mana efficiency and longevity stats in Recount.
I can't think of a case where I'd want to keep this data personally - and the reading/writing of savedvariables is the 'big slowdown' of switching chars (and the reason I don't use mods like Armory or Auctioneer).
Is there an option to clear data at logoff - if not, could there be?? :)
There is allready an option to delete all recorded data before logout, you should find it in the main window.
The death log is simply wrong. Almost all the time.
Sometimes I'll click on a name, and the log is for another player.
Sometimes I'll click on a name of someone I know for a fact died to Burns while standing behind Brutallus, but the death log will claim they took a 10k Meteor Slash. I assume its getting names mixed up somehow.
delete all instances of recount, dependencies, and reinstall it all. Recount has been working like a champ, displaying deaths in order, correctly, with pertinent information.
Only thing I'm missing is the ability to do graphs, that's been broken for a while.
I can see options to clear on new group, new instance and new raid - but not on logout (and certainly some of my toons have large recount.lua files in their savedvariables directories)...
I'm running the latest version available to WAU - 75926 - is there a later version I'm missing perhaps?