3 ms·
> a voxel 'rock' or other solid doesn't need to represent the 'inside' with voxels This seems to contradict Notch's (and Wikipedia's) description of a voxel.
by dpark 15y ago
> a voxel 'rock' or other solid doesn't need to represent the 'inside' with voxels
This seems to contradict Notch's (and Wikipedia's) description of a voxel. They indicate that a 3D space described by voxels has a voxel for each unit in space. The is analogous to having 1 pixel per unit of display space. If this is correct, then a rock would indeed have the inside filled with voxels.
I might be misunderstanding, though.
- zethraeus 15y agoas I understand it, the disparity in explanations can be attributed to that we're talking about using voxels in a data structure known as a sparse octree, that would in itself be used to optimize the system by, among other things, allowing only the surface information to be stored. edit: http://en.wikipedia.org/wiki/Voxel http://en.wikipedia.org/wiki/Voxel http://en.wikipedia.org/wiki/Sparse_voxel_octree http://en.wikipedia.org/wiki/Sparse_voxel_octree
- dpark 15y agoThanks. I'm a little confused how this differs from a point cloud, though. Or perhaps it'd be more correctly called a "cube cloud"?
- ChuckMcM 15y agoI don't think you are misunderstanding so much as conflating two things, the co-ordinate space / construction of the world and construction of objects within that world. It's correct to say that every 'point' in a voxel based world can be represented by a voxel in that point. It's incorrect to say that every point in a world has voxel data associated with it. Perhaps this is the place where Euclideon and Notch diverge as well. Using a quantized world representation view (where co-ordinates in the world are quantized to voxel boundaries) then as a voxel moves through the world space it moves from point to point in that space. So a 'cloud' of voxels has an origin and an orientation in worldspace, that allows the translation of a local voxel space (the object) into world voxel space. Since you can't do sub-voxel positioning it behooves you to have an oversampling rate between voxel space and display pixels as well. A 'feature' here is that it also allows for fine grain collision detection (harder to do in polygon space) but again its pretty expensive computationally. (boundary surface intersection of the local voxel space with the world voxel space).
- dpark 15y agoWhat I'm not understanding is the object space. If a voxel's coordinates are implied based on its position, then there would be voxel data for every "point" in the object space. Unless we use a sparse representation of some sort, in which case it seems that we're basically using point clouds.