Be careful about your textures. I wouldn''t want to give up being able to render the pieces of geometry in texture order. For example, if you''ve got a room busted up into 8 sections by the octree and each section is using the same 4 textures you could swap textures 4 times or 32...

AHHHHH....

I have been wondering why a texture change with textures that have already been loaded into video card memory can still be expensive. Never understood.

Thanks =)

You don''t need to quicksort the polys. In each node of the octree, collect all the polys that use a certain texture/material. Also have an array of structures for all the textures in the environment. When you traverse the octree and hit a node, for each collection of polys add it to a linked list hanging off the texture''s structure used by the collection. Once you''ve traversed all the nodes you''ll have a list of poly collections hanging off each texture. Loop through the textures and render each poly collection. This doesn''t require any sorting, the minimal work is done once per poly collection, not per poly, and you only need to loop through your list of textures in the end. It also guarantees using each texture only once.

Each one of the poly collections could be compiled into a display list.