#trigenometry

Tonight I wrote up moving box vs static box intersection. It’s basically like testing against a line segment with only one point. I add the player box’s half-extents to the static box’s and that gives us the volume to check against.

I quickly found a bug! I was getting positive intersections when the two were nowhere near one another. I went back to the wikipedia for line-line intersections and saw that I not only need to get the intersection with respect to the ray (player movement), but also with respect to the line segment. If both intersection times are between 0 and 1, the intersection is valid. That was a quick fix, but the actual time to track it down was a little longer.

The other thing I realized, although not an issue yet, is that my boxes currently support specifying a center along with the half-extents. Right now my math all assumes that the center is 0,0 relative to the object’s position. Once that is not the case, the intersections will be incorrect. I don’t see needing that any time in the near future, so I’m going to put it in my ToDo list to come back to.

One ninth period and one eleventh.

I only have english in between to study. But we're discussing the Scarlet Letter and I like it

Wahh and I know nothing.