4 vertices, 4 faces.
8 vertices, 12 faces.
color1 = orange [1.0, 0.5, 0.0] at the front (smallest z), color2 = lime [0.75, 1.0, 0.0] at the back (largest z).
Left: image 1. Middle: image 2. Right: union.
Torus, and a Möbius strip.
Torus mesh, and a heart mesh.
For the torus, rendering the point cloud with 200×200 samples (40k points total) took about 3.3 s per frame. After converting it to a mesh with marching cubes, the result had about 7k vertices and 14k faces and rendered in around 1 s per frame, so the mesh was roughly 3× faster. Visually, the mesh also looks nicer because it is a continuous surface, while the point cloud render contain holes. If we want to have less holes from the point cloud render we would have to sample more points which further slows the rendering.
The main advantage of the point cloud was that it was easier to generate. For rendering meshes, it requires evaluation of a function and then run marching cubes. I also had to make sure the grid covered enough space to cover the complete surfae
In terms of memory, there was not a huge difference at this scale. The point cloud stores 40k 3D positions, while the mesh stores about 7k vertices plus 14k faces. The mesh does require extra connectivity information and the temporary voxel grid during construction.
10000 points sampled on the cow, each given a random velocity and pulled down by gravity.
Left to right: 10, 100, 1000, 10000 sampled points, and the original mesh.