0 Members and 1 Guest are viewing this topic.
The model itself doesn't use polygons, it uses voxels. Let's assume that the elephant statue is contained in a 750mm (75cm) cube. The guy said there were 64 voxels per cubic millimeter, so that makes 75 * 75 * 75 * 64, or 27,000,000 voxels. If the voxel has a 32 bit color value associated with it, that is 102MB right there. On a disk, that number can be greatly reduced by not storing information about the voxels inside the model, which nobody sees, but in memory it pretty much has to be in a 3D array so the renderer can quickly access the voxel at the arbitrary point x,y,z. (Unless the breakthrough he is talking about is in searching for voxels in another way) Actually, now that I think about it, an octree could be used so empty/unseen space need not be stored.Also, did anyone notice how that guy left out games that use tesselation? So far, it has been a great solution to the polygon budget issue.