I think it is really funny that the term "voxel" never came up. It seems to be that, but then again, they made it sound sort of like they were trying to show only outer details, e.g. modeling the surface of a rock. In true voxel system, you'd be able to smash the rock apart and see its yummy insides, which is why those systems are so memory intensive -- space is literally subdivided along three axes and a value assigned at each point.
I figure that if you have an arbitrary shape made up of a point clouds, there isn't any reason to store non-visible points (i.e. points which are inside the rock, the previous example), which kind of leads itself to a run-length encoding sort of algorithm, e.g. this column (some X/Y point in 2D space) of points begins at height value A and goes to height value B in space. Since only the points at (X,Y,A) and (X,Y,B) would ever be visible, it wouldn't require memory usage in the same way that storing individual values at every point in the range (X,Y,A) - (X,Y,B) would like a true voxel system....which probably means that majority of the high resolution surfaces are probably static and non-destructible to minimize memory usage.
Considering the 1-point-to-1-pixel statement, it also makes me wonder whether they are trying raytracing. It probably wouldn't be too collide a ray versus a RLE height column...
I'd also like to see what happens when you zoom up to the point that their "point clouds" or "atom" or whatever start to alias multiple pixels -- if they start forming cubes, then I think I've seen enough. I couldn't tell if that happened much, but I'm talking so close that single pebble takes up my entire 1600x1200 screen. I have this funny feeling the detail wouldn't be unlimited .
I figure that if you have an arbitrary shape made up of a point clouds, there isn't any reason to store non-visible points (i.e. points which are inside the rock, the previous example), which kind of leads itself to a run-length encoding sort of algorithm, e.g. this column (some X/Y point in 2D space) of points begins at height value A and goes to height value B in space. Since only the points at (X,Y,A) and (X,Y,B) would ever be visible, it wouldn't require memory usage in the same way that storing individual values at every point in the range (X,Y,A) - (X,Y,B) would like a true voxel system....which probably means that majority of the high resolution surfaces are probably static and non-destructible to minimize memory usage.
Considering the 1-point-to-1-pixel statement, it also makes me wonder whether they are trying raytracing. It probably wouldn't be too collide a ray versus a RLE height column...
I'd also like to see what happens when you zoom up to the point that their "point clouds" or "atom" or whatever start to alias multiple pixels -- if they start forming cubes, then I think I've seen enough. I couldn't tell if that happened much, but I'm talking so close that single pebble takes up my entire 1600x1200 screen. I have this funny feeling the detail wouldn't be unlimited .