Bug #2321

Wesker power usage is delayed compared to where we look with camera (community calls it urosnap bug)

Status:	Open
Priority:	High
Added by:	zyravrv on April 1, '26
Assigned to:	Unassigned
Due date:
Reported for:	10.0.0
Actual Result:	wesker's dash path will be determined by the previous frame of where we were looking in past
Expected Result:	Wesker will go in the exact same way of where we are looking at in the exactm
Severity:	Blocker
Reproducibility:	Always
Platform:	Steam
Additional Notes & Comments:	Not set

Steps to Reproduce

1. charge power
2. spin your mouse at high speed
3. click m1 to use your dash
4. notice how camera and dashing path are disconnected from each other in the initial frame

Explanation

Wesker mostlikely has wrong power action order or the dashpath is delayed compared to where we are looking by 1 frame. When we charge our bound and click m1 to use it instead of camera slowdown happening at the same moment as the dash starts(dashpath being set), since 9.5.0 PTB when we do it it appears as if said dashpath was always behind our actual camera. When we quickly spin the mouse and bound forward our dashpath will be 1 behind the acutal direction we are looking at with our camera(camera slowdown is being applied). We have desynced dash direction(dashpath) and our camera direction

Watchers

+6

All Watchers

Loading...

Watch