This post goes over ways to pull specific types of lines from combat logs of the current raid tier so that you are only looking key information from a fight. Viewing raw log data may seem simplistic compared to the flashy summed and/or averaged figures that World of Logs (WoL) and Recount provide, but don’t be deceived: looking at log lines directly can be incredibly useful, as I describe and then demonstrate after the break.
Posts Tagged ‘wol’
Posted in World of Warcraft, tagged Atramedes Sound, Bastion of Twilight, Blackwing Lair, Cho'gall Corruption, expression editor, query language, Throne of the Four Winds, tier 11, wol, world of logs on May 6, 2011 | 3 Comments »
Comparebot is a useful analysis tool that takes World of Logs parses and winnows that information down even further. It does not display more or better information than World of Logs. It does, however, do more legwork for the user than WoL, pulling out important bits of information and presenting them in ways that are easy to access and understand. (more…)
How is DPS actually calculated? Why do meters love mages? How do you figure out how much damage you and others did to adds or shields? This post answers these and other questions in a discussion of how to read damage meters. The post only focuses on interpreting damage counts on Recount and World of Logs (WoL) and leaves the other uses for those tools for another time.
sourcename="MyName" and (type=TYPE_CAST or (type=TYPE_AURA and (spell="Exploit Weakness" or spell="MyTrinketBuff")))
Comparing predicted to actual damage:
- Configure the dps analyzer with your exact gear, spec, glyphs, pet, etc.
- Make sure to review your raid makeup from the log and apply the exact buffs and debuffs that were available to you. In some cases you may have to make some educated guesses. For example usually enhancement shamans will provide improved strength of earth totem, if you don’t have one chances are you only had regular strength of earth or the DK equivalent. In some cases you may want to check the listed debuffs on the boss to see if important ones were actually being applied (sunder/expose for example is often forgotten when there is no protection warrior).
- If you are looking at an ICC fight, be sure to apply the specific strength of the zonewide buff under Custom Buffs (you can fill it in under both magic and physical damage and be sure to specify that your pet got it too if it isn’t too old a log).
- Go under settings and adjust your Latency to a reasonable estimate of what you think it was on the fight. Look at the fight length in your log and fill in reasonable estimates for the Fight Length and Fight Time Spent in Kill Shot Range. The easiest way to find the kill shot range is probably to check the Log Browser for your kill shots then do the math to figure out the fraction of how long (in minutes) you were in range of kill shot. For example if the fight length was 3:43 and your first kill shot was 38 seconds before the end of the fight, reasonable numbers to fill in would be a 3.7 min fight length and .6 min in kill shot range.
- Review the Wait Time settings under Shot Priority and be sure they reflect your preferred delay time and shots. Also make sure to adjust sniper training uptime to match what’s listed under the log if you’re SV.
- Update DPS. Now copy down just the hunter dps and pay attention to that figure. Unless your pet dps is way off from what’s expected, chances are any problems dpswise are on the hunter side and not the pet, so let’s just look at the hunter dps.
- Look under the debuffs and buffs you gained to see if there are any things that happened during the fight you want to account for. For example if you had a vile gas uptime of 5.3%, you want to reduce your estimated dps by that amount before comparing. If you had to viper you obviously will want to calculate that in as well (assuming the site didn’t already have a viper penalty for you). Also be sure to apply any special buffs someone might have applied to you like tricks of the trade.
- Check for any misses that are above the expected miss rate. Usually this is caused by getting out of range of a Draenei hit buff if you’re relying on one. Add up the average value of each shot missed above the expected amount and divide by the number of seconds to figure out how much dps you lost to this so you can get a new estimated dps.
- To estimate how many autoshots you were expected to fire, take your Average Autoshot Speed (under Effective Haste) and divide the fight length by it. Then reduce this amount by any time on the fight you were incapacitated. This should give you a good idea of if you’re losing autoshots for some reason. Note that the numbers may not match up exactly since there are haste procs and other factors involved, but if the numbers are significantly off that may indicate a problem.
- Compare the number of shots fired to the expected amount displayed in the Shot Priority section of your estimated dps output. Be sure to apply the expected reduction in shots based on the time you were incapacitated on the fight. For example if you were expected to fire 81 steady shots and you had a vile gas uptime of 5.3%, then you actually should only expect 76 steady shots, some of which may have been replaced by arcane shots due to movement. Also be sure to subtract an expected steady shot if you manually refreshed serpent sting for a %dmg buff (which most MM users will do on a straightforward fight).
- Check under your buffs to get an idea of if you used your cooldowns (such as rapid fire) as many times as expected.
This should give you a fairly good idea of where the gaps in dps estimated versus dps real dps are coming from and whether you’re using your shots as efficiently as you could be.