Yep,I tried it out on the dummys.
The only issue I have now is that the "Serpent > Chimera" case just happens on a finished cd,i.e. if I put HM on the target,I have to wait until the GCD is over and FaceShooter puts Serpent on Prio #1.
I feel cheeky for asking this but would your to-do list be able to accommodate functionality for smart tracking?(after raiding work etc etc of course). I only ask as I am so impressed with fs and its simplicity! I am not a script writer so have no idea if this is realistic.
By smart tracking do you mean changing tracking modes to match the current target so that you get the benefit of Improved Tracking? If so, there's no need. All tracking targets classes benefit from Improved Tracking as long as you are tracking something (i.e. beast, human, elemental etc). Tjhis has been true since the 3.1 release.
If course, you could have been in Fish Finder mode and forgotten to swap back I guess, so perhaps alerting if you are in combat but do not have a tracking class active could be useful.
Great add on by the way. When are you planning on implementing a way to change shot priority? I play MM spec and it keeps telling me to use AiS over AS and that is clearly a dps loss for me.
Great add on by the way. When are you planning on implementing a way to change shot priority? I play MM spec and it keeps telling me to use AiS over AS and that is clearly a dps loss for me.
How did you determine that shooting arcane 1st was a dps increase?
How did you determine that shooting arcane 1st was a dps increase?
According to the spreadsheet if I prioritize AS over AiS it is roughly a 80dps increase. When I use AiS over AS I use the same amount of shots in the rotation test roughly 36 each. If I use AS first I use about 53 AS and 36 AiS. This could be due to the fact that I have the AiS glyph. Prioritizing AiS also shows that I waste time waiting for CD's in my rotation.
How did you determine that shooting arcane 1st was a dps increase?
The priority needs to be more dynamic than just "X is better than Y". I round my GCD's math to 2sec for ease of computing.
Opening with Chimera -> Aimed -> Arcane means that arcane and chimera CDs are intersecting at the 10 sec mark, and by the time you fire Chimera, Aimed is off CD and so you're pushing Arcane back 2 whole GCDs (around the 14sec mark) where it will just coincide with Chimera again.
If you open Chimera -> Arcane -> Aimed, then you get your second Arcane shot off at the 8sec mark, allowing Chimera to go off without a hitch then you have arcane and aimed CDs intersecting (14sec). At this point, Aimed needs to go first or else Arcane will intersect Chimera's CD at the 20sec mark. Instead, arcane shot will come around again in between Chimera and Aimed CD's like your opening rotation.
You get the same number of shots during both rotations (counting steady shots, which takes us to 11), but with the latter rotation, you get an extra arcane shot in place of a steady shot. Again, i simplified the rotations by using a 2sec GCD, but the same principal applies to normal rotations. Just need to model it out to see.
Update to v0.6.3b
- check for playerlevel (to prevent non-80 hunters from getting bugs)
- fixed the memory leak bug
- changed the TTL saving behavior
- hide talent specific frames (eg. Sniper Training) on respec
@Razeda
There´re no plans on making the priorities customizable. I´d rather plan on making the addon "smart" enough to offer the best priority on it´s own. In order to do this I depend on this forums feedback about what exactly the "best" priority is. Drabaks post is a nice start.
FaceShooter - a hunter shot recommendation AddOn
The optimism of action is better than the pessimism of thought.
- Greenpeace UK
I do hope that if you so make it as smart as you say, you will have to consider every single glyph combo, and also haste will be part of the factor as how many steady shots the hunter can shot out.
Not say its impossible or anything, just throwing it out there that it wont be the best or perfect priority of shots for every hunter. Also you need to take into consideration of heroism being that would give further more haste issues.
And i only say this because, there is where shot priority addons can fail badly when it gets jumbled up because of CD speed is increased.
Yeah well, getting all those right isn´t really complicated. It´s just a matter of diligence. There´re functions for all the important parts of the damage formulas are already there and the formulas themselves are well known. I´m more worried about how those results translate into priorities.
Say for example I knew that
KS_DMG = 14000, KS_CD = 15s
CS_DMG = 10000, CS_CD = 9s
SpS_DMG = 7000, SpS_TTL = 21s
AimS_DMG = 5000, AimS_CD = 10s
AS_DMG = 4500, AS_CD = 6s
SS_DMG = 3000, SS_CS = 1.6s
Simpelest solution (and the one I´ll propably use for lack of a better model) would be to prioritize them by dps or dpGCD. This solution is flawed though as has been pointed out already, the question is how to model it better.
FaceShooter - a hunter shot recommendation AddOn
The optimism of action is better than the pessimism of thought.
- Greenpeace UK
Simplest solution (and the one I´ll probably use for lack of a better model) would be to prioritize them by dps or dpGCD. This solution is flawed though as has been pointed out already, the question is how to model it better.
This is not a trivial task to implement! To translate damage into optimal priority of shots would require the addon to know about the hunter’s stats (crit, AP, haste, armPen, perhaps hit too) and target debuffs. To keep the development of the addon going, I would suggest to take the 'lowest fruits first': I believe haste issues and GCD often turn out to be the hardest point for keeping a tight rotation; "should I fire my steady shot when my CS has 1.3 sec left before ready, and my current haste is 1.6 due to rapid fire". During an encounter with movement, shifting adds etc. I hardly believe the majority of hunters are able to manage this.
I know the effect from haste only scales with SS and autoshot (volley too), but from my experience haste is the only real stat, which I struggle with to keep my rotation as perfect as it might be on a dummy. I'd love to see Faceshooter do these calculations for me, instead of me trying to keep track of my haste buffs, GCD, special shot CD, and all the stuff in raid trying to kill me
This is not a trivial task to implement! To translate damage into optimal priority of shots would require the addon to know about the hunter’s stats (crit, AP, haste, armPen, perhaps hit too) and target debuffs. To keep the development of the addon going, I would suggest to take the 'lowest fruits first': I believe haste issues and GCD often turn out to be the hardest point for keeping a tight rotation; "should I fire my steady shot when my CS has 1.3 sec left before ready, and my current haste is 1.6 due to rapid fire". During an encounter with movement, shifting adds etc. I hardly believe the majority of hunters are able to manage this.
I know the effect from haste only scales with SS and autoshot (volley too), but from my experience haste is the only real stat, which I struggle with to keep my rotation as perfect as it might be on a dummy. I'd love to see Faceshooter do these calculations for me, instead of me trying to keep track of my haste buffs, GCD, special shot CD, and all the stuff in raid trying to kill me
Love this addon, btw!
/supporting hunter
Actually I think those are relativly easy to come by. I can get most ratings with one simple function call (eg. Attack Power via UnitAttackPower("unit")) and I´m already watching target debuffs for HM, SpS and BA tracking. It will take some time to code all the necessary functions and get the calculations right but that´s not because it´s very complicated but because of the amount of data I´ll have to collect and process.
And - yes like I said I´m more concerned about questions - like when should I wait for a shot and when should I just fire the lower damaging spell and delay the other.
FaceShooter - a hunter shot recommendation AddOn
The optimism of action is better than the pessimism of thought.
- Greenpeace UK
Actually I think those are relatively easy to come by. I can get most ratings with one simple function call (eg. Attack Power via UnitAttackPower("unit")) and I´m already watching target debuffs for HM, SpS and BA tracking.
What I meant was (even if it's rather theoretical scenario): You're fighting General and standing in Shadow Crash to keep mana up, but all rogues+warriors+boomkins are deaded, and you will find zero armor debuffs on the boss. Now, in this situation I would prioritize Chimera Shot > Kill Shot due to the magical effect from CS and the phys. dmg from kill shot (affect by armor). Imo, the addon wouldn't have to be this complex
Originally Posted by Midnight
And - yes like I said I´m more concerned about questions - like when should I wait for a shot and when should I just fire the lower damaging spell and delay the other.
I'm not very much into Lua, but I assume it has boolean operators in its toolbox ("if" statements might also do the trick). I see the post by Drakbak as a possibility by modelling the entire 20 sec including individual haste rating and trying to optimize the damage within these 20 secs. If Faceshooter could 'poll' special shot CD at each GCD, it would be possible to keep the '20 sec window' sort of sliding along keeping tracks of special shot CD's. Now, by adding what you, Midnight, posted about the damage modifiers (eg. KC_DMG) and utilizing this information along with special shot CD's (from the window) it would be possible to keep the prioritization dynamic. The dynamic part from this simple algorithm would come from individual haste, as the addon should try to calculate the maximum damage within a 20 sec window.
I might be asked to make a drawing of this to explain it further
What I meant was (even if it's rather theoretical scenario): You're fighting General and standing in Shadow Crash to keep mana up, but all rogues+warriors+boomkins are deaded, and you will find zero armor debuffs on the boss. Now, in this situation I would prioritize Chimera Shot > Kill Shot due to the magical effect from CS and the phys. dmg from kill shot (affect by armor). Imo, the addon wouldn't have to be this complex
I think we´re talking at cross purposes. I think this part is by far the easier one. I´m already tracking debuffs on target so it´s just a matter of hard coding all the other relevant debuffs which is not "complicated" but rather just "time consuming".
I'm not very much into Lua, but I assume it has boolean operators in its toolbox ("if" statements might also do the trick). I see the post by Drakbak as a possibility by modelling the entire 20 sec including individual haste rating and trying to optimize the damage within these 20 secs. If Faceshooter could 'poll' special shot CD at each GCD, it would be possible to keep the '20 sec window' sort of sliding along keeping tracks of special shot CD's. Now, by adding wath you, Midnight, posted about the damage modifiers (eg. KC_DMG) and utilizing this information along with special shot CD's (from the window) it would be possible to keep the prioritization dynamic. The dynamic part from this simple algorithm would come from individual haste, as the addon should try to calculate the maximum damage within a 20 sec window.
I might be asked to make a drawing of this to explain it further
This one on the other hand may prove to be more complicated especially considering things like LnL procs, target switches, outside buffs/debuffs and about anything else unpredictable. Also maybe someone wants to do some napkin math about how many permutations for all available shots over 20s there would be - I could imagine this might put quite some strain on the CPU if that number gets too high.
FaceShooter - a hunter shot recommendation AddOn
The optimism of action is better than the pessimism of thought.
- Greenpeace UK
Also maybe someone wants to do some napkin math about how many permutations for all available shots over 20s there would be - I could imagine this might put quite some strain on the CPU if that number gets too high.
Well, to keep things simple (at first) let's take MM as it has less RNG compared to SV. My point was to do 20s damage calculations within each global cooldown. This would require you know how much damage each shot deals and how far it is from being of cooldown. The addon should hold a somewhat perfect, virtual shot rotation for the next 20s. What I see as the biggest issue is whether or not to fire that damned steady shot that I talked about in OP.
If we keep damage modifiers static and look away from crit (scales linear but still involves rng) the haste calculation becomes the important factor. Haste is a very well described stat and quite easy to figure out how it affects steady shot; and if attack speed gets <= 1.5 this will be the lower limit.
I'll try to post some pseudo code of what I think (on the top of my head) could be a possible way to find the virtual rotation:
-> GCD initiated
-> set 20s interval (might be sufficient with 15s or maybe 10s or lower)
-> poll every special shot cooldown
-> ignore special shot with cooldown > interval
-> prioritize special shot with largest dmg_modi first (will put steady shot lowest)
-> re-prioritize including cooldown for special shots
-> calculate expected damage output within interval for "initial guess" for static rotation
-> loop start: fill in steady shot before each GCD -> get expected output
-> loop end : 'save' rotation with highest expected output damage
-> show icon for first step in rotation
-> repeat at next GCD initiation
The real strain on CPU will be the filling of steady shots at each GCD in the desired interval + damage calculations, which I would be surprised if it was a noticeable load.
Actually, I think we all do this 'calculation' within our heads, but we cant really decide on the steady shot - so either we wait for special shot CD or we fire the steady shot, thus not firing special shot at the exact time it's off CD.
at higher levels of gear, Chim > KS. Glyphing for both gives them 9 second cooldowns and makes it kind of idiot proof, but on intersecting cooldowns, Chim always wins with unglyphed KS... Unless you have a Runestone proc up of course.
This mod is going to get complicated. I hope you're up for it
With the lastest version of faceshooter, sometimes it will tell me to put up a serpent sting even tho I have one on the target already. I don't know how to reproduce it tho, but I have a screenshot of it happening.
I've toggled through the commands and have the Shot display on my UI. However, it only displays ES. Even after shooting an ES, it just displays ES. Any ideas?
I downloaded the latest version for WoWInterface about 20 minutes ago.
When i tested it, for some reason it didnt give me the sniper training and the aspect, but i do want to know what set amount is set to low, and if possible make it so that you can set the amount, as i know some may not consider certain percent low as others may.
With the lastest version of faceshooter, sometimes it will tell me to put up a serpent sting even tho I have one on the target already. I don't know how to reproduce it tho, but I have a screenshot of it happening.
I've seen this as well. I've also seen where it gets lost for awhile and doesn't suggest any shots. Both events usually correct themselves within a little while, but still very odd.
I've seen this as well. I've also seen where it gets lost for awhile and doesn't suggest any shots. Both events usually correct themselves within a little while, but still very odd.
Confirmed for me as well, last night FaceShooter refused to show me anything but
serpent sting on one of the boss tries.
I've seen this as well. I've also seen where it gets lost for awhile and doesn't suggest any shots. Both events usually correct themselves within a little while, but still very odd.
I too have noticed this at specific times. The two that come to mind are attacking Ignis when someone is in the Slag Pot, and attacking Kologran's right arm when someone is in stone grip. During both of these, FS does not display any shots. Once the people are out of said abilities everything is back to normal.
I too have noticed this at specific times. The two that come to mind are attacking Ignis when someone is in the Slag Pot, and attacking Kologran's right arm when someone is in stone grip. During both of these, FS does not display any shots. Once the people are out of said abilities everything is back to normal.
I´ve already answered to this at the WoWI comments - I´m pretty sure I misjudged the event that fires when you enter/leave a vehicle not only firing for yourself but for everyone in the raid/vicinity. On the bright side - this should make it rather easy to fix the bug.
The serpent sting bug on the other hand is more complicated and will require some more investigation.
FaceShooter - a hunter shot recommendation AddOn
The optimism of action is better than the pessimism of thought.
- Greenpeace UK
The serpent sting bug on the other hand is more complicated and will require some more investigation.
For what it's worth: I tried to re-apply ssting multiple times including dropping my current
target totally. It still kept stating ssting should be the next attack to be activated.
06/09/09, 3:27 PM
Similar Threads
