Noted, sorry for the bump.
But I did check the bug list and couldn't see it on there, infact I still can't... (but maybe I'm just being blind?)
What the...?
I'm certain I added it, but I can't see it any more.
I also don't see another minor edit I did yesterday, but I do remember the forums were behaving very slowly, the two might be related?
Anyway, it's added now (feel free to verify), sorry if I sounded somewhat aggressive.
Look, Lactose, we'd rather you didn't eradicate the whole human race.
- Sam & Max
I'm going to sound like a tool here, but here it goes.
I do not have Microsoft Office and I'm very interested in checking our your spreadsheet to help me work on dps and see where I can fix things. Is there a freeware app that can let me work through your sheet or is it basically Office only?
Also add Elixir of Demonslaying to figure dps for sunwell bosses like Brutallus
This has been covered several times in several different threads. Unless you're meleeing Brutallus, Elixir of Demonslaying does nothing for you (and as long as I've raided it never has).
Originally Posted by Makata
There should be an option for Strength of Earth Totem for the hunters buffs, since pets get a portion of that strength.
If you mean having SoE on the hunter somehow buffs the pet, no, I'm fairly certain only the hunter's RAP and stamina buff the pet, not his strength or melee AP. And I think the pet portion of the buff's page does allow SoE, just the hunter portion does not.
Originally Posted by Makata
Finally Imp. Hunters Marks doesnt seem to be adding the melee ap in the debuffs section. Or i might just be retarded.
Speccing in and out of Imp Mark changes my DPS (or at least it did in January, presumably it still does), so I think it's being calculated into your pet's effective AP. If you don't have Imp Mark, setting it on the debuffs tab doesn't change your pet's effective AP?
I'm going to sound like a tool here, but here it goes.
I do not have Microsoft Office and I'm very interested in checking our your spreadsheet to help me work on dps and see where I can fix things. Is there a freeware app that can let me work through your sheet or is it basically Office only?
There's a version that works with Open Office, a freeware office suite that you can download. Not all the functions will work, but most will.
Great spreadsheet for Hunter DPS calculations. Thank you for your time into this.
On the "GEAR" tab, "META SOCKET";
On the Relentless Earthstorm Diamond, it doesn't show the +3% to Crit that I can see. Even next to the description, it only shows the +12 AGI.
The Relentless Earthstorm Diamond is not +3% to Crit, read it more carefully and it says +3% increased critical strike damage, so your crits are doing 3% more damage. If you check the calculations tab and look under the Critical Hit Damage box you will see the calculation included there.
Is there any plan to model [Righteous Weapon Coating] in the spreadsheet? Do we have any data on the proc-rates on these yet? I know only a few realms have them available, but more and more are getting it every day. If they have independent internal cooldowns on dual wielding, would this possibly make dual [Dagger of Bad Mojo] or [Shiv of Exsanguination] better than [Shivering Felspine]?
Didn't see this in the bug list, so posting here:
When I increase my crit rate from items, my pet dps doesn't change, even though since I crit more it should be regaining more focus.
My current understanding is that haste effects reduce your chance to proc in order to maintain the same ppm from autos -- however, this reduction also carries over to any specials/instants you use while under haste. That means when Quick Shots procs it makes it less likely that DST (or whatever) will proc off any specials you use while under the effects, reducing your total number of procs (though the procs from autos remains constant).
To be mostly correct you could probably calculate the ppm for each of the different shot rotation tabs since they're all under different amounts of haste and then use the uptime % you already have to come to a weighted average proc %. I'm not sure how far off that would be, though -- obviously your shots fired in the 10% of the time you have DST and Quick Shots both active is going to be more than 10% of your total shots fired.
Ok, based on all that, the model reduces to a 20% uptime for the DST, in all cases. Here is my math:
Dragonspine Trophy, Take 2
Normal Auto Shot Speed 2.03
Proc per Minute Rate 1
% Chance per Auto Shot 3.38%
% Chance per Special Shot 3.38%
Total Shot Frequency 1.01
Shots to Proc 29.57
Time to Proc 30.00
Cooldown 20
Proc Duration 10
Uptime for Normal Speed 20.00%
Quick Shots Shot Speed 1.76
% Chance per Shot 2.94%
Total Shot Frequency 0.88
Shots to Proc 34.01
Time to Proc 30.00
Uptime for Quick Shots 20.00%
Now, I don't have a DST to check, but does 20% uptime seem reasonable? I think most of the equations I use are self-explanatory, but I can provide details if needed. If you introduce latency into the equation the uptime goes down. Using the same rotation, but adding 500ms of latency in a /castsequence macro yields a 19.66% uptime.
Using a 3:2 rotation with a slower weapon can increase the uptime, as you take more advantage of your specials. A 3.0s weapon using 3:2 and little latency gets 21.36% uptime in normal shots, 20% in quick shots (as a 1:1.)
I'd like to release a new spreadsheet before I'm out of town next week. Any peer review of this model is appreciated. Adding in Quick Shots to the mix is fairly trivial.
Ok, based on all that, the model reduces to a 20% uptime for the DST, in all cases. Here is my math:
I'm pretty sure that's incorrect.
Special attacks use the unhasted weapon speed to determine proc chance, not the hasted speed.
With a PPM of 1, and a 2.8 weapon speed, you'd see the following:
Dragonspine Trophy, Take 2
Normal Auto Shot Speed 2.03
Proc per Minute Rate 1
% Chance per Auto Shot 3.38%
% Chance per Special Shot 4.67% //Changed
Total Shot Frequency 1.01
Shots to Proc 29.57
Time to Proc 30.00
Cooldown 20
Proc Duration 10
Uptime for Normal Speed 20.00%
Quick Shots Shot Speed 1.76
% Chance per Auto Shot 2.94% //Chance per AUTO shot
% Chance per Special Shot 4.67% //Added
Total Shot Frequency 0.88
Shots to Proc 34.01
Time to Proc 30.00
Uptime for Quick Shots 20.00%
I only changed the proc chance stuff (bolded and commented), so you'll have update the rest of the values based on that.
Look, Lactose, we'd rather you didn't eradicate the whole human race.
- Sam & Max
Now, I don't have a DST to check, but does 20% uptime seem reasonable? I think most of the equations I use are self-explanatory, but I can provide details if needed. If you introduce latency into the equation the uptime goes down. Using the same rotation, but adding 500ms of latency in a /castsequence macro yields a 19.66% uptime.
The post you were quoting had misread the thread, as Lactose said, so I don't think you can get away with a "Total Shot Frequency" method - you'd need one shot frequency for autos, and one for specials, each with different proc chances.
20% uptime doesn't seem right. I was doing some log parsing at http://elitistjerks.com/708890-post3395.html, and had 56% uptime during Nalorakk, and 39% uptime on Halazzi. Both are short fights though, so the variance is large.
If anyone has a larger sample though (say a night of brutallus attempts, going all out every attempt to keep the shot frequency representative) it would be nice to run through the parser to see what kind of values to expect the model to come up with.
Actually, I'll try to get a shadowpriest to come with me and nuke Dr. Boom for an hour, that would remove RF and Heroism's effects on the logs since the spreadsheet model probably isn't factoring those in.
The post you were quoting had misread the thread, as Lactose said, so I don't think you can get away with a "Total Shot Frequency" method - you'd need one shot frequency for autos, and one for specials, each with different proc chances.
20% uptime doesn't seem right. I was doing some log parsing at http://elitistjerks.com/708890-post3395.html, and had 56% uptime during Nalorakk, and 39% uptime on Halazzi. Both are short fights though, so the variance is large.
If anyone has a larger sample though (say a night of brutallus attempts, going all out every attempt to keep the shot frequency representative) it would be nice to run through the parser to see what kind of values to expect the model to come up with.
Actually, I'll try to get a shadowpriest to come with me and nuke Dr. Boom for an hour, that would remove RF and Heroism's effects on the logs since the spreadsheet model probably isn't factoring those in.
With a 10 second duration and a 20 second cool down, how is a 50%+ uptime possible?
I'm working through amortizing the chance per shot, based on the ratios of Autos to Specials. Not sure it will be 100% accurate, but it should suffice.
Last edited by Cheeky : 04/12/08 at 4:38 PM.
Reason: Spelling
the portion of the parser (linked in the procs thread) that measures uptime is the simplest part though, just summing together the times between aura application and aura removal, I'll poke around the logs to see if they match the summary.
the portion of the parser (linked in the procs thread) that measures uptime is the simplest part though, just summing together the times between aura application and aura removal, I'll poke around the logs to see if they match the summary.
All right, I found out what the problem was. I think Tunah originally wrote the script to parse logs from his own solo testing of procs, since while it does check actor IDs to make sure it's only counting one person's attacks, it doesn't do the same for counting procs - since I was parsing logs where multiple people had DSTs, it was recording both my DST and the rogue's DST procs.
With the parser changed to only count my own procs, the numbers work out to:
The reason I've listed two uptimes for each is because the script discards the last proc duration from the calculation. I'm not entirely sure why. The Uptime2 figure uses the full uptime, which gives a result closer to manually going through the log, adding up the uptime and dividing by the time between first and last shots.
I uploaded my hack of the original script at Procalyzer for non-personal logs [ruby] [wow] [procs] if anyone else wants to run some logs through it - just change the line near the bottom to reflect the buff you want to track for the person who recorded the log (you may want to change the filter too if the proc only occurs on specific types of attacks (e.g. Ashtongue/Quick Shots)).
I'm pretty sure that's incorrect.
Special attacks use the unhasted weapon speed to determine proc chance, not the hasted speed.
With a PPM of 1, and a 2.8 weapon speed, you'd see the following:
Dragonspine Trophy, Take 2
Normal Auto Shot Speed 2.03
Proc per Minute Rate 1
% Chance per Auto Shot 3.38%
% Chance per Special Shot 4.67% //Changed
Total Shot Frequency 1.01
Shots to Proc 29.57
Time to Proc 30.00
Cooldown 20
Proc Duration 10
Uptime for Normal Speed 20.00%
Quick Shots Shot Speed 1.76
% Chance per Auto Shot 2.94% //Chance per AUTO shot
% Chance per Special Shot 4.67% //Added
Total Shot Frequency 0.88
Shots to Proc 34.01
Time to Proc 30.00
Uptime for Quick Shots 20.00%
I only changed the proc chance stuff (bolded and commented), so you'll have update the rest of the values based on that.
Ok, carrying that through:
Base Weapon Speed 2.8
Normal Auto Shot Speed 2.03
Proc per Minute Rate 1
% Chance per Auto Shot 3.38%
% Chance per Special Shot 4.67%
Auto Shot Frequency 2.03
Special Shot Frequency 2.03
Auto Shots to Proc 29.57
Special Shots to Proc 21.43
Time for Auto 60.00
Time for Steady 43.48
Weighted Delay 25.21
Auto Shots to Proc 6.38
Cooldown 20
Proc Duration 10
Uptime for Normal Speed 22.12%
To compute the weighted delay, I combined them as 1/((1/Auto Time) + (1/Special Time)), sort of like resisters in parallel. Not sure if that's accurate, it just felt right, and I've been drinking too much to think clearly.
Last edited by Cheeky : 04/13/08 at 11:03 AM.
Reason: Drunken grammar is bad
Change Log:
- Armory scraping for Gear now correctly pulls most enchants too. Thanks to Drakier of Uther for providing the framework and the current set of supported enchants.
- Corrected some item stats (Band of Ruinous Delight, Hauberk of the Warbringer, Tunic of the Ranger Lord).
- Corrected some item names (Scale Leggings of the Skirmisher).
- Added some new items (Bracers of the Forest Stalker, Figurine - Shadowsong Panther, Cloak of the Coming Night, Sunrage Treads, Stalker's Chain Armor, Stalker's Chain Helm, Stalker's Chain Leggings, Stalker's Chain Spaulders, Stalker's Chain Gauntlets, Assassin's Alchemist Stone, Leggings of the Betrayed, Band of Celerity).
- Modeled the Shattered Sun Pendant of Might similar to other, similar trinkets (45 second internal cool down, 10% chance on hit.)
- Allow for selection of Aldor/Scryer factions (only applies to Shattered Sun Pendant of Might) on the 'Settings and Results' tab.
I'll be out of town next week on business. Please send all bug reports to Lactose.
Next up:
Gear sorting based on DPS (starting to put infrastructure in place)
Better modeling for PPM-based items
Better model for Scryer [Shattered Sun Pendant of Might] proc, once we have more data.
Various bug fixes (like auto calculation of stat->DPS changes on gear updates.)
About halfway through the log I switched from a Twinblade to a Silithid Claw/Brutality Blade combo. Procs never overlapped and seemed to share the ICD when using two weapons. ICD was 45 seconds and a rather high proc rate. Altogether it's a 66AP equivalent for hunters.
I've downloaded this sheet a couple of months ago and have used it to improve my hunter. I have, after more than 2 years of being an MM build hunter, chosen to re-spec to BM due to what I got from this sheet. Anyway, after several versions of the worksheet, I'm tired of being unable to load my profile from the armory. I've always gotten the error message 'A connection to the server could not be established'. I didn't mind the first couple of times loading my gear manually, t'was fun actually since I was looking at the other gear I could use, but doing it after every version change is tiring.
Is there anything I have to set so I can get the Load Gear from Armory button to work for me?