Extending lesson 10

lesson 30 can be applied to this.
But i have to admit that true colition detection is tough as hell.

Using something like ODE could help, but colition detection is something all gameprogramers must learn so it just a matter of hard work and study study study.
Using google helps to.

the easiest an cheapest hack is to use lot's and lot's of if statements that basicly say.
If you move into this area then move back because it is forbidden to go here.

tx for the info lc_overlord. The best thing I was able to google on this is:

http://www.morrowland.com/apron/article/gl/boundingbox/index.php

So I guess I'll try to come up with some clever data structure that keeps bounding box information on things kind of close to me.

Darrel

Hey,

Its strange that you should post this, last nite i started working on some code for a tutorial to add collision detection to lesson 10. The collision will allow walking upstairs, sliding along walls etc.

Unfortunately I have my dissertation to work on at the mo so finding time to do it is difficult.

Strangly enough my dissertation is a 3D map editor, which will have an option to export to (you guessed it) lesson 10 format.

So watch this space :D

Luke.

The best collision detection tutorials are on gametutorials.com.

Unfortunately, gametutorials.com recently underwent a change, and they now charge for their tutorials, which is awful. But still, the collision detection tutorials are top rate, and I know that I and alot of others learnt alot from these tutorials back when they were free. However, colision detection is complicated, even when using these tutorials, so I think there would be a chance that even after paying for these tutorials, you may not understand them, in which case you wasted good money.

The hack mentioned, whereby we make certain zones inaccessible, is certainly the best workaround I can think of without implementing real colision detection. Certainly for walking around a room, it would be easy to implement and effective.