Im wondering if anyone knows any decent(free) resources on Dynamic collision detection(3d not 2d). I basicaly need to work out if the players box has hit a face of a entity.

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu

There are some threads on the topic here on the german language boards.

Basicly you have to do some bounding sphere checking. For some better results you could do boundix box checking.

Think of the camera as a sphere, then:
You know the camera position also you can say the size of the camera.
Also you know the positions of your objects in the world, and the sizes of them (calculate them in advance).
Now you can check all bounding spheres with your camere sphere.

Before starting collision detection be sure to understand frustum culling.

_________________
http://3das.noeska.com - create adventure games without programming

The current system i made is basic



It works fine for cubes but even if i wanted a cube only world, it wouldn't work with entitys that are rotated. Frustrum culling to my knowlage is basicaly working out an area in 3d space that is around the camera, if a point of an object is inside the area it can b seen.

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu

getting speedy collison detecting requires you to check as little as possible.

i use bounding boxes for my meshes inside a scene.
so first i check against frustum so i only render the visible items also for these visible objects i do boundinx box checking
if a collsions is determined i go some deeper and go face checking.

so 1. check against frustum
2. do boundix box check
3. do face check

But i see you use bsp so you should be able to skip step 1. and 2. As you alreade render a small part of the bsp. And can use that same part for collision checking.

Also you seem to have collision checking code? What is it that you do not understand?

I think it is best you ask your question at the quake to delphi project.

_________________
http://3das.noeska.com - create adventure games without programming

the collision detection for the actual level is perectly fine. But entitys are another matter. Entitys can move around the map, so u need a system thats dynamic, the code i posted is for entity collision only and is basic. It doesn't allow for the entity to rotate, say u have a train, it goes around a corner, it doesn't keep facing the same way, it rotates. with the current system the collision side would think of it as if it hadn't rotated, thus rotated entitys are imposible, and if the entity was a cylendar then it would act like a cube.

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu

For a dynamic entity with bounding box you need te have:
- its position in the world
- its size
- the rotation (not needed when using a boundingsphere for the entity)
Also you need to know the camera position (i asume you use a bounding sphere for your camera).

Now you can do some math:
- First subtract the camara pos from the object pos
- With the outcome of the previous step do the rotation calculation.
- now you can check if the sphere and the cube collide using something like

Of course the above has to be split up in x y z
That should be it. Next you can check on individual faces. It goes the same way as for the bounding box method, but the calcuation has to be done many times. I personaly don't care a lot about face checking i rather split up my meshes in more smaller meshes.

_________________
http://3das.noeska.com - create adventure games without programming

What do u mean by rotation calculation, from the code u posted it doesn't look like it factors in rotation.... Also with the "size" wouldn't that mean that the Bounding Box would have to have the exact same dimentions for its width, height, depth.......... Camera's box isn't a box as such eather:

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu

Found a rather large bug with just taking the bounding box for collision detection (personaly i don't get how face collisions would work if the player is inside the actual object and not touching a face), i made a nice(ok it looks bad..... just like a Half-Life elevator), but since the system works by the max and min of the object, the player can't get inside the elevator (since it considers everythign between the max and min a sloid part of it). Apart from the fact its compleatly unusable, the "parent - child" thign works (one when the parent entity moves all its "children" are moved with it, i.e buttons and doors on elevators).

If the elevator could b split into several bounding boxes the system could easily b modifyed, but looking at how the thing is stored (array of faces, each "model" has the faceindex and the amount of faces) i don't think its an option.

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu

i did not provide the rotation calculations, only the calculation of the collision after the rotation calculation. Read http://www.delphigl.com/script/do_show. ... 1&action=2 on how to do it.

But if you know how to do the bounding box collision detection you already know how to do the face or even vertice.

- read out a vertice (x,y,z) and (maybe) add the objects world pos to it.
- read out the camera
- the rotation (you can get that from the entity)

Now again
- First subtract the camara pos from the object pos (now face vertice + object pos)
- With the outcome of the previous step do the rotation calculation.
- now you can check if the sphere and the cube collide

and that should be it.

For a much better face collision see: http://www.gametutorials.com/Tutorials/ ... GL_Pg3.htm

_________________
http://3das.noeska.com - create adventure games without programming

From my understanding of ur code i don't think it would work right with rotations. (see the pic below, black being a cube thats rotated and blue being my guess at the areas of collision detection). Tho it may help with the elevator problem.

EDIT: tryed implementing ur code (face checking), apart from being slow, it only worked when the player is crouched.......

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu

i did not say it was fast. But first check with bounding boxes only and if that delivers a collsion do the face check for that entity.

i just noticed you recalculate a bounding box each time? That's bad. You really should precalculate them! Maybe you get a nice speed improvement.

extents is your camera size? What is it set to? try experimenting with that. Also try leaving out y collsion checking for the time being....

also i dont see rotation? With that missing it will not work.

_________________
http://3das.noeska.com - create adventure games without programming

i never added rotation cos it wouldn't work(to my knowlage anyway) so there was no point coding it. The elevator is made of 5 cubes, thats 5x6 sides which is 40 faces. all the faces should have 4 points so working out the mix/max shouldn't take much time at all.

The extents are as follows



Stand and crouch are the only things the player_box can be.

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu

Btw i checked it again and when crouching there is no collision detected at all. Just lags the pc.

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu