Octree problem...

choose one point of the face, preferably the center an use this to determine where to put it.
When rendering, do not only render the stricly neccessary cubes but always ''some'' more. Having a maximum allowed object size helps you a lot at this point.
There is probably a better solution out there, but it''s getting quite late here, sorry

hum, I will got problem with collision like this..

Just mark the poly as drawn with say the frame number. And check it before you render it. Or you can have a second list one for collison and one for rendering.

Good shot. I will make it like that.
Thanks a lot

A commonly used technique is to use quad/oct-trees for rendering polys, and to use a BSP tree (or another oct-tree, your choice) for collision detection. This way, you can optimize each tree to its needs. For example, you should almost NEVER perform collision tests against render-geometry (use a LOD!!) and you hardly EVER render collision-geometry (bounding-boxes, etc etc). Therefore, this two tree system is quite useful.

Another point is when you have a triangle in two (or more) nodes. When you have this case, you want to be sure to render the triangle if you see ANY of the nodes that it''s in, because you don''t want it to suddenly pop onto the screen when you move into it''s node (even though you could ''see'' it before). Therefore, the trick is to put the poly into ALL the nodes that it''s in, and simply have the is-rendered frame-counter, so you can tell if you already rendered the poly (like said above) Good luck!

Chris Pergrossi
< ctoan >
My Realm