You're quite right manta. And the main reason we're using the active dps stat is because fight dps would produce the same relative bars compared to damage done, just with a different number next to it.
I really like violation (with combat log at 250 yds) but when I run it in parallel with damagemeters there are discrepancies of 30+k. Anyone know what can be causing this?
DamageMeters syncs and gets all wrong data, while violation gets everything right? :o
DamageMeters has a very different way of synchronization. DMM spying in violation is off by default due to that way. DMM can suddenly spam all the data for a fight after a fight is over and violation can't cope iwth that yet. If you have DMM spying on and DMM users in your raid then your data might be polluted.
Lately I've been curious about just how much spam goes through the addon communication channels during raids. I've modified the Decurse module into a standalone module which records the amount of data that each person in your group sends through addon communication channels. The length of the string of any addon message that you can see from each group member is counted.
An interesting problem is that with this addon running, you will appear to generate tons of data yourself since Violation's own data sharing messages will count towards your total and as your total increases, Violation keeps sending more sharing messages.
Personally, I'd like to see a list of all of the different prefixes observed (BigWigs, CTRA, KLHTM, SWSudX21, etc.) and what percentage each consumes, but I don't think that's possible within Violation.
Write a custom app to record that. Violation truly wasn't meant for this.