Whirling Blades "random" zip-back moves

Interesting comment in https://www.reddit.com/r/pathofexile/comments/84w79j/uber_elder_kill_bestiary_hardcore

"

[–]Covetous_duelist 1 point 2 days ago

done uber elder deathless a few times, whirling blades is capped out for my ping (any faster and im garunteed to double whirl back to where i was, ~450% inc as)

i'm experiencing same issue here with whirling blades. i love the skill, and i love fast movement speed, but there has to be a way for devs to make this work correctly without making the char move to a position that does not correlate to what the player is pointing at with his mouse.


http://www.imgur.com/a/pc04Yaa

"

a_z0_9 wrote:

That's how the game works. Mouse pointer position isn't synchronized nor immediately registered when mouse moved.

0.75 attack time WB works fine at 40ms latency and start zipping randomly at 90ms+
0.45 attack time WB (necro-support in party) doesn't work properly even at 20ms.

With high attack speed and high latency you starting next WB before the game synchronizing 'new' character-relative mouse position.

So basically you need stable 120+ fps and 5ms latency to never face that issue.

"

drachonius wrote:

i'm experiencing same issue here with whirling blades. i love the skill, and i love fast movement speed, but there has to be a way for devs to make this work correctly without making the char move to a position that does not correlate to what the player is pointing at with his mouse.

There is a GGG claim that this is not supposed to happen anymore. Have not used WB myself since then. As I understand your post - your experience disagrees with the quoted GGG statement. (My guess is that the GGG statement was wrong in the first place anyway.)

"

Bex_GGG wrote:

"

Wazz72 wrote:

Does it work with Whirling Blades? ;-D

Movement skills will not lock onto the target and always move the player in the direction of your cursor.

Source: The long-awaited Attack in Place feature is coming in 3.3.0!

"

drachonius wrote:

http://www.imgur.com/a/pc04Yaa

Can you add some words to this image - what is it supposed to show?

"

drachonius wrote:

"

a_z0_9 wrote:

That's how the game works. Mouse pointer position isn't synchronized nor immediately registered when mouse moved.

0.75 attack time WB works fine at 40ms latency and start zipping randomly at 90ms+
0.45 attack time WB (necro-support in party) doesn't work properly even at 20ms.

With high attack speed and high latency you starting next WB before the game synchronizing 'new' character-relative mouse position.

So basically you need stable 120+ fps and 5ms latency to never face that issue.

New thread about this so the problem appears to persist: whirling blading back and forth instead of going straight?

Well, you can add my complain with a proposed solution over there (toggeable namelocking per skill).

I tried stuff with AutoHotKey without any success so far. Even a single simple script without adding a delay is already too slow, i'm not even sure why.

Since 3.5 will make Whirling Blades even faster afai understand it, i think it's time to fix the issue with high attack speed and Whirling Blades asap.
You can check the message above for details on the issue despite i thought it was maybe related to namelocking but it's not, it's just buggy. There's no monster name on top of the screen when it occurs.

Latest video i did that show the issue.

Answer i got from the support was this one in September 2018 :

"

Hey there,

Thank you for getting in touch with us.

This is something that the team is aware of, but unfortunately we do not yet have a current ETA for an implemented fix regarding this issue.

I am truly sorry that we are not able to be of more help in this instance, however, if there is anything else that we may be able to assist you with in the future, please do not hesitate to get back to us!

Kind regards,
CJ

I wanted to note that about 80% of the time I've died this season is due to this bug. I even switched to Leap Slam and am experiencing the same results with that skill also.

It's making some of the higher level content unplayable, especially the Betrayal events. All of the more complex fights in this game require you to avoid things.

In my opinion, GGG has been really good about fixing issues. Often times reading the patch notes feels like they've fixed things I was just noticing. Hopefully they can get to this sooner than later.

"

Harest wrote:

Well, you can add my complain with a proposed solution over there (toggeable namelocking per skill).

I tried stuff with AutoHotKey without any success so far. Even a single simple script without adding a delay is already too slow, i'm not even sure why.

I finally got tired of this problem myself and wrote this script to prevent WB from repeating during the same keypress.

"

#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
#Warn ; Enable warnings to assist with detecting common errors.
#IfWinActive, Path of Exile
SendMode Input

<your_wb_key>::
Send, {<your_wb_key> Down}
Send, {<your_wb_key> Up}
KeyWait, <your_wb_key>
Return

<hotkey_to_suspend_this_script>::Suspend

This makes it so that the key you use for WB only presses once per keypress. Some may find this behavior annoying as you need to keep repeatedly pressing your bound WB key to use the skill, but it suits me really well. Also, you can set a hotkey to suspend this script.

Hope this helps