Does pet abilities while under Eyes of the Beast transfer through MD? If so this would help with extra tricky pulls.

I'm hearing that Steady Shot toggles auto shot on or off at the end of the cast to prevent the lockups we experienced in TBC. This macro definitely looks like a fix for this problem (until bliz figures out what to do). I understand this macro up until the /click MultiBarBottomLeftButton12 command. Might I ask what is in that slot so I can have some context for what's happening at the end of the macro? This would be greatly appreciated, as I'm just trying to work out the kinks with BM dps post-3.0.2.

In that button slot i have a second macro that is

#showtooltip rabid
/cast [target=pettarget,exists] Rabid
/cast [target=pettarget,exists] rake
/cast [target=pettarget,exists] claw


As long as none of those pet skills are on auto cast it will use them in order the are listed in that second macro. The line itself that is the /click [target=pettarget,exists] MultiBarBottomLeftButton12 just makes the shot macro trigger the pet macro. Basically i needed more room then Blizzard allowed me in the first macro. The original reason for the /click part of the macro was there was a time when the old kill command would make your skills freeze up if it were in the same macro as your shot rotation. I do realize i have some redundancy in the macro checking to see if my pet has a target but i am OK with that.

But if you go back a page it has been proven that using that macro with the Auto Attack/Auot Shot disabled is not a fix to automatically selecting a new target in that it nerfs your dps in the process of fixing your targeting issues. It helps if you want to be paranoid on trash more then simply using Steady shot with Auto Attack/Auto Shot disabled spam but its not perfect and therefore a dps drop. The alternative of course is to leave Auto Attack/Auto Shot enabled and risk pulling extra mobs or breaking CC.

Edit: Explained myself a bit more.

I also redid my tests with the macro. This time however, I used 2 different speed bows and different amounts of haste. First, I did another test exactly the same with my other tests except for that I was spamming this macro:
1.21 attack speed, ~1.427 cast time steadies, Auto Attack/Auto Shot checked, no macro:
441 Steady Shots * 1.5 seconds for GCDs = 661.5 seconds
559 Auto Shots * 1.21 seconds for shot timer = 676.39 seconds
Difference in seconds: 14.89

1.21 attack speed, ~1.427 cast time steadies, Auto Attack/Auto Shot unchecked, no macro:
500 Steady Shots * 1.5 seconds for GCDs = 750 seconds
500 Auto Shots * 1.21 seconds for shot timer = 605 seconds
Difference in seconds: 145

1.21 attack speed, ~1.427 cast time steadies, Auto Shot/Auto Attack unchecked, using above macro:
454 Steady Shots * 1.5 seconds for GCDs = 681 seconds
546 Auto Shots * 1.21 seconds for shot timer = 660.66 seconds
Difference in seconds: 20.34

2.5 attack speed, 1.67 cast time steadies, Auto Shot/Auto Attack checked, no macro:
599 Steady Shots * 1.67 = 1000.33
401 Auto Shots * 2.5 = 1002.5
Difference in seconds: 2.17

2.5 attack speed, 1.67 cast time steadies, Auto Shot/Auto Attack unchecked, no macro:
622 Steady Shots * 1.67 = 1038.74
378 Auto Shots * 2.5 = 945
Difference in seconds: 93.74

2.5 attack speed, 1.67 cast time steadies, Auto Shot/Auto Attack unchecked, using above macro:
603 Steady Shots * 1.67 = 1007.01
397 Auto Shots * 2.5 = 992.5
Difference in seconds: 14.51

It appears that using the macro greatly helps in recovering the lost shots, but it doesn't quite match that amount with it checked.

Edit: Added the original test results.

2nd Edit: Better organization of results.

I was just wondering what the best choice was for trinkets giving 3 trinkets:
Madness of the Betrayer
Berserkers Call
Ashtongue Talisman of Swiftness
I use Madness and Berserkers, especially since i liked blowing Bestial Wrath and the trinket at the same time. However with being 50 pts into BM now BW no longer is on a 2 min cd so BW and trinket dont intersect. Also, we fire more Steady shots in raid in 3.0 than we did in previous version so that makes the Ashtongue Talisman of Swiftness more attractive, doesnt it?
Would madness and talisman be better or even berserkers and ashtongue?

Actually, we fire more Auto Shots than pre-patch, but our Steady Shot has been at the GCD since before patch. Amount of Steady Shots should be the same, with an increase in only Auto Shot. I'm currently using BLoodlust and Ashtongue and am loving it. Ashtongue procs alot too, more than the MH rep ring. Almost twice as much.

Madness haven't dropped yet, but is 5.16% or so ArP (last I checked with Rating Buster) worth it with the new way ArP only affects AFTER armour reducing effects like Sunder and the likes?

I have MM hunter with 2.45 weapon speed and after I turned auto attack/auto shot on i got rid of lost auto shots problem.

Yesterday i was doing dailies and noticed im losing auto shots again. Problem seems to appear if i dont start fight with sting. I guess its not because of sting but more because of auto shot starting time. Everything goes smoothly on raids where i always shoot sting first.

I'm using Berserker's and Ashtongue. After speccing into 3/3 Longevity CDs of KC, BW and trinkets match quite nice.
BW+KC+trinket+rapid at the beginning (on standard fights that don't require burst in certain moments later in fight), next BW+KC minute later and after another minute another BW+KC+trinket. Cooldowns match quite nice for this (at least for me).

If you start with a Steady Shot auto attack is not started until the end of the cast (unless you use a macro to start it right away).

Yes Selmarix, I understand that but it doesnt explain why i'm losing auto shots rest of the fight.

If i start with my macro i'm losing like 30-40% of auto shots and shooting animation look weird too. Macro is basicly steady shot only and it works fine if i start with sting.

My macro is on g15 button with 0.1s timing and I can't copy paste it here now.

Are the auto shots always right after the steady shots in your combat log when that happens?

What could happen is this:
Steady Shot starting while you are not in auto attack mode on that target sends the messages cast Steady Shot and auto attack off to the server. So he starts casting steady shot without auto shotting the target. When the client thinks auto attack is on, he does not send auto attack off.
Once steady shot completes casting the server switches on auto attack and sends that to the client and at the same time triggers an auto shot.
But your g15 repeatedly sends cast Steady Shot and auto attack off to the target and the auto attack off is only stopped once the client realizes that the server switched auto attack on. But messages take time to reach the target so with a 0.1s timing you reliably send a message that reaches the server after the auto attack was switched on with the result that it is switched off again until the next Steady Shot completes and back to step 1.
The result is that you only cast an auto shot right after a steady shot. When you start with a sting the client knows auto attack is on by the time of the first steady shot and therefore you never run into the problem.

Of course that is only a guess but it would fit the observed behavior.

Farming Strath approx 30 times over the past 4-5 days, I often saw growl with a 13 sec (maybe longer) cooldown on my Gorilla which I found really strange.

Growl share a cooldown with cower, so if you use cower (prolly autocast bug) growl will start a 20 sec cooldown.

I have been doing a bit of testing myself to come up with a solution to auto acquiring secondary targets and dropping Auto Shots (still haven't encountered the dropped Steady Shot bug).
Some of the variables I've looked at include:
-Improved Aspect of the Hawk and Dragonspine Trophy haste procs
-Latency (even forcing network loads via torrenting at the same time)
-/stopattack and /stopmacro command functions
-Manual button pressing, button spamming, and mousewheel spamming
-Mob death as close as I could coordinate to button pressing
-Tab targeting and reacquisition of targets

My solution comes down to this...

Turning off the following options (not checked):

[_] Auto Attack/Auto Shot
[_] Stop Auto Attack


Pet bar has:

Cower (Autocast OFF)
Smack (Autocast ON)
Thunderstomp (Autocast ON)
Growl (Autocast ON)


And using the macro below (mine is universal for Ferocity pet or Gorilla):

#showtooltip Steady Shot
/cast !Auto Shot
/cast Steady Shot
/cast [target=pettarget, exists, harm] Rabid
/cast [target=pettarget, exists, harm] Thunderstomp


Observing Quartz both the Auto Shot and Steady Shot timers were independently fluent and uninterrupted.
WWS and Recount show more Auto Shots fired than Steady shots not only because of the shorter cast time, but also with the haste effects pushing the Auto Shot speed below the GCD.
______________________________________

On another note, anyone know the reasoning behind the ridiculous threat generation from Glyph of Mend Pet?
From my testing, every 1.5 seconds it generates 10,000 threat split between the number of mobs in combat, so long as the pet is in combat (otherwise it generates no threat). Therefore on a single target I can send my pet in and spam Mend Pet every 1.5 second GCD and generate 6666.66, or even half that on two mobs which is pretty nice. I have discovered that it isn't attributed to the gain in Happiness. Mend Pet (rank 1) generates only a few hundred threat per activation, yet still restores the same 20 Happiness each time.

The behavior has not changed. The new "server-side macros" feature only stores the macros on the server for download by the client upon login. The client uploads a copy of your macros/settings to the server when you make a change or when you log in the for the first time in 3.02; the client in turn downloads the macros/settings from the server and (over)writes it to your WTF folder when you log back in.

Incidentally, the upload/download feature is bugged in 3.02. If you make macro changes to more than one toon in a single session, the client will only upload changes for the first toon. This bug is fixed in 3.03.

Wait... MD works, if only partially, with Volley? A massive Volley MD at MH could prove to be just enough to keep the tanks free of chainpulling casters that just can't help themselves and really want to get that tanking feeling. I thought that Volley didn't work at all.

Its been that way all along, i remember md-exposivetrapping on a lot of ae pulls before 3.0 went live (it was the sole reason i had it bound in the first place!), basically it works on all the mobs because the server has no way to distinguish between who gets "the first three charges" and will md anything to whoever you wish assuming the hits are from the same ability (same tick in the case of a volley). It will however eat all the charges, same behavior can be seen with multishot, volley or whatever else you might want to try. Consequently it is possible to use two of the charges on autoshots or something and then use the remaining charge to md one tick of a volley etc and still get the same benefit as if you had md'ed the tick with 3 charges left.

The windfury totem change has certainly made items like shivering felspine, cloak of fiends, hard khorium band, clutch of demise and blackened naaru silver very powerful for MM spec at least in the spreadsheet. I guess t7 doesn't look that bad for two out of three specs.

A few questions in regards to the new patch (3.03) for the MM hunters out there:

With the windfury nerf to hunters, is haste now a crucial stat? Meaning Haste > Armor Pen?

Also, with the changes to barrage and other talents, is Aimed shot a part of our rotation now?

If aimed shot is now a must for our rotation, should i spec something like this

Thanks a lot in advance!

General rule of thumb for hunters: Hit until capped, Haste until Steady is at 1.5s, then the normal assortment of stats: i.e. a balance of Agility, Intellect, AP, Crit, ArPen, Haste.

The math is making my head spin. How much haste rating are we looking at to get SS to 1.5?

16% + Quiver should be enough. With the Wft you had the 16% and this was exact the amount needed to push the Steadycasttime to 1,496sec.