3.10.1d Patch and Dash + Second Wind

The latest patch totally screwed with Dash functionality when supported by Second Wind.

Now, when the button pressed, at high Attack Speed values, the dash is often:

1. invoked twice, when there are 2 invocations available
2. desyncs like it's 2018, with artifacts like being able to pick items at a location where the char would be if only 1 Dash was performed, while being at a location where the char ends up after 2 Dashs being performed.

This, of course, almost never happens (there is some desync), when Dash isn't supported by Second Wind.

That behavior hasn't been observed by me prior to 3.10.1d patch (or perhaps 3.10.1c)...

At the moment I am at a 2.23 Default Attack/Second, as an FYI.

Now, Dash should not generally be affected by Attack Speed, so my guess is that a bug has been introduced.

I recall similar behaviour being observed with other skills in the past, although I can't recall which...

Any thoughts?

At this point Dash with Second Wind is nearly unplayable (and I have died at least a dozen times due to the stupid desync).

Note: for control purposes I've been playing for the last several days on/off with and without Second Wind, and the desync is consistent: present with Second Wind, absent without.

Having the exact same problem! It's unplayable.

I'm seeing the same problem since 3.10.1d. Very painful to dash foward and then immediately backward.

I switched to flamedash to avoid it for now.

Can confirm that I'm having this problem as well while on lockstep and I made sure I was using attack in place nor was I pressing shift. I seem to be going dashing forward but then backwards again sometimes expending a charge as well even though I've pressed dash only once. I have tested it with another key and my spare keyboard and the problem is still there

it does double invocation when mapped to a mouse button as well. Any mouse button.

It is not a hardware problem.

So, how do we get this reported?

There isn't an announcement about it yet, but there is a new client-side patch that seems to correct this behavior.

Reddit? I don't see anything here.

Did GGG provide an ETA for that?

"

Wallach wrote:

There isn't an announcement about it yet, but there is a new client-side patch that seems to correct this behavior.

Still the same behaviour for me post patch

I don't think there was a patch post 3.10.1d

i actually post this problem but on wrong forum section.

https://www.pathofexile.com/forum/view-thread/2835971

--------
Problem

1. start attacking with wand and barrage support (with or without attack in place, without attack in place pressed)
2. place mouse cursor at distance less or equal to dash travel distance
3. press dash

result
1. character dash forward then backward (opposite to mouse direction)
2. both charges of dash spended

should be:
1. character dash forward in mouse direction
2. 1 charge spended

The problem comeback again after patch 3.11d

Video proof
https://imgur.com/a/uRI46ds


PS holding attack button and press dash+second wind works perfectly before this patch, now its broken, again

PPS removing the second wind support solve the problem, its all about spending 2 charges with 1 key press

PPS2 bugs only occures if mouse place closer or equal to dash distance and only for attacks supported by barrage support or barrage itself (mb with multistrike too)
-------------