Advertisement Jump to content
Sign in to follow this  
newtechnology

data structure needed for frustum culling

This topic is 1747 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

As my game is growing with hundreds of objects, performance issues are growing up. I'm doing 200 frustum intersection tests against object every frame. I thought a data structure would be good to reduce frustum tests.

 

I know about quadtree and octree and how they work. But, I just don't know how to implement it. Can anyone help me?

 

I'm doing terrain culling in hull shader (GPU based patch culling.)

10245285_860125380680484_1305655902_n.jp

Edited by newtechnology

Share this post


Link to post
Share on other sites
Advertisement

Well, but my idea is to subdivide terrain into octree (not for terrain culling) and then some how add objects list which lie in a specific node then do AABB-frustum test down tree to see if the object was visible. Any idea how to do this? or any other method (I don't understand the SIMD method properly)

Edited by newtechnology

Share this post


Link to post
Share on other sites
Hi. SIMD is a way of doing calculations, it's not a method for culling.
- you can optimize the obb or aabb cull function using SIMD
- besides this you could initially subdivide you world into sectors (big AABB's)'
then when you start culling objects, you check in which segment/AABB the camera is
- now you can just check the big AABB's which the camera is not in, and only cull objects in the sector if it's inside or intersecting the frustum

Share this post


Link to post
Share on other sites

Hi. SIMD is a way of doing calculations, it's not a method for culling.
- you can optimize the obb or aabb cull function using SIMD
- besides this you could initially subdivide you world into sectors (big AABB's)'
then when you start culling objects, you check in which segment/AABB the camera is
- now you can just check the big AABB's which the camera is not in, and only cull objects in the sector if it's inside or intersecting the frustum

I know that but I just don't know how to implement it.

 

EDIT: thanks for the sector idea, i'll try to implement it.

Edited by newtechnology

Share this post


Link to post
Share on other sites

Hey, my idea is as follows:

 

1. Divide world into 8 big sectors (AABB)
2. Load all objects on map
3. Check Intersection between object-AABB and all sectors-AABB (only once for static objects.)
4. Find out which world sector intersects object
5. Save that world sector into object's model structure 
6. Check intersection between all sectors and camera frustum (every frame)
7. save results into memory (which sectors are visible)
8. for all models, if its sector is visible, then move down to see if
object was visible (else skip because sector is not visible then its model is not visible, note: this time we are using the saved result
in memory i.e we are not doing intersection, it has been done already in step 6.)
9. If visible then draw else skip.
10. Goto step 6 (for next frame)
 
But I dunno how to implement it, yet I'll try. Anyone seeing a problem in this method? (I know a problem arises when objects are in between sectors, but in that case we would assume it has 2 sectors as its parent.)
 
(Just for understanding.)
IHXjiYK.png
 
 
(Also, sorry for bad painting skills.)
Edited by newtechnology

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!