Hey, me again

After some more testing while farming for my spellpower enchant, I noticed a little glitch again.



Notice the fight that is selected. It ends sooner than it starts. I was fighting multiple mobs at the same time and chain pulling so that might have to do something with it.

Btw, any idea when you'll be able to add labels to the graphs?
And again, thanks for making this.


Off-topic: What exactly does Protractor do?

The latest Recount version already has labels? (you using the latest version of GraphLib?)

And on the time differences yeah I've noticed that not sure whats causing that yet.

Its a CPU/Memory Profiler for 2.1

Oh I know the issue with the offset.

Its because I use a 25 second time window resulting in it getting shifted 25 seconds to the right. Not noticeable on long fights but is on really short ones.

Yeah, I was using an older build of the addon, since I didn't check the wowace site tonight before logging on. Sorry for that.


Another thing I noticed is that the addon calculates the DPS over the entire 25 sec period even when the fight lasted shorter than that. This shouldn't really matter since the reason we want this is for boss fights which tend to last longer than 25 secs. Well, at least the good ones do :P

One thing that this issue brings to mind though is people deaths in a boss fight. Will the addon stop calculating stats for a raid member that died on the attempt (exited combat)?

Did I make any sense with that?


P.S.: I'll test on Dr.Boom for a longer fight as well.

Yes, this is an issue with using a filter window for calculating DPS. The filter is that large so it doesn't look bursty and is intended for fights of decent length.

It tracks party/raid combat not individual player combat. Also if you are in combat or not has nothing to do with is data being recorded.


Also I should make note the labels are only for the Y Gridlines still haven't decided how to handle it exactly for X Grid Lines.

Aye just tested Dr.Boom and it looks good. I even had a mage join in at 40% or something and it picked him up really nicely.

I'm posting graphs of the 2 of us if they will be of any use to you. The fight lasted for 12 minutes and 15 seconds.



This is a graph of me. It's really nice to see my dps drop at the same time i needed to drain life (my healing picks up). And my peak at over 1200 DPS at the end was a back to back crit. The visual representation can really help remember certain events.




This is the mages DPS chart. He joined late, died once and then rezzed and continued to help since he needed the quest. He also stopped dpsing a few times (OOM). All of which can be seen on the graph.


All in all I'm very pleased with the representation of the lengthier fights so far.


------------------------------------

Regarding the X-label:

- I can foresee some problems in lengthy fights like this, since it'll be hard to see events that took 10 to 20 secs due to the scale having to incorporate all 12 mins. Now the first thing that comes to mind is for the user to choose a certain segment to view more carefully or to be able to change scale of the x-axis, but in the latter case you'd need a way to scroll the graph horizontally then, which might be a problem I guess.

As for the label on the x-axis I suggest for the default to be seconds of the fight divided into the 25 sec chunks you use to measure data.

This is all of the top of my head right now so I could be suggesting something too extreme, since I've never coded in LUA before.

And ofc, great job so far!

I might have missed something or I'm completely out of my league here so I apologize if this isn't relevant. Anyhow, what I'm wondering is if it wouldn't be interesting to have the graph display actual damage as it occurs instead of the damage per second. Maybe it could be displayed as little bars?

Anyhow, this sounds like a very interesting project. Best of luck with the development.

Should have seen the memory usage it was tracking before I made one change today (went from 17mb sitting around doing nothing except some tests to practically to below 500k in the same situation). Heh, was hoping to test some in raid usage today and of course servers acted up too much around our raid time for too long.

I'm thinking of some way to enable/display ticks on the fly for spells with tick damage.

At the moment not possible since I run it through a filter on the fly. There is the possibility I could store raw data and process it when data is being displayed. Was concerned about performance on graphing then though it would lighten the CPU usage on the per tick operations.

Very much liking this so far despite some bugginess. Keep up the good work

psssst actually the dmg done is represented by the the area under the DPS graph

BTW, if you have script profiling enabled you take like a decent hit to framerate. I go from around 50+ FPS most the time without script profiling to 30 FPS sitting around and 20 FPS in combat with script profiling on.

SWS's issue I bet is with their new unilog which is kinda neat but kinda not that neat. Now if I had lots of spare time and wanted to come out with something competitive against their unilog it would be Matlab for WoW with damage variables autoloaded.

I only really have a few feature requests in no particular order.

Sync'ing.... Yeah a the huge one. I know its a ton of work but I always used to get better accuracy fron sws, presumably because it was sync'd.

Remeber positioning. Right now I seem to have it reset to the default position in the middle of the screen everytime I log.

Configurable bar textures. Almost all of my addons are ace2 using the aluminum texture through surfaces. I'd really love to have them all the same just that little bit of extra would be cool.

Death Count. If you could count how many death and who killed people that would be aweseome and very graphable.

Average line for the dps graph. That would be awesome.

Accuracy I found is absolutely not dependent on syncing or at least before the patch. I need to verify the reduced combat log range actually came around for the live 2.1 or not. If it did then well that will move when I do syncing. And by that I mean I found repeatedly I was matching the exact amounts for the top 10 I was checking between SWS and Recount for most fights (of course this doesn't work well for fights like Al'ar where you are in a room much larger than 200 yds).

Yep, needs that of course. Just not real high on the list compared to other stuff I'm trying to polish more.


Thats in the I need to make an options window because I think the default make a console command list then use dewdrop/waterfall is a horrible way to handle options.

Thats in the plans

Cryect, is there any way that one could do this sort of thing with threat per second in conjunction with KTM? It's hard to tell post-battle how much threat was being generated at any given time and I would really love some way to track how our tanks are doing in relation to each other. Just a thought, obviously this would take a good deal of work, I'm more curious about its viability than anything.

It takes absolutely no work at all actually if someone just tells me the KTM Self Threat variable which I know someone was talking about the other day in some RDX thread.

edit: Err guess I need the threat var as well for other people but I assume its some sort of table.

Very nice, I'll test it in tonight's raid.

I think that now the major things missing are comparisons of multiple (2) graphs, the x-axis labels and maybe syncing, although you said you didn't have problems with it.


I think the addition of the threat graph is an excellent way of comparing tanking classes. Really curious how it'll perform in the raid.

One oddity I saw yesterday when using it was that I fought the summonable whip-girl in Bash'ir landing, but she didn't show up in the list of combat sessions. Do you think it was just that the session was labeled by some other mob that died in the vicinity (I definitely wasn't in combat when we engaged, but maybe someone else was). Her data was definitely parsed, cause she was in the chart of who I attacked over the whole Recount session.

One thing I've noticed is that the TPS can go negative on KTM, which makes the TPS graph go through the bottom of the graph window.

Also just a minor feature request, but one thing I love about Recap is the auto-minimize feature; a lot of people love bars updating mid-combat, but I don't find that information to be terribly useful, but I do like being able to mouse over a certain area of my screen with a minimized Recap to have it's window pop up with the general oversight of what people do.

I love you.

I'm very much enjoying this addon and definately believe it will become the new SW Stats. Though I'm having one slight issue and that is of not being able to get the combat log back on to my screen after I foolishly closed it. I'd appreciate it if you could tell me how to get it back as I've gone through the code and haven't been able to find how to get it back. Keep up the great work

Was your fight less than 10 seconds? That or if it can't find the target doing damage to someone while in combat.

Ummm well Recount doesn't have anything to do with your combat log being displayed if you mean the main window though thats /recount show