Collision Detection and Physically Based Modeling Tutorial

The source code upon which this tutorial is based, is from an older contest entry of mine (at OGLchallenge.dhs.org). The theme was Collision Crazy and my entry (which by the way took the 1st place :)) was called Magic Room. It features collision detection, physically based modeling and effects.

Collision Detection

A quite difficult subject and to be honest as far as I have seen until now, there is no easy general solution for it. For every application a slightly different way of finding and testing for collisions can be employed. Of course there are brute force algorithms which are very general but expensive and would work for every kind of objects.

We are going to investigate algorithms which are very fast, easy to understand and to some extend quite flexible. Furthermore importance must be given on what to do once a collision is detected and how to move the objects, in accordance to the laws of physics. So we have a lot stuff to cover. Lets review first what we are going to learn (click on headers to continue).

1) Collision Detection

Moving Sphere – Plane

Moving Sphere – Cylinder

Moving Sphere – Moving Sphere

2) Physically Based Modeling

Collision response

Moving under Gravity using Euler equations

3) Special Effects

Explosion Modeling using a Fin-Tree billboard method.

Sounds using the windows multimedia library (windows only ;()

4) Explaining the code

The code is divided into 5 files.

image.cpp, image.h: code from tutorial 6 to load bitmaps

MagicRoom.cpp: main code of the demo

Tmatrix33.cpp, TMatrix33.h: Classes to handle rotations

TRay.cpp, TRay.h: Classes to handle ray operations

TVector.cpp, TVector.h: Classes to handle vector operations

A lots of handy code. The Vector, Ray and Matrix classes are very useful, a nice library to have. I used them until now for personal projects.

Collision Detection

For the collision detection we are going to use algorithms which are mostly used in ray tracing.

Lets first define a ray.

A ray using vector representation is represented using a vector which denotes the start and a vector (usually normalized) which is the direction in which the ray goes. Essentially a ray starts from the start point and travels in the direction of the direction vector. So our ray equation is.

PointOnRay = Raystart + t*Raydirection

t is a float which takes values from [0, infinity).

With 0 we get the start point and substituting other values we get the corresponding points along the ray.

PointOnRay, Raystart, Raydirection, are 3D Vectors with values (x,y,z). Now we can use this ray representation and calculate the intersections with plane or cylinders.

Ray – Plane intersection detection

A plane is represented using its Vector representation as

Xn dot X = d

Xn, X are vectors and d is a floating point value.

Xn is its normal

X is a point on its surface

d is a float representing the distance of the plane along the normal, from the center of the coordinate system.

Essentially a plane represents a half space. So all that we need to define a plane is a 3D point and a normal from that point which is perpendicular to that plane. These two vectors form a plane, ie. if we take for the 3D point the vector (0,0,0) and for the normal (0,1,0) we essentially define a plane across x,z axes. Therefore defining a point and a normal is enough to compute the Vector representation of a plane.

Using the vector equation of the plane the normal is substituted as Xn and the 3D point from which the normal originates is substituted as X. The only value that is missing is d which can easily be computed using a dot product (from the vector equation).

(Note: This Vector representation is equivalent to the widely known parametric form of the plane Ax + By + Cz + D=0 just take the three x,y,z values of the normal as A,B,C and set D=-d).

The two equations we have until know are

PointOnRay = Raystart + t * Raydirection

Xn dot X = d

If a ray intersects the plane at some point then there must be some point on the ray which satisfies the plane equation as follows

Xn dot PointOnRay = d

or

(Xn dot Raystart) + t* (Xn dot Raydirection) = d

solving for t

t = (d – Xn dot Raystart) / (Xn dot Raydirection)

or by replacing d

t= (Xn dot PointOnRay – Xn dot Raystart) / (Xn dot Raydirection)

or by summing it up

t= (Xn dot (PointOnRay – Raystart)) / (Xn dot Raydirection)

t represents the distance from the start until the intersection point along the direction of the ray. Therefore substituting t into the ray equation we can get the collision point. There are a few special cases though.

If Xn dot Raydirection = 0 then these two vectors are perpendicular (ray runs parallel to plane) and there will be no collision. If t is negative the collision takes place behind the starting point of the ray along the opposite direction and again there is no intersection. In the code now the function

int TestIntersionPlane(const Plane& plane,const TVector& position,const TVector& direction, double& lamda, TVector& pNormal) {

double DotProduct = direction.dot(plane._Normal); //Dot product between plane normal and ray direction

double l2;

//Determine if ray paralle to plane

if ((DotProduct < ZERO) && (DotProduct > -ZERO)) return 0;

l2=(plane._Normal.dot(plane._Position-position)) / DotProduct; //Find distance to collision point

if (l2 < -ZERO) //Test if collision behind start

return 0;

pNormal = plane._Normal;

lamda=l2;

return 1;

}

It calculates and returns the intersection. Returns 1 if there is an intersection otherwise 0. The parameters are the plane, the start and direction of the vector, a double (lamda) where the collision distance is stored if there was any, and the returned normal at the collision point.

Ray – Cylinder intersection

Computing the intersection between an infinite cylinder and a ray is much more complicated that is why I won't explain it here. There are way too many math involved too be useful and my goal is primarily to give you tools how to do it without getting into much detail (this is not a geometry class). If anyone is interested in the theory behind the intersection code, please look at the

Graphic Gems II Book (pp 35, intersection of a with a cylinder). A cylinder is represented as a ray, using a start and direction (here it represents the axis) vector and a radius (radius around the axis of the cylinder). The relevant function is

int TestIntersionCylinder(const Cylinder& cylinder, const TVector& position, const TVector& direction, double& lamda, TVector& pNormal, TVector& newposition)

Returns 1 if an intersection was found and 0 otherwise.

The parameters are the cylinder structure (look at the code explanation further down), the start, direction vectors of the ray. The values returned through the parameters are the distance, the normal at the intersection point and the intersection point itself.

Sphere – Sphere collision

A sphere is represented using its center and its radius. Determining if two spheres collide is easy. Just by finding the distance between the two centers (dist method of the TVector class) we can determine if they intersect, if the distance is less than the sum of their two radius.

The problem lies in determining if 2 MOVING spheres collide. Bellow is an example where 2 sphere move during a time step from on point to another. Their paths cross in-between but this is not enough to prove that an intersection occurred (they could pass at a different time) nor can be the collision point be determined.

Figure 1

The previous intersection methods were solving the equations of the objects to determine the intersection. When using complex shapes or when these equations are not available or can not be solved, a different method has to be used. The start points, endpoints, time step, velocity (direction of the sphere + speed) of the sphere and a method of how to compute intersections of static spheres is already known. To compute the intersection, the time step has to be sliced up into smaller pieces. Then we move each time the spheres according to that sliced time step using its velocity, and check for collisions. If at any point collision is found (which means the spheres have already penetrated each other) then we take the previous position as the intersection point (we could start interpolating between these points to find the exact intersection position, but that is mostly not required).

The smaller the time steps, the more slices we use the more accurate is the method. As an example lets say the time step is 1 and our slices are 3, then we would check the two balls for collision at time 0 , 0.33, 0.66, 1. Easy !!!! The code which performs this is

/*************************************************************************************/

/*************************************************************************************/

/***                  Find if any of the current balls                            ****/

/***             intersect with each other in the current timestep                ****/

/***Returns the index of the 2 intersecting balls, the point and time of intersection */

/*************************************************************************************/

/*************************************************************************************/

int FindBallCol(TVector& point, double& TimePoint, double Time2, int& BallNr1, int& BallNr2) {

TVector RelativeV;

TRay rays;

double MyTime=0.0, Add=Time2/150.0, Timedummy=10000, Timedummy2=-1;

TVector posi;

//Test all balls against each other in 150 small steps

for (int i=0; i < NrOfBalls - 1; i++) {

for (int j = i+1; j < NrOfBalls; j++) {

RelativeV = ArrayVel[i] - ArrayVel[j]; // Find distance

rays = TRay(OldPos[i], TVector::unit(RelativeV));

MyTime = 0.0;

if ( (rays.dist(ArrayPos[j])) > 40) continue;       //If distance between centers bigger than 2*radius

//an intersection occurred

while (MyTime < Time2) //Loop to find the exact intersection point

{

MyTime += Add;

posi = OldPos[i] + RelativeV * MyTime;

if (posi.dist(OldPos[j]) <= 40) {

point = posi;

if (Timedummy > (MyTime - Add)) Timedummy = MyTime - Add;

BallNr1 = i;

BallNr2 = j;

break;

}

}

}

}

if (Timedummy != 10000) {

TimePoint = Timedummy;

return 1;

}

return 0;

}

How to use what we just learned

So now that we can determine the intersection point between a ray and a plane/cylinder we have to use it somehow to determine the collision between a sphere and one of these primitives. What we can do so far is determine the exact collision point between a particle and a plane/cylinder. The start position of the ray is the position of the  particle and the direction of the ray its velocity (speed and direction). To make it usable for spheres is quite easy. Look at Figure 2a to see how this can be accomplished.

Figure 2a                       Figure 2b

Each sphere has a radius, take the center of the sphere as the particle and offset the surface along the normal of each plane/cylinder of interest. In Figure 2a these new primitives are represented with doted lines. Your actual primitives of interest are the ones represented with continuous lines but the collision testing is done with the offset primitives (represented with doted lines). In essence we perform the intersection test with an little offset plane and a larger in radius cylinder. Using this little trick the ball does not penetrate the surface if an intersection is determined with its center. Otherwise we get a situation as in Figure 2b, where be sphere penetrates the surface. This happens because we determine the intersection between its center and the primitives, which means we did not modify our original code!

Having determined where the collision takes place we have to determine if the intersection takes place in our current time step. Timestep is the time we move our sphere from its current point according to its velocity. Because we are testing with infinite rays there is always the possibility that the collision point is after the new position of the sphere. To determine this we move the sphere, calculate its new position and find the distance between the start and end point. From our collision detection procedure we get also the distance from the start point to its collision point. If this distance is less than the distance between start and end point then there is a collision. To calculate the exact time we solve this simple equation. Represent the distance between start – end point with Dst, the distance between start – collision point Dsc, and the time step as T. The time where the collision takes place (Tc) is:

Tc= Dsc * T / Dst

All this is performed of course if an intersection is determined. The returned time is a fraction of the whole time step, so if the time step was 1 sec, and we found an intersection exactly in the middle of the distance then the calculated collision time would be 0.5 sec. this can be interpreted like "0.5 sec after the start there is an intersection". Now the intersection point can be calculated by just multiplying Tc with the current velocity and adding it to the start point.

Collision point= Start + Velocity * Tc

This is the collision point on the offset primitive, to find the collision point on the real primitive we add to that point the reverse of the normal at that point (which is also returned by the intersection routines) by the radius of the sphere. Note that the cylinder intersection routine returns the intersection point if there is one so it does not need to be calculated.

Physically Based Modeling

Collision Response

To determine how to respond after hitting Static Objects like Planes, Cylinders is as important as finding the collision point itself. Using the algorithms and functions described the exact collision point, the normal at the collision point and the time within a time step in which the collision occurs can be found.

To determine how to respond to a collision, laws of physics have to be applied. When an object collides with the surface its direction changes i.e.. it bounces off. The angle of the of the new direction (or reflection vector) with the normal at the collision point is the same as does the original direction vector. Figure 3 shows a collision with a sphere.

Figure 3

R is the new direction vector

I is the old direction vector before the collision

N is the Normal at the collision point

The new vector R is calculated as follows:

R= 2 * (-I dot N) * N + I

The restriction is that the I and N vectors have to be unit vectors. The velocity vector as used in our examples represents speed and direction. Therefore it can not be plugged into the equation in the place of I, without any transformation. The speed has to be extracted. The speed for such a velocity vector is extracted finding the magnitude of the vector. Once the magnitude is found, the vector can be transformed to a unit vector and plugged into the equation giving the reflection vector R. R shows us now the direction, of the reflected ray, but in order to be used as a velocity vector it must also incorporate the speed. Therefore it gets, multiplied with the magnitude of the original ray, thus resulting in the correct velocity vector.

In the example this procedure is applied to compute the collision response if a ball hits a plane or a cylinder. But it works also for arbitrary surfaces, it does not matter what the shape of the surface is. As long as a collision point and a Normal can be found the collision response method is always the same. The code which does these operations is

rt2=ArrayVel[BallNr].mag(); //find magnitude of velocity

ArrayVel[BallNr].unit(); //normalize it

//compute reflection

ArrayVel[BallNr] = TVector::unit( (normal * (2 * normal.dot(-ArrayVel[BallNr]))) + ArrayVel[BallNr] );

ArrayVel[BallNr] = ArrayVel[BallNr] * rt2; //muliply with magnitude to obtain final velocity vector

When Spheres hit other Spheres

Determining the collision response, if two balls hit each other is much more difficult. Complex equations of particle dynamics have to be solved and therefore I will just post the final solution without any proof. Just trust me on this one :) During the collision of 2 balls we have a situation as it is depicted in Figure 4.

Figure 4

U1 and U2 are the velocity vectors of the two spheres at the time of impact. There is an axis (X_Axis) vector which joins the 2 centers of the spheres, and U1x, U2x are the projected vectors of the velocity vectors U1,U2 onto the axis (X_Axis) vector.

U1y and U2y are the projected vectors of the velocity vectors U1,U2 onto the axis which is perpendicular to the X_Axis. To find these vectors a few simple dot products are needed. M1, M2 is the mass of the two spheres respectively. V1,V2 are the new velocities after the impact, and V1x, V1y, V2x, V2y are the projections of the velocity vectors onto the X_Axis.

In more detail:

a) Find X_Axis

X_Axis = (center2 – center1);

Unify X_Axis, X_Axis.unit();

b) Find Projections

U1x = X_Axis * (X_Axis dot U1)

U1y = U1 – U1x

U2x = -X_Axis * (-X_Axis dot U2)

U2y = U2 – U2x

c) Find new velocities

V1x = ((U1x * M1) + (U2x * M2) - (U1x - U2x) * M2) / (M1 + M2)

V2x= ((U1x * M1) + (U2x * M2) - (U2x - U1x) * M1) / (M1 + M2)

In our application we set the M1=M2=1, so the equations get even simpler.

d) Find the final velocities.

V1y = U1y

V2y = U2y

V1 = V1x+V1y

V2 = V2x+V2y

The derivation of that equations has a lot of work, but once they are in a form like the above they can be used quite easily. The code which does the actual collision response is

TVector pb1, pb2, xaxis, U1x, U1y, U2x, U2y, V1x, V1y, V2x, V2y;

double a,b;

pb1 = OldPos[BallColNr1 ] + ArrayVel[BallColNr1] * BallTime; //find pisiotion of ball1

pb2 = OldPos[BallColNr2] + ArrayVel[BallColNr2] * BallTime; //find position of ball2

xaxis = (pb2 - pb1).unit(); // find xaxis

a = xaxis.dot(ArrayVel[BallColNr1]); // find projection

U1x = xaxis * a; // find projected vectors

U1y = ArrayVel[BallColNr1] - U1x;

xaxis = (pb1 - pb2).unit(); // do the same as above

b = xaxis.dot(ArrayVel[BallColNr2]); // to find projection

U2x = xaxis * b; // vectors for the other ball

U2y = ArrayVel[BallColNr2] - U2x;

V1x = (U1x + U2x - (U1x - U2x)) * 0.5; // now find new velocities

V2x = (U1x + U2x - (U2x - U1x)) * 0.5;

V1y = U1y;

V2y = U2y;

for (j=0; j < NrOfBalls; j++) // update all ball positions

ArrayPos[j] = OldPos[j] + ArrayVel[j] * BallTime;

ArrayVel[BallColNr1] = V1x + V1y; // set new velocity vectors

ArrayVel[BallColNr2] = V2x + V2y; // to the colliding balls

Moving under Gravity using Euler equations

To simulate realistic movement with collisions, determining the the collision point and computing the response is not enough. Movement based upon physical laws has also to be simulated.

The most widely used method for doing this is using Euler equations. As indicated all the computations are going to be performed using time steps. This means that the whole simulation is advanced in certain time steps during which all the movement, collision and response tests are performed. As an example we can advanced a simulation 2 sec. on each frame. Based on Euler equations, the velocity and position at each new time step is computed as follows:

Velocity_New = Velovity_Old + Acceleration * TimeStep

Position_New = Position_Old + Velocity_New * TimeStep

Now the objects are moved and tested angainst collision using this new velocity. The Acceleration for each object is determined by accumulating the forces which are acted upon it and divide by its mass according to this equation.

Force = mass * acceleration

A lot of physics formulas :)

But in our case the only force the objects get is the gravity, which can be represented right away as a vector indicating acceleration. In our case something negative in the Y direction like (0,-0.5,0). This means that at the beginning of each time step, we calculate the new velocity of each sphere and move them testing for collisions. If a collision occurs during a time step (say after 0.5 sec with a time step equal to 1 sec.) we advance the object to this position, compute the reflection (new velocity vector) and move the object for the remaining time (which is 0.5 in our example) testing again for collisions during this time. This procedure gets repeated until the time step is completed.

When multiple moving objects are present, each moving object is tested with the static geometry for intersections and the nearest intersection is recorded. Then the intersection test is performed for collisions among moving objects, where each object is tested with everyone else. The returned intersection is compared with the intersection returned by the static objects and the closest one is take. The whole simulation is updated to that point, (i.e. if the closest intersection would be after 0.5 sec. we would move all the objects for 0.5 seconds), the reflection vector is calculated for the colliding object and the loop is run again for the remaining time.

Special Effects

Explosions

Every time a collision takes place an explosion is triggered at the collision point. A nice way to model explosions is to alpha blend two polygons which are perpendicular to each other and have as the center the point of interest (here intersection point). The polygons are scaled and disappear over time. The disappearing is done by changing the alpha values of the vertices from 1 to 0, over time. Because a lot of alpha blended polygons can cause problems and overlap each other (as it is stated in the Red Book in the chapter about transparency and blending) because of the Z buffer, we borrow a technique used in particle rendering. To be correct we had to sort the polygons from back to front according to their eye point distance, but disabling the Depth buffer writes (not reads) does also the trick (this is also documented in the red book). Notice that we limit our number of explosions to maximum 20 per frame, if additional explosions occur and the buffer is full, the explosion is discarded. The source which updates and renders the explosions is

//render/blend explosions

glEnable(GL_BLEND); //enable blending

glDepthMask(GL_FALSE); //disable depth buffer writtes

glBindTexture(GL_TEXTURE_2D, texture[1]); //upload texture

for(i = 0; i < 20; i++) //update and render explosions

{

if (ExplosionArray[i]._Alpha >= 0) {

glPushMatrix();

ExplosionArray[i]._Alpha -= 0.01f; //update alpha

ExplosionArray[i]._Scale += 0.03f; //update scale

//assign vertices colour yellow with alpha

// colour tracks ambient and diffuse

glColor4f(1, 1, 0, ExplosionArray[i]._Alpha);

//scale

glScalef(ExplosionArray[i]._Scale, ExplosionArray[i]._Scale, ExplosionArray[i]._Scale);

// translate into position taking into acout the offset caused by the scale

glTranslatef((float)ExplosionArray[i]._Position.X() / ExplosionArray[i]._Scale, (float)ExplosionArray[i]._Position.Y() / ExplosionArray[i]._Scale, (float)ExplosionArray[i]._Position.Z() / ExplosionArray[i]._Scale);

glCallList(dlist); // call display list glPopMatrix();

}

}

Sound

For the sound the windows multimedia function  PlaySound is used. This is a quick and dirty way to play wav files quickly and without trouble.

Explaining the Code

Congratulations…

If you are still with me you have survived successfully the theory section ;)

Before having fun playing around with the demo, some further explanations about the source code are necessary.

The main flow and steps of the simulation are as follows (in pseudo code).

While (Timestep != 0) {

For each ball {

compute nearest collision with planes;

compute nearest collision with cylinders;

Save and replace if it the nearest intersection in time computed until now;

}

Check for collision among moving balls;

Save and replace if it the nearest intersection in time computed until now;

If (Collision occurred) {

Move All Balls for time equal to collision time;

(We already have computed the point, normal and collision time.)

Compute Response;

Timestep -= CollisonTime;

} else Move All Balls for time equal to Timestep

}

The actual code which implements the above pseudo code is much harder to read but essentially is an exact implementation of the pseudo code above.

// While time step not over

while (RestTime > ZERO) {

lamda = 10000; //initialize to very large value

// For all the balls find closest intersection between balls and planes/cylinders

for (int i = 0; i < NrOfBalls; i++) {

// compute new position and distance

OldPos[i] = ArrayPos[i];

TVector::unit(ArrayVel[i],uveloc);

ArrayPos[i] = ArrayPos[i] + ArrayVel[i] * RestTime;

rt2 = OldPos[i].dist(ArrayPos[i]);

// Test if collision occured between ball and all 5 planes

if (TestIntersionPlane(pl1, OldPos[i], uveloc, rt, norm)) {

// Find intersection time

rt4 = rt * RestTime / rt2;

// if smaller than the one already stored replace and in timestep

if (rt4 <= lamda) {

// if intersection time in current time step

if (rt4 <= RestTime + ZERO) if (! ((rt <= ZERO) && (uveloc.dot(norm) > ZERO)) ) {

normal = norm;

point=OldPos[i] + uveloc * rt;

lamda = rt4;

BallNr = i;

}

}

}

if (TestIntersionPlane(pl2, OldPos[i], uveloc, rt, norm)) {

//…The same as above omitted for space reasons

}

if (TestIntersionPlane(pl3, OldPos[i], uveloc, rt, norm)) {

//…The same as above omitted for space reasons

}

if (TestIntersionPlane(pl4, OldPos[i], uveloc, rt, norm)) {

//…The same as above omitted for space reasons

}

if (TestIntersionPlane(pl5, OldPos[i], uveloc, rt, norm)) {

//…The same as above omitted for space reasons

}

// Now test intersection with the 3 cylinders

if (TestIntersionCylinder(cyl1, OldPos[i], uveloc, rt, norm, Nc)) {

rt4 = rt * RestTime / rt2;

if (rt4 <= lamda) {

if (rt4 <= RestTime + ZERO) if (! ((rt <= ZERO) && (uveloc.dot(norm) > ZERO)) ) {

normal = norm;

point = Nc;

lamda = rt4;

BallNr = i;

}

}

}

if (TestIntersionCylinder(cyl2, OldPos[i], uveloc, rt, norm, Nc)) {

//…The same as above omitted for space reasons

}

if (TestIntersionCylinder(cyl3, OldPos[i], uveloc, rt, norm, Nc)) {

//…The same as above ommited for space reasons

}

}

// After all balls were tested with planes/cylinders test for collision

// between them and replace if collision time smaller

if (FindBallCol(Pos2, BallTime, RestTime, BallColNr1, BallColNr2)) {

if (sounds) PlaySound("Explode.wav", NULL, SND_FILENAME|SND_ASYNC);

if ( (lamda == 10000) || (lamda > BallTime) ) {

RestTime = RestTime - BallTime;

TVector pb1, pb2, xaxis, U1x, U1y, U2x, U2y, V1x, V1y, V2x, V2y;

double a,b;

...

code omitted for space reasons

the code is described in the Physically Based Modeling section under sphere to sphere collision

...

// Update explosion array and insert explosion

for (j = 0; j < 20; j++) {

if (ExplosionArray[j]._Alpha <= 0) {

ExplosionArray[j]._Alpha = 1;

ExplosionArray[j]._Position = ArrayPos[BallColNr1];

ExplosionArray[j]._Scale = 1;

break;

}

}

continue;

}

}

// End of tests

// If collision occured move simulation for the correct timestep

// and compute response for the colliding ball

if (lamda !=10000) {

RestTime -= lamda;

for (j = 0; j < NrOfBalls; j++) ArrayPos[j] = OldPos[j] + ArrayVel[j] * lamda;

rt2 = ArrayVel[BallNr].mag();

ArrayVel[BallNr].unit();

ArrayVel[BallNr] = TVector::unit( (normal * (2 * normal.dot(-ArrayVel[BallNr]))) + ArrayVel[BallNr] );

ArrayVel[BallNr] = ArrayVel[BallNr] * rt2;

// Update explosion array and insert explosion

for (j = 0; j < 20; j++) {

if (ExplosionArray[j]._Alpha <= 0) {

ExplosionArray[j]._Alpha = 1;

ExplosionArray[j]._Position = point;

ExplosionArray[j]._Scale = 1;

break;

}

}

} else RestTime=0;

} //end of while loop

The main global variables of importance are:

Represent the direction and position of the camera. The camera is moved using the LookAt function. As you will probably notice, if not in hook mode (which I will explain later), the whole scene rotates around, the degree of ratation is handles with camera_rotation.

TVector dir; TVector pos(0,-50,1000); float camera_rotation=0;

Represent the acceleration applied to the moving balls. Acts as gravity in the application.

TVector accel(0,-0.05,0);

Arrays which hold the New and old ball positions and the velocity vector of each ball. The number of balls is hard coded to 10.

TVector ArrayVel[10]; TVector ArrayPos[10]; TVector OldPos[10]; int NrOfBalls=3;

The time step we use.

double Time=0.6;

If 1 the camera view changes and a (the ball with index 0 in the array) ball is followed. For making the camera following the ball we used its position and velocity vector to position the camera exactly behind the ball and make it look along the velocity vector of the ball.

int hook_toball1=0;

Self explanatory structures for holding data about explosions, planes and cylinders.

struct Plane struct Cylinder struct Explosion

The explosions are stored in a array, of fixed length.

Explosion ExplosionArray[20];

The main functions of interest are:

Perform Intersection tests with primitives

int TestIntersionPlane(…); int TestIntersionCylinder(…);

Loads Textures from bmp files

void LoadGLTextures();

Has the rendering code. Just renders every time the balls, walls, columns and explosions

void DrawGLScene();

Performs the main simulation logic

void idle();

Sets Up OpenGL state

void InitGL();

Find if any balls collide again each other in current time step

int FindBallCol(…);

For more information look at the source code. I tried to comment it as good as possible. Once the collision detection and response logic is understood, the source should become very clear. For any more info don't hesitate to contact me.

As was stated at the beginning the subject of collision detection is a very difficult and versatile subject to be covered only by one tutorial. Although we have come a long way, learned a lot of new stuff and can now create some nifty and impressive things as the demo shows, there is still a long way in front of you. Now that you have the basics all the other sources on Collision Detection and Physically Based Modeling out there should become easier to understand. With this I send you on your way and wish you happy collisions!!!

Content

Collision Detection and Physically Based Modeling Tutorial

Collision Detection

Ray – Plane intersection detection

Ray – Cylinder intersection

Sphere – Sphere collision

How to use what we just learned

Physically Based Modeling

Collision Response

When Spheres hit other Spheres

Moving under Gravity using Euler equations

Special Effects

Explosions

Sound

Explaining the Code