Jump to content
  • Advertisement
Sign in to follow this  

Let's talk about octree compression ratio.

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

My current implementation has about

100% -> 80% compression, is it any good?


My implementation just prune a seed in the map,

and expand out in 4 directions, namely NE, NW, SE, SW

merge them when they fall in the size threshold.


Eventually, the loop runs out of nodes, and exits out.


Actually, I can do better, but for this time

I can try to merge E, E-E, S, S-S, SE, SE-SE etc




Edited by lucky6969b

Share this post

Link to post
Share on other sites
I'm... having a terrifically hard time parsing this post.

Are you actually using an octree? Because from your description of 4 planar directions, it sounds more like a quadtree.

Also I have no idea what compression ratios would mean in the context of a spatial partitioning structure. Do you mean you want to merge adjacent nodes into larger ones?

If so, have you looked at kd-trees instead? Octrees (and quadtrees for that matter) are based on regular subdivisions. They're not ideal for merging irregular areas/volumes.

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.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!