Bug: Wesker's Insta-Flicks Disabled in 9.5.0 Update
Wesker's Insta-Flicks Disabled in 9.5.0 Update
| Status: | Duplicate |
| Added by: |
|
| Reported for: | |
| Actual Result: |
Wesker's second bound will go towards where he is facing at the end of his first bound. This has a harsh limit due to the limited turning rate during bounds.
|
| Expected Result: |
The second bound should go towards the intended direction, where the mouse input would have moved his camera had there been one frame in-between the bounds, as there used to be.
|
| Severity: |
Major
|
| Reproducibility: |
Always
|
| Platform: |
Steam
|
| Additional Notes & Comments: |
The patch notes for this update claimed this bug was fixed, but it seems it was not.
|
Steps to Reproduce
- Hold M2 to charge the initial bound.
- Quickly tap and release M1 to initiate the first bound.
- Quickly resume holding M1 to buffer the second bound before the first is finished.
- Input a large mouse motion right before the second bound triggers.
Explanation
Wesker cannot flick in-between buffered dashes. "Insta-flicks", a core aspect of his gameplay to dedicated Wesker mains, have not been possible since the 9.5.0 update. Any mouse movement inputted in-between dashes is ignored if the second dash is buffered after the first. Before the 9.5.0 update, there was a one-frame window between the first and second dash if input-buffered. With precise mouse movement, this allowed players to flick exactly where they wanted their second dash to go as soon as physically possible, if they were quick enough. Speaking from personal experience, it was by far my most used mechanic on Wesker. I used insta-flicks in every single match. In nearly every single chase, even. It being gone is a major hinderance to his gameplay, making him significantly less smooth and fun to pilot.
Watchers
Screenshots
None
Video Clips
None
Log Files
None