Hi,

I read to have a good dynamic octree the best choice is to use a loose octree.

I saw the only difference is to use bounds*2 to have always the object in one cell.

Why loose octree is better for a dynamic octeee ? a better choice exists ?

Thanks for the help

Why loose octree is better for a dynamic octeee ?

because when objects move at small distance, octree not reconstrunct, right?

Best solution to what problem?

I second this.

I read to have a good dynamic octree the best choice is to use a loose octree.

Best solution to what problem?

You can see my actual engine work here :

http://zupimages.net/up/15/12/xkr4.png

Since I don't have any octree I draw all object and send all light in the clustered shading shader.

I tried to frustum culling each object but I got a very low FPS when the object count begins to be big.

Best solution to what problem?

You can see my actual engine work here :

http://zupimages.net/up/15/12/xkr4.png

Since I don't have any octree I draw all object and send all light in the clustered shading shader.

I tried to frustum culling each object but I got a very low FPS when the object count begins to be big.

This is why the graph cullings exist . To many objects to check against, V.S. a number of objects.

Anyways. This looks like it's going to be a closed environment. Did you think about a BSP tree?

This is why the graph cullings exist . To many objects to check against, V.S. a number of objects.

Yea this is why I asked to have hint how implement culling system in an engine to be the more global stuff possible, maybe that need to be a bunch of a lot of culling system mixed ?

How handle the switch of the mix of all systems, a param in the scene settings to have a culling based on the current scene ?

If a world system is made to have multiple scene streamed, the mix of culling is ok ?