Відео

you mean, final model isnt animated like in john lin's sandbox?

The main goal of this project is to create a feeling of nature. Firstly, as I think, it should be spacious. I've tried another solutions [1-3] to make the scene dynamic, but these ones do not deal with huge scenes. Now I'm focusing on the scene size. Maybe there's a golden mean with use of dynamic particles or so over the static scene, but for now I have no answer [1] ua-cam.com/video/1E_5YfIoM3I/v-deo.html [2] ua-cam.com/video/nYZfrOqnJd0/v-deo.html [3] ua-cam.com/video/xVeq__BfoB8/v-deo.html

@@danygankoff i know that in john lin's sandbox animated voxels are acutally just rasterized polygons within voxel volume, so its kinda stupid (for those who says static voxel rederers are boring) to expect that the entire volumetric canvas could be updated in realtime.

You are right with your idea. I want to implement LRU (like as @voxelbee described), but I'm in search for optimal measure or criterion (sorry for my English) to select (and do it fast) from voxels I have. In this video it's not done. For now, I only delete nodes on down-top merging and this could cause overflow

Maybe it makes sense to separate the idea of "streaming," which deals with the CPU->GPU flow of data, from the thing that determines what data needs to be streamed next. This determination of what is needed next might be what Daniil is calling a "progressive" approach, referring to the last-frame dependency each new frame has. Just my guess.

@@delphicdescant, thanks for your clarification. You are right. In this video I do not accent on voxel streaming but on the data to select for the next frame. @GabeRundlett, nice to meet you on my videos. Again, really love your work. I will try to explain more the details in the next video. In this one, I do not focus on the explanation but only brief what I'm working on.

Also wanted to ask how you store your octrees to maintain their relationship with one another, I'm assuming each scene is multiple octrees

Hey, rustacean ❤️ Nice to see you on my channel. I really love what you are doing with voxels 👍

The next video is for you 😉 ua-cam.com/video/1E_5YfIoM3I/v-deo.html

Voxels are 3d cubes

No, i see here rectangles in 3d, check first voxel engine Comanche dos game

Voxels are pixels in 3d not cubes, typical fake voxels we can se in Minecraft. If your opinion was a true that voxels are cubes, will be not different between voxel engine and typical polygon vector graphics.

@@djaccount5458 voxels are just values on a 3d grid. Here they are rendered shaped like cubes

Jest they have x,y,z values, if voxel are bigger if they are closer to camera, but in this example I see squares (rectangles) not cubes, maybe I have to small resolution in phone :) Never mind, Marry Christmas, i have little time today :) cheers

Thanks for the feedback ❤️ Check out [1] video description about the animations and [2] comment about the tree generation. Maybe someday I will make a video describing the internals of the project. [1] ua-cam.com/video/xVeq__BfoB8/v-deo.html [2] www.reddit.com/r/VoxelGameDev/comments/10g9gyh/comment/j5bwj6s

Thank you for your response! I will definitely look into that! I am also thinking about making my own Ray traced voxel engine (have been for quite a while now) and i have recently looked more into ray marching. It seems like ray marching is a cheaper way of achieving basically the same result (especially if you can optimize the distance functions by using an octree). What is your opinion on ray marching vs tracing for voxels?

No, not in this implementation. It is DDA advanced with some logic to skip empty octree nodes.

Hey, John. I am so glad to see you here on my channel. It could be considered, you have contributed a lot to this project, because the work you have done is extremely inspirational for me. Me [and I hope, the whole volumetric data explorers community] are waiting for you to return to this game 😉