FD bug and other issues - Page 10

Pijn · 09/13/09, 7:54 PM

A most curious bug, that one. What I personally think what happened was; some time ago, the Steady Shot glyph didn't work properly with the MM spec caused by the talent Marked for Death, so Blizzard 'fixed' this in a later patch. However, as we only just now found out, they used bad coding and apparently added the 10% extra damage in the talent regardless of having the Steady Shot glyph or not.
Enjoy the bug while you can, I suspect Blizz will fix it somewhere in the future

Lilyana · 09/13/09, 10:32 PM

Originally Posted by Máddox

I have noticed like many have said before about pets not attacking in XT in heart phase, mimiron phase 4, and not attacking the adds on the lord jaraxxus. but not all the time would he bug out.

i have never had my pet bug out in the brain phase on Yogg...

What really bothers me is that Call of the wild seems to always reset to autocast nowadays. and is allways on cool down when i go to use it.

A workaround is to drag all the abilities you want to keep off autocast, to the pet cast bar, and leave the abilities you want to have on autocast enabled in the spellbook. This solves most of the problems however it still pays to check the spellbook whenever you zone in or summon the pet.

This is an old bug, and it has been mentioned by blizzard but no fix yet forthcoming. I hope this helps.

promdates · 09/14/09, 3:31 AM

There's another issue with that. If you use dual spec, when you summon your pet after the respec, everything is turned on auto cast, and the pet bar isn't setup how you had originally had it.

Kelthuryon · 09/14/09, 10:18 AM

Originally Posted by promdates

There's another issue with that. If you use dual spec, when you summon your pet after the respec, everything is turned on auto cast, and the pet bar isn't setup how you had originally had it.

Do you have to set it up every single time?

In my experience, each each pet is considered different for both spec: Given Wolfy the wolf, a MM and a SV spec, you have MM Wolfy and SV Wolfy. Virtually, each spec has its stables even if they both store the same pets in practice.

Normally you should only have to configure your autocasts after a respec, because your pet is then resetted.

Edit: by respec I do not mean "spec switch", but actually removing your talents.

Bozorgmehr · 09/14/09, 12:46 PM

I've had a lot of trouble with the call of the wild autocast as well. It might be worth it to make a macro like

/usetalents 1
/petautocastoff Growl
/petautocastoff Cower
/petautocastoff Call of the Wild

Though I'm not sure if that would work, since it wouldn't wait for the talent respec cast to finish before doing the last three lines. I'm going to have to test it at home, but it might be worth it to just have the last three lines macro'd to hunter's mark /petattack or something.

promdates · 09/14/09, 1:01 PM

Originally Posted by Kelthuryon

Do you have to set it up every single time?

Yes, each time I switch talent builds, I resummon the pet it comes out with the same pet bar every time. I always know what to do to get it back to normal, but it always comes out with Growl, Cower, Dash, Rabid on the bars and everything is turned to auto cast. Even replacing Rabid with CotW and turning it off auto cast won't save it if I dismiss pet, resummon, or switch specs.

Rezdan · 09/16/09, 2:37 AM

Yeah Prom, I have the same issue as well. Basically, like you, the changes I make to the pet action bar don't persist after swapping talent builds. After swapping specs, the pet will always come out of the stables with the same skills on the pet talent bar.

Thetalisker · 09/16/09, 5:24 AM

Originally Posted by promdates

If you use dual spec, when you summon your pet after the respec, everything is turned on auto cast, and the pet bar isn't setup how you had originally had it.

I thought that only happened when one of those specs is BM, but judging from your armory page I was wrong.

I can't remember where, but one explanation I read was that, when switching to and from BM, your pet had to re-learn all of its talents because of the different number of talent points. This means that after unlearning it's SV talents, for example, the state and location of the corresponding abilities are lost. When learning it's BM talents, everything is set to the default settings. This would also explain why Growl and Cower aren't affected, whereas Dash and Call of the Wild are.

I posted this on the EU forums this week, and the blue response (delete Cache, WTF and Interface and see if it automagically goes away) gave me the impression they weren't really aware of the issue. If anything worth mentioning comes out that thread I will post it here.

Edit: Blizz response is "thanks for reporting it, we have taken the issue into investigation". Again no hint that they heard of it before.

Ktharsis · 09/16/09, 12:24 PM

Happens to me whenever I switch from MM to SV or vice versa.

Maihes · 09/17/09, 3:44 AM

Glyphed

No Sting, No Mark - Hit: 561 Crit: 1393

Sting, No Mark - Hit: 611 Crit: 1531

No Sting, Mark - Hit: 629 Crit: 1563

Sting, Mark - Hit: 692 Crit: 1720

Unglyphed

No Sting, No Mark - Hit: 561 Crit: 1393

Sting, No Mark - Hit: 611 Crit: 1531

No Sting, Mark - Hit: 629 Crit: 1563

Sting, Mark - Hit: 692 Crit: 1720

Done with Fine Light Crossbow, no Pet out (was shown that FF talent didn't seem to impact if prefered I can run two more sets of parses later with pet on passive), no proc trinkets, and specced 7/57/7.

Seems that the Glyph is built in atm.

Add: So going through options for glyphs for third slot, I am torn between TSA (10% Crit to Aimed Shot) and Rapid Fire (8% more haste)

Cerevantes · 09/17/09, 12:53 PM

Originally Posted by Maihes

Glyphed
Add: So going through options for glyphs for third slot, I am torn between TSA (10% Crit to Aimed Shot) and Rapid Fire (8% more haste)

As my Guild runs with 3 Hunters regularly, I have picked up Glyph of Improved Hunter's mark in Steady Shot's place. I've found the combined hunter DPS gain is significantly more substantial than TSA or RF glyphs.

baklava · 09/17/09, 1:28 PM

I have pet damage on Yogg problem as well. Moreover, It happens at XT-002 Heart too. My pet cannot attack both targets, or the targets stays a bit higher from the ground.

I really don't know this is discussed but I have another issue at the moment;

- Wolf "Bite" ability closes itself sometimes when I log to the game. But this happens rarely, I have no idea why it happens. I have to make it autouse it every time when this happens.

Note: "Bite" ability doesnt stay at pet bar at the moment.

Maihes · 09/17/09, 5:06 PM

Originally Posted by Cerevantes

As my Guild runs with 3 Hunters regularly, I have picked up Glyph of Improved Hunter's mark in Steady Shot's place. I've found the combined hunter DPS gain is significantly more substantial than TSA or RF glyphs.

I believe we have another hunter running it already, I actually picked up KS because I noticed Marked for Death is also 10% more crit damage on it so meh.

kahdirone · 09/17/09, 7:35 PM

Anyone else having issues with pets not attacking the Snobolds on Northrend Beasts? Not incredibly dramatic, but if anyone knows how to work around it, it would be greatly appreciated.

alienangel · 09/17/09, 7:42 PM

I have never gotten my pet to attack a snobold. One of our other hunters claims his does, but I've never actually noticed his pet on the meters for damage done to snobolds, so he might be off his rocker.

Imps seem to attack them with gusto, I wonder if a windserpent could too.

Erlen · 09/17/09, 8:41 PM

I've found that hitting a pet ability such as Bite or Furious Howl will make the pet attack the kobolds and other such targets that pets seem to have trouble attacking. Our log for this week shows the kobolds taking damage from the two hunter pets.

Lilyana · 09/17/09, 8:54 PM

Originally Posted by alienangel

I have never gotten my pet to attack a snobold. One of our other hunters claims his does, but I've never actually noticed his pet on the meters for damage done to snobolds, so he might be off his rocker.

Imps seem to attack them with gusto, I wonder if a windserpent could too.

I am able to get my pet onto the snowbold if I first set to passive, recall it and then defensive + send to attack. It was a couple of weeks ago and now I leave it on Gormok.

Rozmetal · 09/19/09, 8:16 AM

Originally Posted by alienangel

I have never gotten my pet to attack a snobold. One of our other hunters claims his does, but I've never actually noticed his pet on the meters for damage done to snobolds, so he might be off his rocker.

Imps seem to attack them with gusto, I wonder if a windserpent could too.

Set your pet on defensive stance
Call your pet back
Attack Snowbold
=> he will now automatically attack snowbolds.
Enable your growl autocast and he will get the Snowbold´s attention (not always tho). Sometimes its very helpful as he will no longer interupt player´s casts etc.

prime311 · 09/23/09, 10:45 PM

My crits for Serpent Sting are way up now:

1. Crit 29 (67%) (Min: 1462 Avg: 1841 Max: 2134)
2. Tick 14 (33%) (Min: 649 Avg: 815 Max: 947)

This is with 2 piece T9+ 2 piece T8. Me likey.

Mr Tazza · 09/23/09, 10:54 PM

Originally Posted by prime311

My crits for Serpent Sting are way up now:

1. Crit 29 (67%) (Min: 1462 Avg: 1841 Max: 2134)
2. Tick 14 (33%) (Min: 649 Avg: 815 Max: 947)

This is with 2 piece T9+ 2 piece T8. Me likey.

They indeed fix it somehow, this morning SrS crit multiplier was 50% (was getting 559 hits and 9xx crits), now im getting 559 hits and 1260 crits

Masterdragon · 09/24/09, 9:38 AM

It does look like the Serpent Sting Crit Bonus from our T9 was somewhat fixed. Its now critting at the 100% crit damage value but there still seems to be something wrong with it. Heres the data from last nights raid.

World of Logs - Real Time Raid Analysis

870 Avg Non-Crit
2009 Avg Crit
230.9% Crit Damage

World of Logs - Real Time Raid Analysis

1220 Avg Non-Crit
2864 Avg Crit
234.8% Crit Damage

Those are averages though. Heres the actual log of Emalon with the Chimera's listed to seperate out the new applications.

[21:10:08.948] Wyvernmaster Chimera Shot Emalon the Storm Watcher *7397* (R: 659)
[21:10:10.307] Wyvernmaster Serpent Sting Emalon the Storm Watcher 929
[21:10:14.510] Wyvernmaster Serpent Sting Emalon the Storm Watcher *2093*
[21:10:16.354] Wyvernmaster Serpent Sting Emalon the Storm Watcher *2093*
[21:10:19.182] Wyvernmaster Serpent Sting Tempest Minion 734 (R: 82)
[21:10:19.370] Wyvernmaster Chimera Shot Tempest Minion *7470*
[21:10:19.370] Wyvernmaster Serpent Sting Emalon the Storm Watcher 929
[21:10:22.260] Wyvernmaster Serpent Sting Tempest Minion 732 (R: 81)
[21:10:22.354] Wyvernmaster Serpent Sting Emalon the Storm Watcher 836 (R: 82)
[21:10:25.088] Wyvernmaster Serpent Sting Tempest Minion 732 (R: 81)
[21:10:25.416] Wyvernmaster Serpent Sting Emalon the Storm Watcher 929
[21:10:28.135] Wyvernmaster Serpent Sting Tempest Minion *1835*
[21:10:28.448] Wyvernmaster Serpent Sting Emalon the Storm Watcher *2093*
[21:10:31.713] Wyvernmaster Chimera Shot Emalon the Storm Watcher *8886*
[21:10:33.229] Wyvernmaster Serpent Sting Emalon the Storm Watcher *2101*
[21:10:36.182] Wyvernmaster Serpent Sting Emalon the Storm Watcher *2101*
[21:10:37.916] Wyvernmaster Chimera Shot Emalon the Storm Watcher 4246
[21:10:39.245] Wyvernmaster Serpent Sting Emalon the Storm Watcher 1038
[21:10:42.135] Wyvernmaster Serpent Sting Emalon the Storm Watcher 933 (R: 92)
[21:10:45.276] Wyvernmaster Serpent Sting Emalon the Storm Watcher 830 (R: 184)
[21:10:48.166] Wyvernmaster Serpent Sting Emalon the Storm Watcher 1038
[21:10:48.807] Wyvernmaster Chimera Shot Emalon the Storm Watcher 4382
[21:10:51.135] Wyvernmaster Serpent Sting Emalon the Storm Watcher *2338*
[21:10:54.307] Wyvernmaster Serpent Sting Emalon the Storm Watcher 1038
[21:10:57.166] Wyvernmaster Serpent Sting Emalon the Storm Watcher 830 (R: 184)
[21:10:59.151] Wyvernmaster Chimera Shot Emalon the Storm Watcher 3873 (R: 381)
[21:11:00.198] Wyvernmaster Serpent Sting Emalon the Storm Watcher 959
[21:11:03.104] Wyvernmaster Serpent Sting Emalon the Storm Watcher 862 (R: 85)
[21:11:06.120] Wyvernmaster Serpent Sting Emalon the Storm Watcher *1943* (R: 85)
[21:11:07.104] Wyvernmaster Serpent Sting Tempest Minion 816
[21:11:08.979] Wyvernmaster Chimera Shot Tempest Minion *7962*
[21:11:09.229] Wyvernmaster Serpent Sting Emalon the Storm Watcher 862 (R: 85)
[21:11:10.166] Wyvernmaster Serpent Sting Tempest Minion 814
[21:11:12.151] Wyvernmaster Serpent Sting Emalon the Storm Watcher *2160*
[21:11:17.901] Wyvernmaster Serpent Sting Emalon the Storm Watcher 960
[21:11:20.838] Wyvernmaster Serpent Sting Emalon the Storm Watcher *2164*
[21:11:21.276] Wyvernmaster Chimera Shot Emalon the Storm Watcher 3699 (R: 818)
[21:11:23.713] Wyvernmaster Serpent Sting Emalon the Storm Watcher *2156*
[21:11:26.854] Wyvernmaster Serpent Sting Emalon the Storm Watcher *2156*
[21:11:29.776] Wyvernmaster Serpent Sting Emalon the Storm Watcher *2156*
[21:11:32.463] Wyvernmaster Chimera Shot Emalon the Storm Watcher *9402*
[21:11:32.807] Wyvernmaster Serpent Sting Emalon the Storm Watcher *2156*
[21:11:35.760] Wyvernmaster Serpent Sting Emalon the Storm Watcher 861 (R: 85)
[21:11:38.838] Wyvernmaster Serpent Sting Emalon the Storm Watcher 957
[21:11:41.870] Wyvernmaster Serpent Sting Emalon the Storm Watcher 765 (R: 169)
[21:11:42.682] Wyvernmaster Chimera Shot Emalon the Storm Watcher 3805
[21:11:44.854] Wyvernmaster Serpent Sting Emalon the Storm Watcher 839 (R: 82)
[21:11:47.807] Wyvernmaster Serpent Sting Emalon the Storm Watcher 839 (R: 82)
[21:11:50.745] Wyvernmaster Serpent Sting Emalon the Storm Watcher *1890* (R: 82)
[21:11:50.963] Wyvernmaster Serpent Sting Tempest Minion *1838*
[21:11:52.760] Wyvernmaster Chimera Shot Tempest Minion *7846* (R: 351)

If you compared the crits to non-crits inbetween Chimera's they're at 225% when they should be 237%.

Pijn · 09/24/09, 7:32 PM

Originally Posted by Masterdragon

If you compared the crits to non-crits inbetween Chimera's they're at 225% when they should be 237%.

I noticed the same numbers; 225% on target dummy in IF (trinkets unequiped, Furious Howl disabled), so exact same numbers posted by you and the person above. In raids you will get slightly different numbers of course, like in the logs you posted, but this makes sense since Chimera Shot will vary the Serpent Sting damage, and the random nature of crits means it won't be 225% damage overall.

Still, I can't explain where this number 225% comes from.

alienangel · 09/24/09, 7:43 PM

Since you guys seem to have missed it, this has already been discussed and more or less worked out in the spreadsheet thread: WotLK DPS spreadsheet

To summarise: Esoth's final working shows that for whatever reason, mortal shots is only having half its effect, while the metagem is having 1.5 times its effect, leading to the 225% we're seeing.

Ralnar · 09/25/09, 10:06 AM

I've done Onyxia both on 25m (Tuesday) and 10m (Thursday) in both cases, I've had any abilities not in macros, in my case Hunters Mark, Aimed and Arcane shots lock up on me after zoning into Onyxia's lair with "Invalid Target" errors. Abilities that were in macros, in my case Chimera, Silence, Serpent, Steady all worked normally.

Exiting the game completely and logging back in fixes the issue, simply logging out or reloading my UI did not. This is the first time I've had this issue and only in Onyxia's lair.

Has anyone else noticed this behavior?

Tragos · 10/15/09, 2:17 AM

Originally Posted by Ralnar

I've done Onyxia both on 25m (Tuesday) and 10m (Thursday) in both cases, I've had any abilities not in macros, in my case Hunters Mark, Aimed and Arcane shots lock up on me after zoning into Onyxia's lair with "Invalid Target" errors. Abilities that were in macros, in my case Chimera, Silence, Serpent, Steady all worked normally.

Exiting the game completely and logging back in fixes the issue, simply logging out or reloading my UI did not. This is the first time I've had this issue and only in Onyxia's lair.

Has anyone else noticed this behavior?

I had this happen to me in 10m Onyxia tonight. I wasn't able to get arcane shots off but all my other shots (which also happened to be in a macro) worked normally.

Edit: Started happening in phase 3, to my knowledge.