Warrior DPS Calculation Spreadsheet - Page 9

Rallik · 01/20/09, 3:14 AM

Originally Posted by landsoul

There's no way that's right though, that formula would yield >60% uptime on the main hand which is way off in practice. Come to think of it, I don't remember where I got that but the dividing by 100 is what gives the conversion to percent. But I may be wrong. I'll do it this way then

1proc/72s * 3.5s/attack = .04861111 procs/attack = % chance. = p.

That's how you are supposed to do it. We were both wrong I guess, but thanks for bringing it to the light.

That's still wrong. That's the same as doing: 3.5/(60*1.2) instead of (3.5*1.2)/60 and obviously still doesn't fit the definition of PPM. If I had to guess, I'd just say the PPM is less than 1.2, or else the uptime really is 60%+. I tested on a dummy with 0 raid buffs and had ~50%. I could easily see it being over 60 with WF/higher flurry uptime/BL.

• landsoul · 01/20/09, 3:17 AM

Well if it's wrong or not what does it help if there's no data anyways and nobody knows the answer to the problem?

You'd have to make a test where you would sit there and auto attack for hours and disengage your attacks when you get a proc. Anyone willing to do that?

Rallik · 01/20/09, 3:30 AM

Originally Posted by landsoul

Well if it's wrong or not what does it help if there's no data anyways and nobody knows the answer to the problem?

Well there's no point in using a wrong formula trying to fit it to the data. Just needs further testing most likely. One of these is true:

A) The uptime really is 60%+.
B) The PPM is less than 1.2.
C) Abilities we think proc enchants don't(WW? BT? Execute?)

I can do a couple hours of autoattacking, and test to make sure every ability procs it too. Also afaik, /combatlog now will actually report refreshed buffs instead of only gains/fades, so should be no need to stop attacking ever.

• landsoul · 01/20/09, 3:37 AM

Ok then well let's get some data and fit a PPM to it. I was always under the notion that 60+% was too high.

Rallik · 01/20/09, 3:57 AM

Originally Posted by landsoul

Ok then well let's get some data and fit a PPM to it. I was always under the notion that 60+% was too high.

Yeah, 45% sounded right to me. It wasn't til I wrote a sim and kept seeing 60%+ using 1.2 PPM that I started to wonder wtf was up.

• landsoul · 01/20/09, 4:15 AM

Im sitting next to my rogue friend, has 34 procs over 1977 connects, no haste, autoattacking with a 1.4 dagger. That's a .017 chance. That's .7370 ppm. I'm beginning to get a little worried. You got any data yet? Is the data set too small?

.75 PPM gives me a 45% uptime in the main hand with that correct formula.

This makes Berserking noticably worse than Mongoose.

Shha · 01/20/09, 8:23 AM

One new feature that would be really nice, is to add a switch that would change the SEP of use effects to maximum possible (IE if you loatheb shadow, it could assume you always use it while hysteria and DW are up etc). Clickable trinkets were always weaker on sheets then passive ones, but they made it up with that sort of flexibility. The internal cooldown trinkets also can be used to great effect.

Just for example Im really in love with grim toll trinket lately. On paper its not so awesome, but in reality it procs at very predictable times (around 5 sec after greatness in "rotation". So for example on sartharion i already time it to be up for executes on 1st AND 2nd drake - in case of 1st i have heroism/dw/hysteria, making the proc insanely powerful (boosting my executes into 21k range).

While such things are hard to model, taking a look for selected buffs (heroism, hysteria), and if present , the switch would make the sheet assume they are up during trinket uptime (or half of it actually). That would put them a bit more in place - given how Grim Toll passive part (84 hit), is considerably weaker on SEP then other trinkets STR/Crit, but the proc is a lot more powerful in my opinion (especially timed for executes).

• landsoul · 01/20/09, 12:48 PM

Sounds like something you can do with the +Phoney stats box. I'll look into putting in a variable (on rage) execute strength box somewhere.

Still though comparing (double proc for time one and no proc for time 2) and (average procs over time 1 and time 2) may be interesting. I'll look into it when setting up another update.

Pogues · 01/20/09, 12:48 PM

Just a quick question, does the spreadsheet currently count in the crit reduction of 4.80% from bosses found by Vulajin found here?

• landsoul · 01/20/09, 12:50 PM

Yes. I actually rolled that in about a week after it was discovered.

Ariakis_Uther · 01/20/09, 1:55 PM

Originally Posted by NobleHelium

Nice interface changes. There's a bug with ring sockets though, when I switch a ring to Greatring of Collision it says "16" where it should say the socket color.

Also, the SEP macro seems broken on the .xls version. When I press the button I get the error "Run-time error '1004': This operation requires the merged cells to be identically sized." Clicking debug says the error occurs on the line:

Selection.PasteSpecial Paste:=xlPasteValues, Operation:=xlNone, SkipBlanks _
:=False, Transpose:=False

in the SEP() function. In addition, the error occurs when cells AM-AN on row 29 are highlighted.

I tried to find a fix for this since I'm seeing it on Excel 2003 also. The threads I found suggest not using merged cells but centering over selection instead. The other hints they provided haven't netted a working function yet.

• landsoul · 01/20/09, 2:43 PM

Right then, so probably the solution would arise from unmerging the cells being changed as a macro in excel 97 cannot determine which square the information is actually in? I'll give that a shot when I post the next update with fixes soon.

• ebs2002 · 01/20/09, 3:32 PM

Yes, if you unmerge the cells and instead center across selection, you achieve the same visual effect. You only need to do this in two places: NewDPS and SEP under the SEP calculator.

The only downside is that it makes an empty cell that appears to contain data.

If this bugs you, you can simply unmerge at the start of the macro, then merge again. I'm pretty sure you can just use Selection.Merge and Selection.Unmerge, although I haven't tried this.

Rallik · 01/20/09, 6:58 PM

Originally Posted by landsoul

Im sitting next to my rogue friend, has 34 procs over 1977 connects, no haste, autoattacking with a 1.4 dagger. That's a .017 chance. That's .7370 ppm. I'm beginning to get a little worried. You got any data yet? Is the data set too small?

.75 PPM gives me a 45% uptime in the main hand with that correct formula.

This makes Berserking noticably worse than Mongoose.

I had time to do a little bit of testing before raid today. Over 1000 landed attacks with a 3.6 speed wep/shield in OH, I saw 68 procs. That'd be 1.1333~ PPM. I'd say it's certainly reasonable for the true PPM value to be 1-1.2 and won't be anything crazy low. Later tonight I'll be able to do further testing. I'd like at least 10,000 swings. I also confirmed that WW/BT/Execute/Slam are all capable of proccing the enchant, aaand WW with Zerk in the OH is capable of proccing zerking too. Given all of this, I can only assume that the real uptime is 60%+, there's no reason it shouldn't be. It should also completely destroy Massacre in the OH given that info too.

I can only assume your friend didn't have an offhand equipped, and so was auto-attacking with his fists too and didn't remove those hits from his results. If he has a 1.4 speed dagger and is swinging at 2.0 with his fists... (1/1.4)/(1/1.4 + 1/2) = 58.8% of his swings being dagger swings, .588 * 1977 connects ~= 1163 dagger connects. 34/1163 ~= .029 * (60/1.4) = 1.25 PPM. .737 PPM just seems too low to be reasonable when I saw so much higher over 1000 attacks.

• landsoul · 01/20/09, 7:01 PM

Ah that completely slipped my mind I feel like an idiot

Rallik · 01/20/09, 7:13 PM

Oh hey, updated my post with other info ^

• landsoul · 01/20/09, 7:20 PM

Yeah definately, I think I'm ready to update again in the next hour.

Avin · 01/20/09, 9:24 PM

Very nice update with the new looks and a good and useful spreadsheet overall, thanks a lot for the work you have put into this!

Etra · 01/20/09, 11:34 PM

Definitely prefer the new color scheme, works really well.

Rallik · 01/21/09, 1:55 AM

Actually, not going to bother with more in-depth zerking PPM testing. If it works on every ability and assuming its PPM is around 1.2, it should be at like 62% uptime. I just glanced at wowmeteronline's parses for my raid today and had 77% uptime on patch, 75% uptime on loatheb, 61% uptime on raz, and 57% on thaddius, which are all pretty good near 100% dps time fights for uptime purposes. I'm pretty much convinced the 1.2 estimate is right and it really is that good.

Aurethios · 01/21/09, 4:32 AM

The "Run-time error 1004" that was reported earlier in the thread is still there.

I am really enjoying the changes to the set1 tab.

rejdakon · 01/21/09, 11:07 AM

First of all: Tremendous work with the new socket-detection! This makes the sheet almost perfect with regard functionality.

A few comments, however:

- Run-time error 1004 is still occuring when calculating SEP (Excel 2003).

- A minor thing: The standard gear set has Sword Spec 5/5. As the sheet does not calculate Sword Spec, this has no impact on DpS-calculation but is merely an issue of perfection.

- The new layout is nice. Everything is closer together and the background being not completely black makes the sheet nicer to the eyes. However, the old sheet was 1.5 MB, the new one is almost 13.5 MB. Load/save times have also increased. If this is the price of the "Steel" background or the red/black background pic on the Into-Tab, I am not quite sure that this is the way to go. Taking the Red/Black background out reduces the size by 7.4 MB. Not that it's an enormous issue, but as the sheet is out of beta now, I think its ok to talk about perfection issues.

- The text box reading "Landsoul's FURY DPS Spreadsheet Version 2.301" in the Intro-Tab is too small height-wise and cuts the last line of text (Version 2.301) in half.

Mightybeast · 01/21/09, 1:59 PM

I've found that running the SEP green button thing is much slower now thatn it was in the beta version. Also for some reason the gem in Titanium Impact Band is not showing the stat bonus and I have to add it in pheony stats

Mightybeast · 01/21/09, 2:00 PM

O silly me you updated it on the 20th. Is there a way I can use the new update without having to input all my gear again?

Pogues · 01/21/09, 2:11 PM

Landsoul, I just downloaded the new version and it is brilliant. The layout is so much better and easier to read and find what you want. The smart item set up for sockets and bonuses saved me about 3 minutes putting in my gear and trying to remember what bonus i get on my ring. Overall, i think you did a great job and really appreciate your time that you sink into this for us. The increase in time to do SEP is worth it for easier time dropping in gear. I had to get 2007 on my home PC just so I could use this without the run error, but it was worth the time "finding" 2007. Thanks for the hard work. Honestly at this point I'm so used to where the two gems I use are that I don't know how big a deal reordering the drop down is. If you did I would just recommend changing it to all +str gems in order from least to greatest and then AP gems, Crit, Hit, Exp, hybrid gems. For the most part I think most people here onlu use Crit, Str, and a couple of purples.
Anyway, great work sir and thanks!