Back to General and Gameplay Programming

Let's talk about octree compression ratio.

General and Gameplay Programming Programming

Started by lucky6969b October 15, 2016 06:27 AM

1 comment, last by lucky6969b 7 years, 6 months ago

lucky6969b

1,334

Author

October 15, 2016 06:27 AM

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

Thanks

Jack

ApochPiQ

23,138

October 15, 2016 06:37 AM

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.

Wielder of the Sacred Wands
[Work - ArenaNet] [Epoch Language] [Scribblings]