Authors CurseForge

Message: WTF\Account\OLDCHAP\Nordrassil\Angayelle\SavedVariables\Recount.lua:305548: unexpected symbol near '<eof>'
Time: 10/15/11 10:03:07
Count: 1
Stack:
Locals:

first time i got this message and i don't recall upgrading or something lately, happened only once

detail screens, when you left click on things to get the pie chart, it doesnt come up. any ideas?

How can I turn Recount OFF in battlegrounds or simply get it to ignore them and not track that data, thanks?

Forum report heavy lag on the fight even if addon-free. See for example here:

http://us.battle.net/wow/en/forum/topic/3558816183

I have no first-hand experience, but by the sound of it, it's an issue with the encounter itself.

Elsia, Did you get my PM about paid support for this addon? --

I know that your time is valuable, I'm just wondering if I could "donate" to your coding time, in order to get 1-2 bugs fixed I'm having?

If not, please contact me at - Nomiconn - Sisters of Elune -- I'd be more than happy to go over it? They are really simple bugs I believe. I'll also be your testing slave ;)

I'm not accepting any donations but thanks for the thought.

On the two bugs you report:

1) CC tracking is broken due to a blizzard bug. It will start working again the moment the relevant events reappear in the combat log. This cannot be fixed addon-side.

2) Damage to an absorption mechanism is tracked, as long as the combat log properly reports it as damage.

I just downloaded last version of Recount. So far i notice a very nasty bug:recount doesnt collect pet (demon ) data properly.
I have the "merge pet dmg" option on, however recount doesnt collect any data for Felhunter's dmg. When i turn it off there is no change in my current dmg/dps but i see felhunter's dmg on a seperate line. Puting the option back on removes felhunter from the table and my dps still stays unchanged.
Please check if there is some problem with pets dmg and merging pets dmg with players dmg. THanks. :D

I would love if you could add an option for outlines.

Date: 2011-11-29 23:12:56
ID: -1
Error occured in: Global
Count: 1
Message: ..\AddOns\Recount\Tracker.lua line 1183:
attempt to perform arithmetic on local 'amount' (a nil value)
Debug:
(tail call): ?
Recount\Tracker.lua:1183: AddAmount2()
Recount\Tracker.lua:1805: AddDamageData()
Recount\Tracker.lua:577:
Recount\Tracker.lua:564
Recount\Tracker.lua:1033: ?()
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147:
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147
[string "safecall Dispatcher[18]"]:4:
[string "safecall Dispatcher[18]"]:4
[C]: ?
[string "safecall Dispatcher[18]"]:13: ?()
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire()
...s\AckisRecipeList\libs\AceEvent-3.0\AceEvent-3.0.lua:120:
...s\AckisRecipeList\libs\AceEvent-3.0\AceEvent-3.0.lua:119

Update.

nvm its fixed

I'd need something more tangible than people blaming Recount for performance issues. I.e. is there any indication of increased combat log traffic? If yes what events are unusually frequent etc etc?

Edit:

http://www.mmo-champion.com/threads/1032766-Ultraxion-FPS-Issues

There is no consensus that it's a Recount issue. In fact people report the problem with Recount turned off. Now if a machine is challenged, running Recount does have a chance to make it worse. And it may in some configuration be what makes the difference. But by the sound of it, it is simply the event volume/graphics detail that is the issue. So yes, use /recount pause for the encounter to lower your machine's load. But this does seem to me to be an issue on Blizzard's side, given that it will choke players who don't run the addon.

Can you no longer click on names and have it show details? it does nothing

Quote from Elsia

I'd need something more tangible than people blaming Recount for performance issues. I.e. is there any indication of increased combat log traffic? If yes what events are unusually frequent etc etc?

Edit:

http://www.mmo-champion.com/threads/1032766-Ultraxion-FPS-Issues

There is no consensus that it's a Recount issue. In fact people report the problem with Recount turned off. Now if a machine is challenged, running Recount does have a chance to make it worse. And it may in some configuration be what makes the difference. But by the sound of it, it is simply the event volume/graphics detail that is the issue. So yes, use /recount pause for the encounter to lower your machine's load. But this does seem to me to be an issue on Blizzard's side, given that it will choke players who don't run the addon.

The reason fps get grinded to a halt in this fight is very specific. There are 3 healer buffs in this encounter the offender in this case being the second one which duplicates your healing and splashes it to entire raid within 50 yards(in 25-mans for example the problem is 3 times worse than in 10-mans for obvious reasons(more players etc.)). As you can see this produces a ton of healing events and it's heavily dependant on healing classes (example: holy priests/shamans using holy word:sanctuary/healing rain + echo of light ticks/earthliving ticks will produce way more healign events than say a druid or a paladin). These 2 classes basically will wreck fps on even the strongest computer because of the sheer magnitude of healing events happening past that point.

This problem although is not recount specific since if you use any other addon that parses the combat log will have similar results and wreck your fps as well.

Some suggestions now to circumvent said problem:
1) Add a switch to toggle healing on/off.
2) Ignore completely healing produced from Essence of Dreams(This is the healer buff that causes the issue).

The problem is not parsing healing events. The problem is that the machine is overextended for performance. Even if all healing events were disabled, and Recount only parsed damage events it would still degrade performance as the machine is already exceeding its performance cap. This is precisely why different people report different effects:

1. Some have no issues. Their machines are not performance capped.
2. Some report 25FPS with, 9FPS without recount on a machine that will run at 60FPS everywhere else. The problem here is the 25FPS, i.e. the machine is already overloaded. Any extra load will drop the FPS and it doesn't matter if it is related to combat log events, though if it scales with it it surely has a chance to make it worse.
3. Some report unplayable FPS without recount. Their machines are so overloaded that it doesn't matter anymore.

There is no one fix. Clearly blizz has designed an encounter that is too testing on many systems. I recommend disabling recount (/recount pause) for anybody who is in category 2) and 3), because anything but disabling recount (and any other addon that does substantial computation) will inevitably degrade your system's performance. You can leave it running for those in 1). And report to blizzard hard. It's them causing this.

Quote from ZedFighter

Date: 2011-11-29 23:12:56
ID: -1
Error occured in: Global
Count: 1
Message: ..\AddOns\Recount\Tracker.lua line 1183:
attempt to perform arithmetic on local 'amount' (a nil value)
Debug:
(tail call): ?
Recount\Tracker.lua:1183: AddAmount2()
Recount\Tracker.lua:1805: AddDamageData()
Recount\Tracker.lua:577:
Recount\Tracker.lua:564
Recount\Tracker.lua:1033: ?()
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147:
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147
[string "safecall Dispatcher[18]"]:4:
[string "safecall Dispatcher[18]"]:4
[C]: ?
[string "safecall Dispatcher[18]"]:13: ?()
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire()
...s\AckisRecipeList\libs\AceEvent-3.0\AceEvent-3.0.lua:120:
...s\AckisRecipeList\libs\AceEvent-3.0\AceEvent-3.0.lua:119

I'm having this exact same error. It seems to be linked to record "non-trivial" mobs. When I have it checkmarked I get the error spammed at me, and when I remove the checkmark the error stops.

It doesn't seem to happen when there are no mobs present. However, just flying around something like Hyjal will get the error to start appearing. I am using the latest version of Recount.