Fury DPS Spreadsheet for 3.0

landsoul · 03/17/08, 4:59 AM

/********WARNING: DO NOT ATTEMPT TO USE THE OO SHEET UNTIL YOU HAVE READ THE FRONT PAGE. The Excel versions are much more stable than Open Office, but that's the price you pay for free software. Open Office version sometimes has convergence problems and you need to learn how to force recalculations in Open Office until you can get the numbers to look "not incorrect." In other words, don't trust Open Office until you can learn how to work it.************/

Current Version:
v2.002 BETA November 06 2008

Excel 2007+ with SEP
FuryDPS2.002BETAExcel07.xlsm - FileFront.com

Excel 1997-2003 with SEP
FuryDPS2.002BETAExcel97.xls - FileFront.com

Open Office
FuryDPS2.002BETAOO.ods - FileFront.com

Downlaod OpenOffice here
download: OpenOffice.org Downloads

Currently you can do most things except full arms dps or prot dps. Gearset for 70 only includes t6 and higher quality raiding gear as the focus is for WOTLK. Please post if you find any errors. I suggest playing around with it you will have fun!

Recent fixed/changes:
New releases in all three wonderful shreadsheet languages. The Excel ones are recommended obviously. The Excel sheet is conveniently automatic and looks much nicer in general. I didn't get around to learning to macro it for SEP yet, but I'll get around to doing that later becasue the migration to Excel required me to re-write everything by hand. Fortunately it came out picture perfect with no errors and matched the OO sheet down to a pin tip.

11/07 Added [Mayhem Projection Goggles]
11/07 Added 8 STR socket bonus
11/06 Added click-button SEP module for Excel Sheets.
11/06 Fixed an issue where [Blackened Naaru Sliver] could build off of special attacks, when it only truely builds from swings.
11/04 Fixed armor lookup error for chestpiece and error with the weapon mastery dropbox in excel sheets.
11/03 Fixed expertise error in 07 and 97 excel sheets.
11/03 Changed Bloodthirst cooldown to 5 seconds and freed up Whirlwind frequency respectively.
11/03 Changed Deep Wounds to correctly work off of off-hand strikes
11/03 Changed TG hit penalty to 5%
11/03 Fixed some double-dipping errors leading to Heroic strike representation in percentage of damage done.
11/03 Fixed some errors all around that I noticed, only several small ones.
10/20 Instated a white crit cap. Yeah, you definately get there now even with good gear.
10/20 Fixed miscellaneous calculation errors.
10/20 (removed) BT/WW/BS rotation automatically switches itself when BT>WW strength. Fixed rotation calculations.
10/14 Fixed an issue where Bloodthirst was not receiving certian bonus damage from sharp stones, raid synergy, and deathwish.

Korash · 03/17/08, 7:04 AM

I'd say landsoul just did a typo, considering that he has the Warglaives enchanted with Executioner MH and Mongoose OH.
But I like the Spreadsheet a lot. Easy to use, most important Items are in. Keep up the good work.

Gruntle · 03/17/08, 7:14 AM

Yeah, seems like a typo to me too, I must admit that this spreadsheet is now the one I'm using (I gave up on my own OO spreadsheet in favor of this). Simple to use, works in OpenOffice and is more stable than the other sheets (in my opinion). Great work landsoul!

Tauftamir · 03/17/08, 8:27 AM

Originally Posted by landsoul

Do hidden cooldowns on trinkets or procs start after the buff finishes or when the buff starts?

The cooldown begins when the buff starts. You should be able to find evidence of this in the DST Thread, if memory serves.

landsoul · 03/17/08, 9:25 AM

If only the DST threat was more than just mindless speculation... what I really would love to see is a screenshot of a combat log with the buff coming up 10-15 seconds after it faded. that would be hot.

If thats true, then uptimes on hidden cooldown items will start going up and numbers will shift and maybe bump around certain SEP rankings with these items equipped.

landsoul · 03/17/08, 9:39 AM

On topic of BS hammers: from [Warrior] DPS Spreadsheet 2.3 and beyond

Originally Posted by Shha

As for BS 1h hammers:

- They dont have hidden cooldown and i said in posts above. I did personally had countless occurances of the buff overlapping each other.

- Im currently running several hour long test in blasted lands:

Conditions:

- Mob attacked from the front - noone to tank it . My parry is at around 31%, something to take into account.
- Tanking gear (need to do something else lol).
- UM and combatlogging.
- No flurry or other haste procs.
- No instants - just autoattack.

So far the uptime for it oscilates around 21%, and has not changed for few hours. this suggests around 1.2 PPM with following problems:

Overlapping procs can lower a bit the result (although not much).
Parry speeds up weapon speed considerably. Out of every 10 swings 3 are hasted (if i recall the haste averages to making your weapon speed 0.4 of normal - im not 100% sure on parry mechanics, someone can probably correct me). If so the 10 swings take only 8.2 time of normal one, so we can say the proc shows 1.22 times more. Taking that into account, Id say the PPM is just 1.

Conclusion - current 16.6% uptime model in your spreadsheet is too low. How much its debatable. However even without haste effects uptime is at the 16.6%. That doesnt count instants, or haste effects.

Speculation. From my other tests, it seems that the proc follows rules of noncooldowned procs like executioner/mongoose aka:

- Extra procs from instants.
- Haste/Flurry doesnt affect proc rate - its calculated from base weapon speed.
- Proc can override itself.

Probably similiar modelling to mongoose/executioner can be applied, however the proc duration is 10 sec as opposed to 15, so the uptime will be lower.

Interesting values - according to combat log

Haste buffs =601
Executioner buffs = 463

That doesnt take into account refreshing buffs, so i think higher number for haste, is simply because executioner overwrites itself a lot more due to longer buff duration.

There's a lot of conditions there that seem funky. That and also the whole thing of measuring PPM of something that procs a good amount of haste throws the whole thing off too. I'm biased towards things being either 1.0 or 1.5 ppm, but I guess I can remove the hidden CD. That being said I will probably have to bump it down to 1.0 instead of 1.5 ppm after that to make the uptime at all reasonable.

Possessed · 03/17/08, 10:21 AM

First up, nice job on the spreadsheet thus far

.

With a quick play around on v1.101 I thought of two suggestions:

-Items with procs dont have the DPS gained from the proc added to DPS gained from the passive stats (on the Gear Display sheet). EG: DST shows as ~19DPS, is it possible to add the DPS from the proc too?

-On the Gear sheet, perhaps underneath the section for unbuffed stats, there could be a buffed stats row too, just for a quicker reference rather than switching to the output sheet.

Also just wondering if using ctrl-shift-y (no biggy really, i just occassionally forget :P) is a permanent thing i'll have to remember to do because of a limitation in the program, or is a workaround in the works?

Looking forward to the execute stuff being implemented

Shha · 03/17/08, 12:29 PM

Well reasonable value after everything is considered should be around 35%, which is what i see in raids. Given how Executioner ends up being 54% uptime with your sheet using 1 PPM and 15 sec duration, i guess 1 PPM +10 sec duration would do it.

As for the SEP values. Trying to play around and test it, but honestly , its pretty strange that your spreadsheet and other 2 differ so much here. Im trying to play around with different values before making a verdict, but its fishy (especially that when i set my crit rate near 0, the value of crit is lower then with normal gear, instead of higher which doesnt seem to make sense at all).

Machinator · 03/17/08, 3:31 PM

-Still cant put executioner on OH.
-I dont understand how you figure out rage/sec. I cant find anything that looks like a rage formula and the rage/sec cell doesnt seem to reference anything that has the information you would need, like weapon speed, crit bonus, ect. It just looks like you multiply white dps by a constant which doesnt really make sense.

-"Wicked Edge of the Plains" should be "Wicked Edge of the Planes"
-The OH fury should have a red socket with a 4 AP socket bonus, sheet shows no sockets.
-Is there anyway to detect the proper Gem bonus? Gems/bonus dont go away when you switch to an item with no sockets.

Edit: I also linked the data showing mongoose/executioner proc rates to be more than 1 ppm in the other thread. Here it is again Link

Shha · 03/17/08, 4:08 PM

Well if thats the case (rage = dps x constant) , it would explain the STR dominance in the chart. As haste/crit increase the rage generation by more then the added dps, while str doesnt. However, I dont have enough calc sheets knowledge to see if thats whats happening.

landsoul · 03/17/08, 5:19 PM

About the Crit SEp thing when you lower it, I will analyze it when I get home from work.
I will definately change BS hammer to 1 PPM no cooldown.

On dual executioner: I do plan on putting it in, yet its not my priority at the moment. there are still a lot of things I need to fix before I do something secondary like that and for any conclusions to be made on that regard I dont want that to happen based on false information.

On: RAGE PER SECOND

A fury warrior's rage flow fully controls his second half of his DPS, his yellow attacks. To be able to determine how frequent he can use those abilities, we must arrive at an ideal RPS value.

Luckily, we already have our ideal white DPS and windfury values. All we have to do then, is to find a way to plug it into blizzard's rage generation formula, shown below for level 70.

(7.5d / 274.7 + f * WepSpd) / 2

f = 7 for MH crit, 3.5 for MH hit and OH crit, and 1.75 for OH hit

d is the damage dealt, or the damage you apply with armor taken into account. Blizzard wants us to get 1 rage for every 73.25 damage we deal plus a normalized amount based on our weapon speed and rolled hit. For example, if we were to crit with our 2.6 speed main hand for 1000 and hit with our 2.6 speed off hand for 300, we would get 22 and 6 rage.

Since we are working with infinites, we want to know rage over time, but this formula only shows the rage per hit. All I do is convert that rage per hit and multiply it by hits in MH and OH and WF per second, and combine a shit ton of terms.

RPS = .01365[WhiteDPS+WFDPS] + 21 / 8 * (1 - [%dodge] - [%misswhite] + [%crit])(1 + [%hasteAVG])(1 + .25[%FlurryUp])(1+[%AVGSpeed] + 1/3[AManage] + 3[UBWrathTP](MHWepSpd[MHWHSperSec] + OHWepSpd[OHWperSec]) + (20 + 3[ImpBR]) / 60 + ([MHWHSWFSpecperSec] + [OHWWWperSec])[%dodge][4pct4]+[RotSKprocperSec]

The proof is way too large to bother posting it at work, but I did work it out and go through it twice to make sure it was correct. I do however need to go back into it sometime and add the normalized portion of the WF hits into the formula, cause I honestly forgot when I made it. That will take some time and verification also.

The only real thing rage per second over rotation contributes to is Heroic strike, which tightens up our hits per second and adds a little bit of DPS, all while increasing our proc and flurry uptimes. One thing I might want to figure out is if spamming hamstring to increase proc uptimes is better than using rage for heroic strikes, but probably not.

Thanks for catching Wicked edge of the planes and fury. Those typos drive me nuts sometimes.
Also great idea on the buffed stats row. I will include one that lists static raid buffs, which will mostly only incerase your AP and crit or hit if you eat the food or if you have a Draenei.

I also have been doing a lot of reading about haste... well does PPM use listed weapon speed on the tooltip, or on the character sheet after haste and speed buffs?. I dont have the time or the energy to sit in F'in blasted lands and do this junk myself.

I do intend to add SEP values to procs from items into the item SEP value, but that will take some time, so just be patient! All will come in good time =)

Hozz · 03/17/08, 6:12 PM

Any chance you could work sword spec into the talent portion?

landsoul · 03/17/08, 6:27 PM

Originally Posted by Hozz

Any chance you could work sword spec into the talent portion?

Possibly yes when I can start on damage procs but not yet

WernerVonBraun · 03/17/08, 6:41 PM

Originally Posted by landsoul

1. What is proc rate or PPM of Rod of the Sun King?
2. What is the Proc Rate of Romulo's Poison Vial?
3. Does the blacksmithing tiered hammers have a hidden cooldown, what is the PPM?

1. [Rod of the Sun King] About 6 PPM, no CD. I don't think it's crucial, since it's not a very powerful proc. Maybe I'll test it properly (I would now, if the PTR was up...).
2. [Romulo's Poison Vial] 1 PPM or 1,2. Not very powerful anyway.
3. [Dragonstrike] No CD. Procrate feels like Mongoose/Executioner, so about 1 PPM.

[Madness of the Betrayer] What PPM does it have?
How do you do stuff like Tsunami/DST? Active every 45s?

landsoul · 03/17/08, 6:52 PM

Originally Posted by Machinator

-Still cant put executioner on OH.
-I dont understand how you figure out rage/sec. I cant find anything that looks like a rage formula and the rage/sec cell doesnt seem to reference anything that has the information you would need, like weapon speed, crit bonus, ect. It just looks like you multiply white dps by a constant which doesnt really make sense.

-"Wicked Edge of the Plains" should be "Wicked Edge of the Planes"
-The OH fury should have a red socket with a 4 AP socket bonus, sheet shows no sockets.
-Is there anyway to detect the proper Gem bonus? Gems/bonus dont go away when you switch to an item with no sockets.

Edit: I also linked the data showing mongoose/executioner proc rates to be more than 1 ppm in the other thread. Here it is again Link

The only convincing argument based off of blizzard's design history is the 1.33 PPM or 1 proc per 45 seconds. It seems to follow the 15s/45s methodology, meaning 15 up 30 down every 45. I guess I can give that a shot.

Also I would love to know if haste, flurry, and speed affect PPM. Is PPm - > static weapon speed -> flat% chance indeed the rule? If that would be the case then 1.33 PPM would be too high for a MH.

Determining gem bonuses is possible, but requires way too much work right now to overcome someone's laziness. I am going for full functionality first before bells and whistles.