Recount already supports storing real-time window positions. I cannot really reproduce this problem as it does keep the windows in the saved position for me. Can you do me a favor and do three things: Can you turn off your frame-moving addons and see if they wrongly try to force the window in the wrong position? If that doesn't help delete the Recount.lua files from your WTF/* folder. If that doesn't help let me know which specific real-time window you are talking about, i.e. if its for a character or for a raid/network window.
Yep saw, great news. I ditched the CVar code for the PTR version a long time ago though, if anyone gets that error you use the live version on PTR and not the 2.4 PTR version.
Recount already supports storing real-time window positions. I cannot really reproduce this problem as it does keep the windows in the saved position for me. Can you do me a favor and do three things: Can you turn off your frame-moving addons and see if they wrongly try to force the window in the wrong position? If that doesn't help delete the Recount.lua files from your WTF/* folder. If that doesn't help let me know which specific real-time window you are talking about, i.e. if its for a character or for a raid/network window.
Pardon the mess, i'm in the middle or building a new ui. Anyway, these pics were taken after I deleted the lua files from both my account folder and character folder. Notice that i'm using the smallest scale(.5) and that the lock windows option is checked. The focus of these screenshots are the Latency and FPS graph frames at the bottom. Both have been scaled and positioned in a manner that I would like them to be:
last night I was in some arena fights, and saved the data to view after the fact. (2v2 fights) it was kind of odd, but some times I saw 3 people on the list not 2 or 4 as I would expect?
Also, my team mate was a hunter (I have merge pets on, and show pets in list off) If I click on him to see his data screen, I can't find his pet anyplace. when they are merged in, where do they show up??
Love this mod, it's been helpful in my knowing I'm making improvements to DPS! :) I hope the 2.4 patch helps make SHaman data even more accurate, as far as recording more data known to be mine, like Elementals and damage caused by my totem. :) (maybe I'm closer to my hinter friends DPS that I know!)
Don't know if this has been reported yet, but if a hunter has a pet with the same name as the hunter, recount does not work correctly and there damage resets everytime the pet hits. Is this fixable with the current version of the combat log? (2.3) or will we have to wait for 2.4?
Has anyone had problems with lag/delays when using recount? Spamming lifeblooms I usually have 4 global cooldowns to work with, Last night raiding I had 2-3, disabled recount and had 4 again. Now a friend of mine suggested I disable recount, but it doesn't make much sense to me that it would cause this problem (and it could have been a coincidence that things improved). I had 70ms and no fps problems before and after disabling recount, so that's not it, and the change between 3 and 4 gcd's was very noticable.
@Grendalf: I assume that's Recount for Live? I'll try to see if I can figure this one out when the servers come up again. In the meantime can you check if you have Threat-1.0? That missing function is from that library.
@Darkclaw: It very much depends what you see from the filters in the data setting and what actually happened in the fight. For example if you only collect and show friendly data, you really only should see your part, unless you mind-controlled someone. Then that person will show up as pet too. If you want detail about pets, disable merge pets in the options and the pet will show as a separate bar with all the details of what it did.
Word is in about shaman damage. In the current PTR it is still the least comfortable to track and some things are still impossible to track, such as greater elemental damage. Also it is still impossible to track earthshield and lifebloom properly, but just very recently improvements for the latter have been promised for a later patch. 2.4 will improve a lot of things but some improvements will have to wait for a later patch even. Specifically a number of shaman related things. Most other classes should be very managable to handle come 2.4 (well that means I don't know of a case where their damage can't be tracked back to them).
@icemanwol: Yeah it's been reported before and it's impossible to correct in 2.3. 2.4 will fix this though, I'm just waiting for the promised API calls to actually making it onto the PTR to implement this in the current 2.4 Recount in the branches.
@neuron: The likely main cause is that some recounts in your raid have sync turned on. This causes very high network traffic and I strongly advice that everybody in raid turns it off unless you absolutely need it. The sync situation will get much better for 2.4.
@neuron: The likely main cause is that some recounts in your raid have sync turned on. This causes very high network traffic and I strongly advice that everybody in raid turns it off unless you absolutely need it. The sync situation will get much better for 2.4.
Will it cause lag if someone else in the raid has it on, and I dont?
I probably did turn that on myself though, I have a habbit of opening options and pulling all the levers :P, you might wanna put a warning on that option or something ;)
Yeah others having it on matters, so you may alert people to turn if off if you have issues. Recount will very likely greatly improve in that department with the upcoming patch 2.4.
The current commit has a lot of new strings prepared for localization. I think we are pretty close if not already complete with localizing strings. Any localizer volunteers very much encourages to add translations for the new strings! Thanks!
I would like the option in the "damage done" list to have it not show the percent of damage you do for the raid.
The only numbers I really care about is total damage done and dps.
So instead of having this "Galvin 9891212 (800.2, 99.0%)" you could have
"galvin 9891212 (800.2)" or even make it so its completly configurable by letting the user make the columns himself.
Elsia, I'm just going to punt my favorite request --- shot count in the personal dmg detail (#, dmg, dmg%). I know you've already said you liked the idea but just want to make sure it isn't forgotten :)
Yeah both of these ideas are on the wishlist already. New features are kind of slowed now that I focus on all the things that need to happen for the 2.4 patch. I probably won't look at a lot of things (except bugs or things that need to happen for 2.4 anyway) until that's done. So nothing is forgotten, there just isn't much time right now for some things.
I've committed a new 2.4 branch version that now uses only Ace3 and very few other dependencies. This was a rather massive change and while it looked good to me it certainly could use some good testing, so any feedback very welcome as always.
I am testing new recruits for the next two weeks. Is there anyway I can save multiple boss encounters per run so I can review after raid? So let's say we have a kill on Najentus, Supremus, Shade and I want to save data for kill attempts for review later. How can I accomplish this? Thanks in advance for your help!
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBlue just posted on the 2.4 changes thread: "The combat log range is now everything that you can see."
Hawksy
Pardon the mess, i'm in the middle or building a new ui. Anyway, these pics were taken after I deleted the lua files from both my account folder and character folder. Notice that i'm using the smallest scale(.5) and that the lock windows option is checked. The focus of these screenshots are the Latency and FPS graph frames at the bottom. Both have been scaled and positioned in a manner that I would like them to be:
After a reloadui or logout:
What Move Anything shows:
What Visor2 shows:
So if you join a party that is turned into a raid and then enter an instance you will only get one confirmation window instead of three.
Date: 2008-02-26 19:21:01
ID: 53
Error occured in: Global
Count: 1
Message: ..\AddOns\Recount\Sync.lua line 335:
attempt to call method 'TranslateForeignMobName' (a nil value)
Debug:
...\AddOns\AtlasLoot\Libs\AceEvent-2.0\AceEvent-2.0.lua:301: TriggerEvent()
...\AddOns\AtlasLoot\Libs\AceEvent-2.0\AceEvent-2.0.lua:914:
...\AddOns\AtlasLoot\Libs\AceEvent-2.0\AceEvent-2.0.lua:907
AddOns:
Thank you
last night I was in some arena fights, and saved the data to view after the fact. (2v2 fights) it was kind of odd, but some times I saw 3 people on the list not 2 or 4 as I would expect?
Also, my team mate was a hunter (I have merge pets on, and show pets in list off) If I click on him to see his data screen, I can't find his pet anyplace. when they are merged in, where do they show up??
Love this mod, it's been helpful in my knowing I'm making improvements to DPS! :) I hope the 2.4 patch helps make SHaman data even more accurate, as far as recording more data known to be mine, like Elementals and damage caused by my totem. :) (maybe I'm closer to my hinter friends DPS that I know!)
@Darkclaw: It very much depends what you see from the filters in the data setting and what actually happened in the fight. For example if you only collect and show friendly data, you really only should see your part, unless you mind-controlled someone. Then that person will show up as pet too. If you want detail about pets, disable merge pets in the options and the pet will show as a separate bar with all the details of what it did.
Word is in about shaman damage. In the current PTR it is still the least comfortable to track and some things are still impossible to track, such as greater elemental damage. Also it is still impossible to track earthshield and lifebloom properly, but just very recently improvements for the latter have been promised for a later patch. 2.4 will improve a lot of things but some improvements will have to wait for a later patch even. Specifically a number of shaman related things. Most other classes should be very managable to handle come 2.4 (well that means I don't know of a case where their damage can't be tracked back to them).
@icemanwol: Yeah it's been reported before and it's impossible to correct in 2.3. 2.4 will fix this though, I'm just waiting for the promised API calls to actually making it onto the PTR to implement this in the current 2.4 Recount in the branches.
@neuron: The likely main cause is that some recounts in your raid have sync turned on. This causes very high network traffic and I strongly advice that everybody in raid turns it off unless you absolutely need it. The sync situation will get much better for 2.4.
Will it cause lag if someone else in the raid has it on, and I dont?
I probably did turn that on myself though, I have a habbit of opening options and pulling all the levers :P, you might wanna put a warning on that option or something ;)
Thanks for the help.
The only numbers I really care about is total damage done and dps.
So instead of having this "Galvin 9891212 (800.2, 99.0%)" you could have
"galvin 9891212 (800.2)" or even make it so its completly configurable by letting the user make the columns himself.
thanks