[2008/05/07 22:06:29-4305-x254]: Recount-70425\LazySync.lua:581: bad argument #1 to 'pairs' (table expected, got nil)
Recount-70425\LazySync.lua:581: in function `AddOwnerPetLazySyncAmount'
Recount-70425\Tracker.lua:658: in function `AddTimeEvent'
Recount-70425\Tracker.lua:1252: in function `AddDamageData'
Recount-70425\Tracker.lua:343: in function `parsefunc'
Recount-70425\Tracker.lua:584: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...tus\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[10]":4: in function <[string "safecall Dispatcher[10]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[10]":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
AceEvent-3.0\AceEvent-3.0.lua:70: in function <...Ons\aX_RaidStatus\libs\AceEvent-3.0\AceEvent-3.0.lua:69>
But Sync is disabled according to /recount gui ...
And also once these errors occur, damage recorded goes way out of whack.
70425 is the version shown in BugSack... seems like you don't sync the files revisions.
Actual revision I'm having is 73072, my fault.
Line 581 looks like the one posted in here as correction.
The column text in the detail window overlaps with some fonts. 1680x1050 resolution, 0.8 UI scale. See attached screenshot.
...and even when the fonts don't overlap, the percentage could use some buffer space in front of it. When the percent column is 100%, the prior column will run right into it, meaning if you have the value 2314 in the prior column, "2314 100%" will look instead like "2314100%".
Ah I see I get an idea what could be the issue here. Are the people who long on still in the recount data from earlier raids for some reason? Or are they even invited but sit out?
I have the notification on to show when any1 from my guild comes online. Not sure but might have been that the error popped up also when any1 from my guild came online.
@mega: Are you using the latest version? The spacing has been adjusted already. I can image that some super-wide fonts still can cram the display but it should be fine for all typical fonts now.
@pqee: The boss segmentation relies on mob level to be -1 (skull). Unfortunately most 5-man bosses are no longer skull but share the same mob level as some trash, so this method isn't working to segment for 5-man bosses. Improved segmentation support is on my list but it'll be a while as more pressing other issues will come first.
@elk: Thanks, will be fixed with next commit. Missing parenthesis.
@esaiah: Thanks. Next time it happens can you send me the full bugstack so I can identify which line in recount causes this? From the debug message you sent me it could actually be another addon causing the error. So I need to see the full think to know for sure what's going on here.
@pqee: The boss segmentation relies on mob level to be -1 (skull). Unfortunately most 5-man bosses are no longer skull but share the same mob level as some trash, so this method isn't working to segment for 5-man bosses. Improved segmentation support is on my list but it'll be a while as more pressing other issues will come first.
My apologies if this has been answered before, but each time I use the wowaceupdator to install this mod, it comes up in the center of my screen, I'm unable to move it whether it's locked or not, and I can't click the gear icon to bring up the preferences. To compound that, the mod doesn't actually do anything either. Many in my guild use this program so I'd like to as well, but clearly I need to resolve this first.
There a direct download I can try rather than the updater doing it?
Edit: As I suspected, the updater version was what was breaking it. The direct download from page 1 of this thread took care of it and it seems to work great now.
@mega: Are you using the latest version? The spacing has been adjusted already. I can image that some super-wide fonts still can cram the display but it should be fine for all typical fonts now.
I'll have to update and check again tonight when I get home and see if that resolves it, since it looks like some updates were made since I last updated earlier yesterday. I'm just using Segoe UI (via SharedMedia->MyMedia), so it's not an extra-wide font or anything. ;)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBut Sync is disabled according to /recount gui ...
And also once these errors occur, damage recorded goes way out of whack.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI think that should do it. (Also, argument spacing is super-inconsistent, but that's just me nitpicking. :p)
Phanx: I know that the layout is too tight for wide fonts. I'll look into making the detail window wider overall so that there is space.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWhat was odd though was that I had sync disabled in the Ace3 config GUI for Recount, and yet it was still executing sync code?
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorAnyway to make the option to keep only boss segments to include 5-mas instance bosses? Whether a .lua hack I can do or an official update?
Thanks!
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorActual revision I'm having is 73072, my fault.
Line 581 looks like the one posted in here as correction.
...and even when the fonts don't overlap, the percentage could use some buffer space in front of it. When the percent column is 100%, the prior column will run right into it, meaning if you have the value 2314 in the prior column, "2314 100%" will look instead like "2314100%".
I have the notification on to show when any1 from my guild comes online. Not sure but might have been that the error popped up also when any1 from my guild came online.
@pqee: The boss segmentation relies on mob level to be -1 (skull). Unfortunately most 5-man bosses are no longer skull but share the same mob level as some trash, so this method isn't working to segment for 5-man bosses. Improved segmentation support is on my list but it'll be a while as more pressing other issues will come first.
@elk: Thanks, will be fixed with next commit. Missing parenthesis.
Fair enough. Thanks for the response.
There a direct download I can try rather than the updater doing it?
Edit: As I suspected, the updater version was what was breaking it. The direct download from page 1 of this thread took care of it and it seems to work great now.
I'll have to update and check again tonight when I get home and see if that resolves it, since it looks like some updates were made since I last updated earlier yesterday. I'm just using Segoe UI (via SharedMedia->MyMedia), so it's not an extra-wide font or anything. ;)