Bug: Camera lockup during consecutive dashes ignores fast mouse movements
Camera lockup during consecutive dashes ignores fast mouse movements
| Status: | Duplicate |
| Added by: |
|
| Reported for: | |
| Actual Result: |
When chaining the second bound immediately, the game completely ignores fast mouse movements. Because the 1-frame gap between the dashes was removed, the heavy camera stiffness from the initial dash carries over, making it impossible to adjust your aim for the second dash.
|
| 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: |
Not set
|
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 because the camera is still locked.
Explanation
When chaining the second bound immediately, the game completely ignores fast mouse movements. Because the 1-frame gap between attacks was removed, the camera turn rate restriction from first dash carries over, making it impossible to adjust your aim for the second dash. If the fix to the issue would be reintroducing 1 frame gap, it is important to also adjust the animation of reseting hand to happend frame later than the dash ends, otherwise the same problem will be reintroduced. Altough there are many ways to fix insta flicks, other one could be that the last frame of dash doesn't have camera slowdown applied.
Watchers
Screenshots
None
Video Clips
None
Log Files
None