This topic is now archived and is closed to further replies.

Speed of culling

This topic is 5000 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts


I think the best way is to calculate a set of possible visible objects (maybe your Scenegraph is able to do that...i.e. portal engines etc). For this objects you should do a Frustum Culling, sort the remaining objects by texture (shader ?) and render them.

This should be the fastest way to render things. If your complete scene is quite lowpoly (i.e. Quake 2 Map + md2 Models) you could just sort them by texture and render all of them, todays graphics cards should render that with 150+ fps (maybe even 300+).

With HW TnL you should never do culling on a per triangle-base, this would slow things down. The best should be a per object or per render call base. This just relies on your texture count/shader complexity.


Share this post

Link to post
Share on other sites
It depends. Generally, if the cost of culling is lower than the cost of rendering, then cull. If the opposite is true, then don''t. Usually, culling is very cheap, so you almost always want to cull.

On the other hand, if the bottleneck is the CPU, then culling won''t help since the GPU is idle anyway.

Share this post

Link to post
Share on other sites