Nope

The formula for average uptime on such a thing is 1 - (1 - procchance)^attacks
at 10%, given hitcap and 5% dodge chance, I'd expect about 9.5% of attacks to proc it, 19% at 20%
Over those 5s you make 5 * (1/1.25 + 1/(2/1.3/1.2)) = 7.9 attacks (1.25 = pet gcd, 1.3 = cobra reflexes, 1.2 = windfury) - that assumes focus cap, which is actually quite hard to hit in practice as MM given GftT's randomness, though you can get within 5% pretty easily

so at 1/2 you'd expect around 55% uptime, at 2/2 you'd expect about 81% uptime

Second point definitely adds value, not as much as the first, but it's no 5/5 hunting party :P

Obviously MM and Surv 'need' 2/2 more, but with Serpent's Swiftness and Retribution Aura it goes up and up. While I haven't specifically tested for this, I have noticed the little blinking heals, and they have been pretty constant even on dummies.
With that and Frenzy going the pet does melee at around 0.8 speed and specials every 1.25. So that's an optimal 10.25ish attacks every 5 seconds. Enough to keep Bloodthirsty at a rather constant uptime.

In any case, my argument was that 1/2 achives the main goal, and that is fast happiness, and maintainance of happiness over a long time. The heals will help against such things as AoE that is enough to overcome Mend Pet. And that is perhaps not often, but often enough. Against such things as Doomfires on Archi there is little else than have 2xT5 and plenty Resto Shamans. At least that is my experience.

Are you 100% sure cower didn't toggle itself back on? Cower has a 20 second shared cooldown with growl if it goes off and this may cause the longer cooldowns you saw.

Your first bullet point doesn't jive with your second. I'm not a regular participant on these forums, but this issue is what brought me here in the first place. Link to the post quoting my observations.

It's not Steady Shot that is interrupted, but Auto Shot under certain conditions. It appears most likely to happen when Auto Shot and Steady Shot are both close to firing. I suggest you do another timed test with the option checked/unchecked. I think you will see number of Steady Shots fired in that period will be consistent while observing a dip in Auto Shots with the box unchecked.

Try this...

Find a hunter buddy the with same auto shot speed as you (same bow, same haste, same pertinent talents.) Go to a test dummy, remember to switch off Hawk and sync your Auto Shots. Do this by having your buddy start his Auto Shot just as yours is about to fly. Now, with the Auto Attack / Auto Shoot box unchecked, you start spamming steady shot for a while. Is your shot now out of sync with your buddy's? If so, then your Auto Shot definitely got interrupted at some point.

Now sync up Auto Shots again and have your buddy spam Steady Shots, but with the box checked instead. If everything goes according to plan, your Auto Shots will remain in perfect sync.

I have not tested this since 3.0.2 was released, so it's possible it may have been fixed, but when 3.0 first came out the bug was very real.

Thanks, I had the words reversed. The second instance (enabled) was 50 steadies, 37 autos. Thanks for catching that. I corrected the post.

Last night I was 2-manning a necrotic shard area with a resto Druid and my gorilla, and at one point I clearly saw OmniCC showing at least 8 seconds left on a Growl cooldown. Unfortunately it didn't register fast enough for me to think to take a screenshot, and I didn't notice it again (so I guess it was a fluke).

I did later notice that my gorilla was generating a very low TPS on a single target (Shadow of Doom), and opened my pet spell book to find nothing wrong.

So it seems like things can get weird occasionally, but I haven't figured out anything consistent yet.

I'm going to look at some other pets over the weekend and see if there isn't anything going on with the others or if it is specific to the gorilla or other pets wtih AE abilities. Something else that I noticed last night, something that I've seen before but just never paid it much mind, is that when you use one of your own abilities, it will flash your pet's bar. It doesn't cause any GCD that I can tell. Was really tired last night trying to finish up SWP so I could have just been imagining things.

On the topic of the Gorilla pet, I have to say that I'm amazed, to an extent, as how good of a pet this thing is. Granted, I still pull aggro rather easily due to Volley critting. But the beating that this thing can take along with the AE damage is pretty nice. I'm using 2 piece T5 when I grind so it helps a lot. I can only imagine how it would work with Rhino Blood and Spirit Bond.

From using Omen and watching my pets threat, I can confirm that Mend Pet with the Minor Glyph is generating threat. And not just a little either. I was finding that when I used it, my pet would instantly generate 10k threat. However, if the pet was full Happy, it wouldn't generate the 10k and instead a lot less depending on how much was missing. So it's looking like Gaining Happiness on the pet generates about 500 threat per point of Happiness Gained. Was having a bit of fun yesterday with some of my other pets AoE Tanking just fine as long as they weren't at full happiness. Just gather the group and let the pet get some threat on each one, pop a Mend Pet and see all the mobs with 10k threat on my pet.

And why so? If i'm not useing misdirection i could controling my pet and standing right next to the tank even bevor the fight starts. From there i just have to push 2 buttons and i'm done. Unfortunately there is no one selling this glyph on my server

Tried it yesterday on the EU beta. Quartz as usual shows 1.0s Steady shots, but GCD still doesn't drop below 1.5s, at least with Rapid Fire or Quick Shots.

I've verified it by looking at the combat logs and under haste the average time between damage from steady shots on the target dummies was a bit over 1.5s, as expected.

So GCD is not reduced by haste effects on beta.

i did some test with this new macro but my stupid gorilla seems not able to read the macro :\

#showtooltip Steady Shot
/stopmacro [target=target,dead]
/stopmacro [target=target,noexists]
/cast [harm,nodead] Steady Shot
/petattack [target=pettarget, noexists]
/click BT4Button73Secure
/script UIErrorsFrame:Clear()

i haven't done tests about the number of SS fired but that's not the main problem atm

BT4Button73Secure:

#showtooltip Thunderstomp
/cast [target=pettarget] Thunderstomp
/cast [target=pettarget] Smack

if i send the pet on a target then i start dpsing on another target the stupid gorilla will change his target to the 2nd one if he's not yet in melee with the 1st

some ideas?

P.S. sry for my english :P

It looks like you're telling your pet to cast Thunderstomp and/or Smack on your current target (via the button press)... which would cause it to change targets to your current target.

Unless I'm misreading it?

It has been noted that the Auto Shot bug is happening regardless of adding all the additonal /stopmacro commands and what not (though the original ideas were great). I am also not sure the old Manito-esque /click button command works consistently with the change to server-side macros. I use a very simple macro for when I use my gorilla that basically looks like..

This macro works perfectly. The /cast !Auto Shot line is for good measure. There is no need to have Smack macro'd. Just leave both TS and Smack on autocast and the macro will basically just put TS as priority and also force it to trigger on a single mob. There really is no reason for the fancy coding in your macro to achieve the same end result. Un-check "Auto Shot/Attack" option in your interface.

EDIT: fixed wording

At the moment, on Live, according to my tests... your macro (if you have Auto Shot/Attack unchecked) will cause a loss in DPS because your Auto Shot will interrupt your Steady Shot and cause it to restart.

Edit: Never mind... you added the (/cast !Auto Shot) into your macro, which removes issue.

edit: nevermind, beaten to the punch

I was reading about the auto shot clipping issue, and nobody really had any conclusive evidence about it. So, I decided to run some tests of my own.

Equipment used: Light Bow, Cloak of Fiends, Rough Arrow x 1000 per test, and a Lower City Tabard for decency.
Aspect: Viper entire time
Spec: Link
Target: Level 60 training dummy in Darnassus.
Macro in WoW used: None, was just a straight steady shot binding from the spellbook.
G15 Macro used: A macro that hits the key binding for steady every .1 seconds on a toggle.

First test results(Auto Attack/Auto Shot checked): Picture
441 Steady Shots * 1.5 seconds for GCDs = 661.5 seconds
559 Auto Shots * 1.21 seconds for shot timer = 676.39 seconds

Second test results(Auto Attack/Auto Shot unchecked): Picture
500 Steady Shots * 1.5 seconds for GCDs = 750 seconds
500 Auto Shots * 1.21 seconds for shot timer = 605 seconds

Unfortunately, I didn't think to time these tests until midway through the second one, but I believe the difference should be large enough to show that unchecking it for some reason delays auto shots.

I tried to read through most of the posts. There is always the "Auto Attack/Shoot" mentioned. However, there is another option in the Interface "Stop Auto Attack when switching targets". I did not see (or simply overlooked) any reference to that. For me, simply

- turning off "Auto Shoot", AND
- turning on "Stopp Attack when switching targets"

does the job. No fancy "/stopattack "etc. Macro required...

Yes, I noticed your WWS reports show similar shot ratios for checked/unchecked behavior. I'm not exactly sure how you've produced the results, but the post below yours supports my findings... 500:500 vs 441:559. The #shots*delay should be fairly close for Auto Shot and Steady Shot as they are in Sthellesta's first example. The second test clearly shows that Auto Shot is frequently being reset.

Well, and what do you do about the clipping? I tried all combinations of the two options and turning off "Auto Attack/Auto Shot" lead to Auto Shot clipping, in my case having a Auto Shot fire every 2 Steady Shots, as the Auto Shot Attack Speed is higher than the Steady Cast Time. When using Quartz, whenever there is no Auto Attack Cast Bar (the small white one), something is wrong and the Auto Shot is not unlinked from other attacks. Everyone can easily try on some dummy.

Also adding some !Auto Shot in the Steady macro is not helping here - ...I never really knew, what's it with the "!" in front...

I prefer doing superior damage to occasionally pulling some mobs involuntary; as for raids, just be carefull with sheeps and you'll be fine.

I believe the solution is in the macro. Simply spamming steady shot allows the game to choose when to Auto Shoot and for some reason still clips the auto cast timer. With the line for !auto shot in a macro that spams steady it fixes it somehow. I shall do some more testing after i get off work to see if i can mimic the clipped results without using a macro to fire. If i can the good news is that the problem is solvable on our end with the use of a macro and unchecking Auto Attack/Auto Shoot. The bad news is we have to rely on a macro to perform well without fear of shooting stuff we don't want to.

If you want to test my theory before i have a chance this is the macro i used for my findings.

/console Sound_EnableSFX 0
/use [harm,nodead]Steady Shot
/cast [harm,nodead] !auto Shot
/console Sound_EnableSFX 1
/script UIErrorsFrame:Clear()

I also have a function to spam multibarbottemleftbutton12 in my in game macro which is where i have another macro forcing rake to cast but for the purpose of testing it is not needed

As for deselecting Stop Auto Attack the bug where you select a new target and fire at it after your current one dies still persists through that being disabled.

Edit: clarification
Edit: After thinking about it a bit more i might be showing these results because of my attack speed of 1.96. ill try to find a slower bow to work with and remove all my haste gear.

So after yet another round of testing with a few settings changed i have some more results that show what i have previously done and what i thought would happen. For this round i switched out my badge bow for the slower Ancient Amani Longbow and took off the 2 pieces of gear that have haste while running aspect of the viper like before.

The first one was my control test with the Auto Attack/Auto Shoot option turned on
Wow Web Stats

Second, turned off with use of a macro.
Wow Web Stats

Lastly just steady shot spam with it disabled
Wow Web Stats

I am not sure what to make of this round of testing. I think that it is buggy still with the Auto Attack/Auto Shoot option disabled, but the use of a macro that forces the auto shot to fire makes it less severe. I also believe that attack speed plays a role in how much you see the bug occurring as well. i have not noticed it enough for it to even be a negative impact on my dps with a speed of 1.96 though i am unaware of if it is effecting me while hasted through windfury totem while it lasts or during rapid fire or quick shots.

I have also tested this out with a friend like someone previously suggested. no matter the situation our auto shots desynchronized with the Auto Attack/Auto shoot disabled.

Honestly i am at a loss right now. Just to play it safe i am going to be disabling Auto Attack/Auto shoot during trash and enabling it for boss fights.

Edit: Clarification.