-
Notifications
You must be signed in to change notification settings - Fork 142
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.
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
At high speed, colision detection misses blocks #22
Comments
schlagmichdoch
added a commit
to schlagmichdoch/yin-yang-pong
that referenced
this issue
Feb 8, 2024
schlagmichdoch
added a commit
to schlagmichdoch/yin-yang-pong
that referenced
this issue
Feb 8, 2024
schlagmichdoch
added a commit
to schlagmichdoch/yin-yang-pong
that referenced
this issue
Feb 9, 2024
schlagmichdoch
added a commit
to schlagmichdoch/yin-yang-pong
that referenced
this issue
Feb 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With a sufficiently fast velocity (easily obtained with long runtimes), balls will phase through blocks entirely.
I speculate that this happens when the velocity of the ball is greater than one block size per frame, but I haven't read the code to see how collision checks work.
Checking for blocks between the last position and the current position would help prevent such warping.
The text was updated successfully, but these errors were encountered: