Heh, after finishing up a demo of my libraries Mode7 and GPSLib in an addon called Dungeon Crawler (check my sig if your curious), I went back to work.

1. 5 Time Data Values Being tracked as seen each can be enabled/disabled
2. Space for 5 more Time Data Values which will be where the second player/mob can placed
3. The bottom section is the times of fights, here you will be able to select fights(or range of fights to show)
4. The fought column will display the name of the highest level mob fought in that fight (tooltip will show names of all the mobs)
5. Data will also be deletable here
6. Times in and out of combat will be displayable on the graph as filled in regions (red regions in combat & green out of combat will be light alpha so just slightly noticeable).

Any update on how the CPU/memory usage is looking right now? Definitely very eager about seeing this finalized - but I'm just a tad worried about how this'll play out in-game (particularily w/ the data collection; client side lag is something I consider critical since I have DPS riding my *** on the threatmeter and Shield Block to keep activated :P)

Does Overhealing mean overhealing taken or overhealing done? Is healing effective healing (no overheal included) or do you have to display overhealing to see that visually? For the times, any chance of doing start + duration instead of start to end? I know for myself it's easier to remember durations than exact times.

Did memory concerns push it to track only two targets at a time for the new graph? Or am I reading too much into things?

I'm not tracking those considering I'm not on 2.1. The only times I've got lag is if I try to display a graph of like 10 minutes of data and thats due to I need to make things smarter how they are handled.

Memory usage isn't going to add client lag so that shouldn't be a worry. If you set it up to record Time Data for everything (including people/mobs not in your raid) then yes it will be a little high.

Overhealing means overhealing done (I can't see any really good reason to track overhealing received). I only have effective healing since I believe its an unnecessary factor to show an additional data value that means nothing without considering overhealing (in which case why not look at their overhealing).

Memory concerns have nothing why its only 2 people comparison. The graph the way it works can receive up to 10 data sets so you could if you only sent 10 people's damage done to the window it would work. I prolly will remove that limit though. I'm trying to prevent the player from information overload with worthless graphs because they decided to graph everything they could think of on one graph.

Oh and I forgot to say before I need to add in numbers to the graph of course.

With a chance of making a none contructive post I must just say that this is a project I am following closely as the statsfreak I am... Keep up the nice work!

I downloaded the addon from wowace, since I saw it was in the files section as well, but I had an error popping out whenever there was a friendly character nearby doing damage as well.

I realize the addon is still being worked on, but I just thought it might help you to know this.



Btw, if you need any help testing the addon out, just say so

And thanks again for making this.

Error fixed!

And yeah I should add something so you can see those type of events on the graph.

The KTM hack didn't do much so not going to post it

Would be nice if you can look up the healing curve for a specific player (maybe even several if you want to compare them) to evaluate the effectivness of healing.

Btw your memory usage mod works kinda nice for the memory usage but CPU usage displays no usage for all mods and the third option (dunno its name - not at home at the moment - ) freezes the screen for about a minute and pops up the Error Reporter (looks like too many data) and returns no values aswell

unless you are on the PTR i assume that cpu profiling isnt implemented for current live servers/clients

I am on PTR - the whole mod doesnt work pre 2.1 since memory profilijng and all that stuff comes with 2.1 - Dunno he said the mod isnst finished yet - maybe that part is still unfinished

One thing that I would love to see in WWS (or something similar to that) is:

- a graph of the dps of the raid + a graph for each member
- a graph of the dps of one member spanning multiple raids for the same boss fight. The graph maybe enhanced to mark areas that the member is affected by temporary buffs: destruction potions, trinkets, bloodlust/heroism you get the idea
- a % of how much time the MT was out of shield block for the duration of the encounter
- a % of how much time the boss was out of each of some important important debuffs: TC, FF, DS/DR, SE, CoR (for some bosses like Aran for example), CoS, CoE
- a count of how many crushing blows the MT took (hopefully none :-p)
- a % time of casters (mainly healers) being out of FSR

I am toying with the idea of building something like this up, but it would take quite some time, given the limited amount of time I have lately :-)

I'm really excited about this addon, I've wanted to do something like this for a long time, but never really had the drive to. I downloaded your current release from wowace and just thought you'd like a bit of feedback.

Some bugs I saw:
1) If you put the mod on standby then reactivate it, it will open up a new window without closing the original, so there will be two.
2) Resetting the mod doesn't update the current window, so you have to close it and reopen it. Giving some nil value errors.
3) I cannot find any way to reliably open up the graph window. It sort of just popped up all of a sudden once.
4) The graph window doesn't seem to be updating while in combat, but if I check and uncheck options while data is being parsed, it will update the graph in real time (by doing it repeatedly).

I've done some quick testing of my own as well. I managed to get another error which seems to try to index something which doesn't exist.



I'm not exactly sure what I did to get this error, but I got it while browsing through different fights in the graph window. I think i double-clicked on a fight to get this error, not sure though.

I have some suggestions of my own as well:

- numbers at the x- and y- axis would help a lot / overlays of the measured value on graph peaks

- I'm guessing you have the number of fights the addon remembers capped right now; it would be nice if we can choose which fights to disregard and which to remember

- comparison between people: i'm not sure if i just don't know how to do this or if you haven't implemented it yet, but it would be great to be able to compare damage done graph of, 2 mages let's say.

- synchronization between the raid members


Other than that, I have only praise for this. Thank you so much for taking the time to do this for us, stat hungry dicks

I'd love it if it recalled boss fights (or periods of combat in which you fought a boss) and discarded trash fights. Perhaps a setting to simply ignore non-boss fights might be handy, for those of us who don't really care about the trash data.

Yeah, labeling will be in. Still thinking how to do things like moving your mouse around and showing peaks (thinking something along the lines of you select one data set and then a vertical line is shown with numbers in tooltip).

Its not actually capped just I didn't add the code in yet for scrolling past the first 10 :p

In plans to be done.

On the list of course to be done, working more on getting the UI down at the moment. I rewrote a good portion of the data tracking with this in mind the other day.

Thats in plans as well plans for in the filtering section of being able to select what type of data you want recorded for what.

Bug is now fixed was in a rush last night to finish up new feature so I could goto sleep that I didn't notice buggrabber grabbing that one.

Thank you for your quick reply. I hope I'm not being too intrusive or annoying with the suggestions and error reports It's just how I get about something new.

Anyway I'll keep on testing the addon and continute submitting my "reports" if it's ok with you.

BTW if you were testing out Protractor on the test server earlier and it didn't seem to be working. Thats because it didn't enable script profiling by default. I switched it to do that now in the version I released 5 minutes ago.

Oh also make sure you ReloadUI() once after it starts the first time since the profiling doesn't take effect right away.

Edit; Rats its not working right >_>

New Version works!

BTW at the moment fixing up memory usage of Recount a little. Already made some minor changes that result in massive improvements.