🚀 go-pugleaf

Kevin Martin (sigma@picasso.ipl.rpi.edu) writes:

}                                                                it was sort
} of just that the ball could accidentally go through things.

Here is another problem that could easily be overlooked. If the ball's
speed is sufficiently high, it is not enough to check for collision
with just 1 object borderline. Bluntly computing its new position and
heading after 1 collision might cause it to pass a couple of
other borders too, that are ignored in the computation.
If you ask me, during each frame collisions should be checked like
this:
	while ball will collide with some object:
		compute new heading and position ball AT the object's
		border;
		repeat, to see if it can hit something else;

	position ball for next frame;

So the above while-statement should definitely not be an if-statement.
Am I right?

Martin