Whispering myself worked fine tonight. I did get some other errors at one point when I wasn't even trying to interact with Acheron. Couldn't figure out what triggered them, and I lost them due to forgetfulness; if I see them again I'll try to post.
Love the addon. Any chance you could add an option to whisper reports to a name you type in since you can't target people far from you and not in group/raid?
I did "extensive" CPU testing on Acheron with standalone libs here. Extensive meaning killing helpless baby spiders on my level 11 test character, solo. As well as letting them eat me (er, so to speak).
At no time did Acheron ever use excessive CPU time; it used none/virtually none at all times, including when dying. And neither did the libs it used, above the steady no-mod CPU state they normally did. That person's lag issues most likely due to another mod.
I did "extensive" CPU testing on Acheron with standalone libs here. Extensive meaning killing helpless baby spiders on my level 11 test character, solo. As well as letting them eat me (er, so to speak).
At no time did Acheron ever use excessive CPU time; it used none/virtually none at all times, including when dying. And neither did the libs it used, above the steady no-mod CPU state they normally did. That person's lag issues most likely due to another mod.
To test these kinds of addons you need to do it in a raid. Anyway great addon, just what i needed after GrimReaper started acting funny with my tooltip mod.
Love the addon. Any chance you could add an option to whisper reports to a name you type in since you can't target people far from you and not in group/raid?
Yep, I'll add that.
Quote from Neo »
Is it possible to add in a menu to show you who died in chronological order?
To test these kinds of addons you need to do it in a raid.
Eh, no.
For 100% behavior-accurate conclusions, sure. For proposed conclusion drawing based on long experience, its not really necessary. The poster was saying this mod was doing something without providing the hard data (numbers, etc.) and/or not running it without other mods being present. My hard data here for this-mod-alone in-combat usage & self-deaths shows 0 CPU usage. Also shows 0 CPU usage in an instance party in-combat.
Its difficult to impossible to test CPU usage in a raid unless you have 9 willing volunteeers who will put up with you lagging and holding things up when CPU profiling is turned on and you are staring at the OptionHouse/FuBar_Usage/Profiler/etc. tables. Raid lag can be caused by many different things. Its a reasonable assumption to make that mods which use excessive CPU time when OOC & idle or in combat solo or in a party will amplify and/or continue this behavior when in a raid.
Based on that, the probability of Acheron eating tons of CPU during trash mobs is slim and its much more likely some other mod is causing it for that person. Again, not a 100% behavior-accurate conclusion, but good enough ;).
I used it in Mount Hyjal yesterday - and yes we died a lot, so plenty of input to process ^_^. Worked fine, mighty fine actually.
Might ofc be that since now that I have Acheron I disabled Recount, I actually notice the removed CPU-usage from Recount. In either case, very awesome. :)
[2008/07/28 19:29:01-5431-x1]: Acheron-1.0\Display.lua:376: attempt to index field '?' (a nil value)
Acheron-1.0\Display.lua:353: in function `Report'
Acheron-1.0\Display.lua:295: in function <Interface\AddOns\Acheron\Display.lua:295>
One thing I'd like to request would be some way to see a list of all deaths in chronological order, with the ability to click on one to be taken to that death report. Targetting someone and right-clicking them is a bit cumbersome, especially for viewing multiple people's deaths, especially if you want to switch back and forth between them. :P
i updated the language file, because i didnt save it in utf8, so the special chars were ingame 'very special' ^^
if you use the updated file, everything works fine
Edit: Oh, also I think I was in combat when I was trying to report if that makes a difference.
At no time did Acheron ever use excessive CPU time; it used none/virtually none at all times, including when dying. And neither did the libs it used, above the steady no-mod CPU state they normally did. That person's lag issues most likely due to another mod.
To test these kinds of addons you need to do it in a raid. Anyway great addon, just what i needed after GrimReaper started acting funny with my tooltip mod.
Yep, I'll add that.
http://www.wowace.com/forums/index.php?topic=14372.msg232403#msg232403
Eh, no.
For 100% behavior-accurate conclusions, sure. For proposed conclusion drawing based on long experience, its not really necessary. The poster was saying this mod was doing something without providing the hard data (numbers, etc.) and/or not running it without other mods being present. My hard data here for this-mod-alone in-combat usage & self-deaths shows 0 CPU usage. Also shows 0 CPU usage in an instance party in-combat.
Its difficult to impossible to test CPU usage in a raid unless you have 9 willing volunteeers who will put up with you lagging and holding things up when CPU profiling is turned on and you are staring at the OptionHouse/FuBar_Usage/Profiler/etc. tables. Raid lag can be caused by many different things. Its a reasonable assumption to make that mods which use excessive CPU time when OOC & idle or in combat solo or in a party will amplify and/or continue this behavior when in a raid.
Based on that, the probability of Acheron eating tons of CPU during trash mobs is slim and its much more likely some other mod is causing it for that person. Again, not a 100% behavior-accurate conclusion, but good enough ;).
Might ofc be that since now that I have Acheron I disabled Recount, I actually notice the removed CPU-usage from Recount. In either case, very awesome. :)
Acheron-1.0\Display.lua:353: in function `Report'
Acheron-1.0\Display.lua:295: in function <Interface\AddOns\Acheron\Display.lua:295>
---
Trying to report in guild.
edit: save localization in utf8, so special charakters actually word, doh'!
if you use the updated file, everything works fine
It was r79281.