Buffering bounds ignore fast mouse movements between dashes

Bug: Buffering bounds ignore fast mouse movements between dashes

This issue might be a duplicate of #3258 Wesker Loss of camera mobility in between Consecutive dashes. Flicking issue.

Buffering bounds ignore fast mouse movements between dashes

Status:	Pending Moderation
Priority:	High
Added by:	Anonymous on October 15, '26
Assigned to:	Unassigned
Due date:
Reported for:	10.2.1 Patch Notes
Actual Result:	When chaining the second bound immediately, the game completely ignores fast mouse movements while buffering or timing the mouse click even though there is 1 frame gap between the dashes, second dash does not change directions
Expected Result:	The game should register my quick mouse swipe during the chainwindow thanks to 1 frame gap between the dashes and let me aim in a new direction, just like in the attached video
Severity:	Blocker
Reproducibility:	Always
Platform:	Steam
Additional Notes & Comments:	an email contact or via discord would be apperciated to fully discuss what causes the issue or how to fix it. Either there is a bug where what game calculates as wesker dashpath is in "past" there's a delay to it, or camera movement restriction from first dash still carries over to second dash, or it's the problem with second dash itself

Steps to Reproduce

Charge the ability (M2)
Perform the initial forward bound.
Buffer or time the second dash so it happens the exact moment the first one finishes
In the final moments before first dash ends, swipe your mouse left or right very fast
Notice that the character just flies straight, completely ignoring your fast mouse movement even though there is 1 frame gap between the dashes

Explanation

Buffering bounds still does not allow you to insta-flick. When chaining the second bound immediately, the game completely ignores fast mouse movements. Even though there is 1-frame gap between bounds. For some reason Wesker cannot change directions while buffering bounds and trying to insta flick, as if dashpath was frame behind what's actually happening on screen (this is just theory). A consultation with dev in charge of Wesker fixes in dm would be most apperciated