Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Automatic chunk loading #50

Open
TOGoS opened this Issue Feb 11, 2013 · 1 comment

Comments

Projects
None yet
2 participants
Contributor

TOGoS commented Feb 11, 2013

How hard do you think it would it be to have Chunky automatically load chunks during tracing? I'm thinking this could be done with a first pass that figures out which chunks rays would enter, then loads only those chunks, after which Chunky would proceed to do the full render. You'd probably want limits set, like no loading chunks that would appear <10 pixels wide, or not loading chunks hit after a ray has already bounced twice, in order to avoid loading up the whole world when someone points the camera too high. There could also be a hard limit of N chunks, which would be prioritized by closeness to the camera. (I have ideas for how this could be done pretty simply and efficiently, but I don't know how easy it would be to work in to Chunky's current architecture.)

Owner

llbit commented Feb 11, 2013

I did a test once where chunks were automatically loaded around the camera position, so it would be kind of like in-game. It shouldn't be too hard to implement. One problem is that the entire octree needs to be re-finalized after new chunks are loaded.

I've been thinking about implementing the opposite of your suggestion, which would be to cull the octree in order to optimize rendering one particular view.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment