Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NobugLandingOrigin uses incorrect velocity and origin for calculation #21

Closed
zer0k-z opened this issue Jul 20, 2021 · 0 comments
Closed

NobugLandingOrigin uses incorrect velocity and origin for calculation #21

zer0k-z opened this issue Jul 20, 2021 · 0 comments

Comments

@zer0k-z
Copy link
Contributor

zer0k-z commented Jul 20, 2021

Currently it takes the previous tick's velocity and origin to predict the landing origin.

This is not correct as velocity can be modified inbetween the two ticks due to airstrafing and the origin can also be changed due to ducking/unducking.

This causes the traces to be incorrect and can miss at times. Calling NobugLandingOrigin on a duckbugged jump will always fail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zealain @zer0k-z