Bug: Wesker movement transitions completely broken after patch 9.5.0
190 °C
Bug #5078

Wesker movement transitions completely broken after patch 9.5.0

Status: Under Investigation
Priority:
High
Added by:
zyravrv
on July 3, '26
Assigned to:
Unassigned
Due date:
Reported for:
Actual Result:
The Mastermind begins the forward attack travel, but his velocity artificially drops to zero before the ability's active duration fully elapses, causing him to freeze in place for a few frames while the animation finishes.
Expected Result:
The forward travel velocity should remain consistent throughout the entire active ability window. The character should only begin their slowdown/friction phase after the travel duration has officially concluded and transitioned into the Chain Bound window.
Severity:
Blocker
Reproducibility:
Always
Platform:
Steam
Additional Notes & Comments:
The character should smoothly enter a friction state only after the active power window ends, rather than being forcefully stopped while the ability is technically still ongoing.

Steps to Reproduce

  1. Hold forward ('W').
  2. Charge the Virulent Bound.
  3. Go forward with your bound by pressing m1
  4. Pay close attention to the final active frames of the travel phase.
  5. Observe that the character model loses all forward velocity and gets stuck in a static position before the attack animation finishes and transitions into the secondary window.

Explanation

Currently, there is a severe bug with the ability's deceleration logic. Before the bound's timer actually runs out, the character model forcefully decelerates to a complete, dead halt. We are effectively frozen in place for a few frames while the remaining duration of the bound ticks down, and only then does the game allow us to enter the Chain Bound window. The ability is cutting its own forward movement short before the timer allows it to naturally transition into smooth slide. Same happens at the start of the power if there was any previous movement.

Watchers

Log Files

None

No comments yet.
Loading comments...
Loading comments...
0 comments loaded

You need to join this project to comment on issues. Join Project