Jump to content
  • Advertisement
Sign in to follow this  

Spatial and scenegraph implementation woes

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

So I finally got my mesh loader rolling I now only have the SG and spatial partitioning left. What I had originally planned was having was having a normal scenegraph where each mesh node has an AABBTree, which then would be stored in an octree. Now while implementing i started wondering if this design would actually suffice? Now i know there ain't one answer for this question but do people have better suggestions? I've heard alot about ABT trees(?) but couldn't find anything real on them. Anybody have ressources about these in hand? [Edited by - JSoftware on March 30, 2006 12:40:24 PM]

Share this post


Link to post
Share on other sites
Advertisement
I personally give each node (not just geomentry nodes) their own bounding volumes and propogate changes in transformations in a downward pass, and changes in the bounding volumes in an upward pass. That way you can eliminate multiple geomentry nodes from rendering (via frustum/occlussion testing) by testing the node which groups them together. The way you have seems like it would work fine. You might consider also adding render states to your scenegraph, and maybe lighting?

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.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!