From reading the SV thread I have to ask; is the shot queueing enabled on the website? we shouldn't have latency impacting SS or CoS as we can queue our shots now - this has an effect on haste valuation - leading to haste inflation with higher latencies.

You can check this yourself.

If you do not know, if you select the debug Settings option, you get a full list of the shot simulation and timing. You can also change your latency numbers on it too.

Queueing shots is not new. I've always been able to do it.

I don't have any special support for shot queueing. Is there something I should do to handle it differently other than just letting users set whatever latency they want to emulate? (which is already supported)

It pleases me to read this. It worried me that I didn't see a lot of non-heroic raiding hunters making use of 4 set. As it stands I'm top dps in my guild and my performance has always been rather good, but it worried me deeply that I might be "missing" something.

In response to the shot queuing: would setting latency to 0 be too drastic?

With 4.0.1 came the spell or ability queuing. Basically, any spell (including shots) with a casttime greater than the GCD can be precast while still casting so there is 0 gap between ending cast and beginning the next one. This is new and accepted serverside and clientside. What Dch48 and others have been able to do is to start casting at a time when latency would delay the command to the serve rlong enough to be counted as coming in after the cast end (quartz latency incorporation for instance).
What it should be is that anytime a shot is cast aftera casttime shot, 0 latency (it seems from the SV discussion that latency affects time between shots) as long as the casttime is greater than 1 second. Whether people do set the spell queue correctly is, in my opinion, a matter between themselves and the game client, just like clicking, keyboard turning and other specific ways of doing things shouldn't impact the theorycrafting.

Setting the latency to 800ms (absurdly high to get a clear effect) I see the following a ways into the fight;
I have edited out the irrelevant info here.
The second Cobra Shot should, with spell queue enabled, start casting at 75.157 due to being queued while it was still casting (between 74.8 and 75.157).

Edit: adding reply to this here.
Yes, because the shot queueing only works after the GCD, so any shot following an instant will still be delayed by latency.

KergeKacsa can you be more specific about what you're looking to accomplish? I could add some more detailed behavior but I need a better understanding of what options you're talking about.

It would be nice if we could test that what is bigger DPS at LnL procc: (in 2 cases: at low and high focus)
ES-KC-ES-AC-ES
ES-AC-ES
ES-CS-ES-CS-ES
ES-ES-ES

And so on.

Thx

I've just added support for the latest batch of 4.0.6 changes announced based on what I see listed on MMO Champion. Be sure to enable PTR support under settings if you want to see the estimated effects of the changes.

As I see, you didn't fixed the Hunting Party vs. Focus-regen bug.
The fix isn't in the notes, but here: MMO-Champion BlueTracker

I ran the with and without PTR changes for both MM and SV for my character, and here are the results:

MM

Total change was about a 4% increase from 20029 DPS to 20819 DPS (+789). This is nothing big, but still a nice increase.

The total change breaks down as the following for my character:
CS: 12.41% increase
KS: 21.41% increase
AI: 35.76% increase (too bad we do not do more of these)
PS: 8.68% increase (from increased CS and AI damage)

These changes do not affect how MM hunters perform their rotation much beyond needing to reevaluate the KS vs CS glyph debate.

SV

Total change was about a 10% decrease from 23065 DPS to 20745 DPS (-2320), such that MM now does about 74 more damage despite changing from a ferocity pet for MM to a cunning pet for SV. This makes the two specs pretty even in the ideal fight with SV probably still being favored with its more forgiving rotation.

The total change breaks down as the following for my character:
Agi: -4.36% (-320)
AP: -3.99% (-703)
Crit: -2.64% (-0.99% crit)
SrS: -3.43% (with ISrS now does a little more damage than ES)
ES: -27.48%
KS: +17.08% (at least it got buffed - its damage is almost as much as ES now)
BA: -8.08% (does significantly more damage than ES now)
AS: -3.28%
CoS: -3.12%
Auto: -3.28%
ISrS: -3.47%
Bite: -2.69%
WB: - 4.21%
Pet melee: -4.03%

If this holds true, it has impacts on SV priorities since ES is no longer the highest damage shot. BA far exceeds it on targets on which the full effect lasts, and SrS beats it as well).

I've just added support for a few more patch changes which weren't in the MMO post but are in the notes:
- MM mastery buffed by approximately 17% (I'm guessing approximately means the new amount is 2.1% and not the 2.106% that we'd get from applying 17% to the existing value)
- PvP 4pc bonus now gives 10% focus regen bonus instead of 5%
- Synapse Springs now proc agility (I'm assuming the same amount as for the int version)

There's also a note in the patch notes about them adding sockets to some epic crafted items, but until I see the changed items I won't know how to add proper support for this (and I'm not sure I can support socket changes only for PTR easily).

I've been thinking a bit, and wondering, would it be possible to add [Beast-tamer's Shoulders] to the analyzer? I'm wondering if it could actually (still) be an upgrade for BM at certain gear points.

In my shot prio I have Explosive before Black Arrow in PTR mode, but it didn't work.

Explosive shot comes off CD, but BA is shot first.

Is there a bug, or I misunderstand something?

KergeKacsa, have you checked the "Don't save focus for Lock and Load trigger (Black Arrow or trap) if it comes off cooldown" box? I would have to doublecheck the code, but I think when the saving focus is enabled for this, it handles that before dealing with the higher priority shots to prevent tapping out on focus before the shot is fired. If that doesn't explain it, send me your saved setting link in a PM and I'll take a closer look.

Yepp, "Don't save focus for Lock and Load trigger (Black Arrow or trap) if it comes off cooldown" was off.
But there was a "Save Focus For Explosive Shot" setted up too, and since Explosive Shot is higher on the prio list, it would be correct if it would save for Explosive Shot (so do not shot BA, AS), and after if save some focus for BA (do not shot AS).

There is 2 save-focus settings, so it should follow the prio-list between them.

I'm attempting to compile a list of random enchant codes for the epic random enchant items so I can properly support them on my site (I'm going to continue to leave blues to be handled by custom stats as people shouldn't be wearing them all that long). I'd appreciate some help with armory links to track these down. If you are wearing one of these missing items in your armory or know someone who is, please PM me the link. Note that I actually did check one person's armory with Mistral Circle but it seemed to be giving bugged codes so I'm hoping someone else's will be more useful.

BTW for those curious about where the codes are coming from, it's the r= part of the URL for the tooltip that you can find if you look in the HTML.

I'm missing the following:

Star Chaser Legguards (heroic) - 372
of the Stormblast - 238 hit, 238 cri, 345 agi, 578 sta
of the Windflurry - 238 cri, 238 has, 345 agi, 578 sta
of the Windstorm - 238 cri, 238 mas, 345 agi, 578 sta
of the Zephyr - 238 has, 238 mas, 345 agi, 578 sta

I already have the following:

Mistral Circle (regular) - 359 (not sure why regular and heroic have the same codes and if that's working properly)
of the Stormblast - 126 hit, 126 cri, 190 agi, 285 sta (-133)
of the Windflurry - 126 cri, 126 has, 190 agi, 285 sta (-135)
of the Windstorm - 126 cri, 126 mas, 190 agi, 285 sta (-137)
of the Zephyr - 126 has, 126 mas, 190 agi, 285 sta (-136)

Mistral Circle (heroic) - 372
of the Stormblast - 143 hit, 143 cri, 214 agi, 321 sta (-133)
of the Windflurry - 143 cri, 143 has, 214 agi, 321 sta (-135)
of the Windstorm - 143 cri, 143 mas, 214 agi, 321 sta (-137)
of the Zephyr - 143 has, 143 mas, 214 agi, 321 sta (-136)

Star Chaser Belt (regular) - 359
of the Stormblast - 160 hit, 160 cri, 232 agi, 380 sta (-216)
of the Windflurry - 160 cri, 160 has, 232 agi, 380 sta (-217)
of the Windstorm - 160 cri, 160 mas, 232 agi, 380 sta (-218)
of the Zephyr - 160 has, 160 mas, 232 agi, 380 sta (-219)

Star Chaser Belt (heroic) - 372
of the Stormblast - 180 hit, 180 cri, 266 agi, 429 sta (-233)
of the Windflurry - 180 cri, 180 has, 266 agi, 429 sta (-234)
of the Windstorm - 180 cri, 180 mas, 266 agi, 429 sta (-235)
of the Zephyr - 180 has, 180 mas, 266 agi, 429 sta (-236)

Star Chaser Legguards (regular) - 359
of the Stormblast - 208 hit, 208 cri, 301 agi, 511 sta (-195)
of the Windflurry - 208 cri, 208 has, 301 agi, 511 sta (-196)
of the Windstorm - 208 cri, 208 mas, 301 agi, 511 sta (-197)
of the Zephyr - 208 has, 208 mas, 301 agi, 511 sta (-198)

The armory seems to be buggy on this random enchant items. The "Star Chaser Belt of the Stormblast" (359) has 160 hit and 160 crit. Agility, stamina and socketbonus are correct. The "Star Chaser Legguards of the Stormblast" (359) have 208 hit and 208 crit. The code is "-195". I've logged out with them equipped. You may check the code, if you want. Every random enchant item i've lootet so far has two random stats plus stamina and agi.

I've incorporated the latest round of PTR changes on the site. Note that I'm unclear on how some work (whether the 50% buff to chimera and arcane also affect weapon damage or how it was implemented, and if the black arrow nerf affects RAP as well as base damage). For now I have chimera and arcane buffs affecting all 3 portions of the shot damage calculation and black arrow only affecting base damage, I'll update when I have more info.

Initial review shows all 3 specs pretty close, things are looking more promising.

I'll look into the beast tamer's shoulders when I have some more time. Thanks for the data on the random enchants guys!

I'm not sure if you've thought of this earlier, but a mobile-friendly layout of the page would be great. Unlike other tools/sims which aren't really usable on mobiles either because of the UI or the complexity, FD is pretty straightforward to use on mobiles. It's just that the layout forces a lot of scrolling to see anything.

Definitely gear effects the numbers, especially if you have to reforge a lot of stats for hit.

Another item is using the same pet as adverse affects in the comparison. A ferocity pet with 2/2 WH does the best DPS for BM and MM (with Frenzy spec) from my observations, but that is not true for SV. Since SV does not have as much pet focus regen (1 point in BD at most), a Cunning pet with 2/2 WH is much better for it than a Ferocity pet with 2/2 WH or 1 WH/1 SA.

In addition, when haste effects are used is important too.

For my character, with balanced MM/SV gear, I get:

MM--- 22576 dps (Ferocity pet with 2/2 WH)
BM---22235 dps (Ferocity pet with 2/2 WH and 2/2 SA)
SV--- 21775 dps (Cunning pet with 2/2 WH)

Notes:
- For MM, nothing has changed concerning the CA phase, despite the buff to AS. The non-AS rotation still wins out during the CA phase as long as you have a SS cast time hasted near 1s. This is not only due to SS damage with the extra 60% crit chance and PS damage still being slightly greater than AS damage during this phase but also due to more MMM procs for additional AI damage. As before, if you have a slow SS cast speed, you want to use the standard MM rotation during the CA phase.
- For MM, the changes seem to prefer the CS glyph over the KS glyph, despite the boost to KS damage; however, the numbers are still currently close enough where it can be a preferrential decision.
- For BM, the standard rotation with AS is best during the CA phase, even with a fully hasted CoS. Although the average hasted CoS damage is slightly greater than the AS damage over that phase, the additional pet damage from higher WH uptime due to the Sic'Em procs from AS trumps the situation.
- For SV, the standard rotation is much better during the CA phase than the one without AS. Not only is this because of the WH uptime being more important than a little higher CoS damage, but it is also because with the 757 recommended haste rating for SV, the CoS cast does not get anywhere near a 1s cast since they are missing the 15% haste buffs that MM and BM have. This slower SS cast time, even when under dynamic haste effects, makes the CoS average damage lower.

As can be seen, with the current PTR numbers, all 3 hunter specs are much more comparable. However, I think that the SV nerf needs to be reduced some to bring it back into line better with the other specs, although the agi scaling may make up for that soon already.

I like the changes for the most part since it will allow me to raid with my preferred spec (MM) instead of feeling that I need to play a different spec in order to provide maximum contribution. In the same vein, I hope the SV numbers are buffed back up a bit so that the hunters who prefer SV do not feel like they have to switch to MM or BM for a general fight. For a pure DPS class, all three specs should be ideally viable with the only reason one is preferred over the other is due to specific boss mechanics for a fight favoring a utility that one ot the other spec has uniquely or is better at.

I've added explicit support for the epic random enchant items on the site. This will make the item lists a bit long but I know folks have been frustrated by having to use custom stats for them. Blue random enchant items will still require the use of custom stats as I expect anyone wearing those items is only doing so temporarily and each random enchant item is significant work to support in this fashion.

Armory import should work for the random enchant codes I already have. I'm still missing codes for the heroic Star Chaser Legguards and the regular Mistral Circle. I'm also not sure the heroic Mistral Circle codes are correct so if anyone runs into issues with that, send me an armory link. If it doesn't recognize your random enchant code it should just select the blank version of the item. Since I can't link directly to the random enchant stats for an item on wowhead (if someone knows a way, let me know), I've just set it to display stats directly for the items when it can't display a wowhead link.