Hi,

Is it worth it to have a full dynamic octree for all or stay octree for static only still nowadays the best way ?

Thanks

What kind of queries you are going to need? If you just need single query for frustum culling which is linear operation then updating octree would just be more expensive. But if you have hundreds shadow casting point lights then it would make perfect sense.

It's essentially for frustum culling because doing frustum culling of each actor and then actor components gives worse performance than render all directly.

But it can be also be the question about the generation of shadow map atlas for point light and spot light to find the 16 nearest lights, can reduce the test of distance.

For terrain rendering I actually do GPU Quad Tree doing the culling in the hull shader, in the tessellation pass.

It's essentially for frustum culling because doing frustum culling of each actor and then actor components gives worse performance than render all directly.

But it can be also be the question about the generation of shadow map atlas for point light and spot light to find the 16 nearest lights, can reduce the test of distance.

For terrain rendering I actually do GPU Quad Tree doing the culling in the hull shader, in the tessellation pass.

Updating dynamic objects to octree is not linear operation. Frustum culling is. For just sake of frustum culling using dynamic octree isn't making any sense.

It's also because I have a light limit on the clustered shading and using the octree could add less test to select the N light visible near from the camera.

Apparently Humus will do an article on GPU Pro 7 about a new method for clustered shading using d3d12, but surely a max light still needed about perf and memory.