Rectangle / Rectangle collision

See all those things with || between them? Those are the different ways the collision can occur. Try returning a value that indicates which way the collision happened, maybe with 0 for no collision.

if(CurObj.X + (CurObjDim.X / 2.0f) < CollideObj.X - (CurObjDim.X / 2.0f)) return 1;else if .... return 2;...else return 0;

actually, shouldn't i check for two of those to happen, because a rectangle won't intersect another rectangle linearly, at least two sides of the rectangle will intersect with another one.

I can figure out which two intersected, but I need to find which one to more the first rectangle back to.

ex:



the two different instances come out to the same collision, but the motion vector is different, how do i use that to find out which side it hit and then figure out where to put the rectangle back so it look like it stuck to the edge and at the point it hit?

edit: i probably should have made it more clear that the left example the first box hits the left side of the second box; and the second example the first box hits the bottom of the second box

[Edited by - EvilKnuckles666 on July 28, 2006 5:53:47 PM]

Quote:

Original post by EvilKnuckles666 actually, shouldn't i check for two of those to happen, because a rectangle won't intersect another rectangle linearly, at least two sides of the rectangle will intersect with another one. I can figure out which two intersected, but I need to find which one to more the first rectangle back to. ex: the two different instances come out to the same collision, but the motion vector is different, how do i use that to find out which side it hit and then figure out where to put the rectangle back so it look like it stuck to the edge and at the point it hit? edit: i probably should have made it more clear that the left example the first box hits the left side of the second box; and the second example the first box hits the bottom of the second box

To distinguish between these two cases you'll need to perform a swept rather than static intersection test. There's a good explanation of this test, with code, for axis-aligned boxes in a gamasutra article (by Gomez, I believe) which you can find in the gdnet articles section.