#7990 Wesker is still unable to redirect second bound when doing it instantly after first

Dead by Daylight

Overview

Bugs (5474)

Releases

Dead by Daylight

Home

Discover Projects

Bug: Wesker is still unable to redirect second bound when doing it instantly after first

242 °C

Bug #7990

Wesker is still unable to redirect second bound when doing it instantly after first

Status:	Open
Priority:	Critical
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 first clip of 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 with M2.
Launch the initial forward bound.
Buffer the input for the secondary dash so it executes the moment the first one ends.
Throughhout the dashes and during the brief transition (the 1-frame gap), keep doing a very fast mouse swipe.
Observe that despite the gap existing, the mouse flick fails—the character dashes perfectly straight, discarding your mouse input.

Explanation

Despite 10.2.1 bugfix to improve redirecting with Wesker, 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