TPMS Structures in Cinema 4D: Gyroid, Primitive and Diamond with Scene Nodes and Volumes (2026)
Triply periodic minimal surfaces such as the Gyroid can be generated in Cinema 4D by evaluating their equation on voxel points inside a Node Mesh, then turning the kept points into a smooth surface with a Fog Volume Builder.
- Boundary: a Hexa Platonic (about 150 cm) inside a Connect object defines the cube the structure fills.
- Points: Volume Voxel Fill turns the boundary into a solid grid of points; Split Vector gives x, y and z.
- Formula: trigonometry nodes evaluate the TPMS equation; L sets the cell size, T the wall thickness.
- Surface: a Volume Builder set to Fog, voxel size synced with XPresso, then Fog Smooth at about 50%.
- Variants: swap the formula to get the Primitive or Diamond surface with the same setup.
Triply periodic minimal surfaces (TPMS) are surfaces with zero mean curvature that repeat in all three directions. Their large surface area for their weight is why engineers use them in 3D printing, heat exchangers and lightweight parts, and why they make striking abstract motion graphics.
Our tutorial builds them inside Cinema 4D with Scene Nodes and Volumes. This guide explains the idea behind the setup, the role of each node, and how the same graph produces the Gyroid, the Primitive and the Diamond surfaces just by changing the formula.
Checked against the Maxon Cinema 4D help pages for Scene Nodes and the Volume Builder, and published TPMS level-set equations, November 2026.
The full tutorial runs 16:43. Chapters: 0:00 intro, 1:17 boundary, 2:12 Node Mesh and Volume, 14:22 experiments with other formulas, 15:41 wrap-up.
What a TPMS is, in practical terms
A TPMS divides space into two connected regions with one smooth surface that repeats like a crystal lattice. The exact Gyroid is described with elliptic integrals, so in practice software uses a simpler trigonometric level-set equation that approximates it; materials scientists made the same substitution long ago (see the discussion in Mixing Mathematics and Materials, arXiv). The common Gyroid form is sin x cos y + sin y cos z + sin z cos x = C (arXiv 2511.19821).
How to read the figure. Each panel plots the points where one equation is close to zero on a single slice through the structure. The Gyroid gives the curving, labyrinth-like channels it is known for, the Primitive gives rounded openings on a square grid, and the Diamond gives a diagonal, diamond-like pattern. In Cinema 4D you evaluate the same expressions on 3D points, so you get the full surface instead of a slice.
The setup at a glance
The graph runs in four stages, from a boundary shape to a smooth surface. The figure shows what each stage produces.
How to read the figure. Panel 1 is the boundary, a Hexa Platonic inside a Connect object. Panel 2 is the same cube after Volume Voxel Fill: a regular grid of points. Panel 3 keeps only the points where the Gyroid equation is close to zero, which already shows the curving channels of the structure; these points were computed from the equation, two cells per side. Panel 4 is the Fog Volume Builder: each kept point becomes a soft blob of density, and Fog Smooth blends them into one continuous surface.
1. Build the boundary
Create a Connect object and put a Platonic object inside it with a radius of about 150 cm and the type set to Hexa. That gives a cube for the structure to fill. Keeping it inside a Connect object makes it easy to swap the shape later: any closed object can become the boundary.
2. Turn the boundary into points
- Create a Node Mesh and an Object Link input in the node workspace, and link the boundary object.
- Apply Volume Voxel Fill to turn the object into a solid volume, and expose the control parameters you need (such as voxel size).
- Use Decompose Container and Iterate Collection to read the point coordinates from the solid volume.
- Use Split Vector to get the X, Y and Z values of each point.
Scene Nodes are built for this kind of geometry processing: Maxon’s introduction describes them as a way to generate geometry and modelling functions from nodes, including functions not available as normal objects (Maxon: Scene Nodes Introduction).
How to read the figure. This is the graph behind steps 2 and 3, drawn the way it looks in the Node Editor with helper nodes left out. Read the top row left to right: it turns the boundary object into a grid of points and splits each into X, Y and Z. The dashed wire takes those values to the bottom row, which runs the Gyroid formula, compares it with the thickness T and passes only the points that pass to Append Element. If the result looks inverted or empty, the Compare node is the first place to check.
3. Apply the TPMS formula
Use calculation nodes and the Trigonometry node to implement the equation. Two parameters control the result:
- L, the size of one unit cell in each direction. Scale the coordinates by 2π/L before the sine and cosine.
- T, the wall thickness. A common way to turn the zero surface into a solid shell is to keep the points where the square of the equation is smaller than the square of T (TPMS equations, GitHub gist).
Then use Assemble Collection to collect the original point data together with the results of the formula, Append Element to build the final point collection, and a Point Set node to output it. In the video a mistake in the T logic is caught and fixed at 11:09; if your structure looks inverted or empty, check that comparison first.
4. Make a surface with a Fog volume
- Add a Volume Builder with the volume type set to Fog, and put the Node Mesh in it.
- Use Xpresso to link the Node Mesh voxel size to the Volume Builder’s Voxel Size and Mesh Point Radius, so the points and the fog stay in step when you change the resolution.
- At this point the video catches a mistake in the T logic (11:09). Fix the comparison before you go on; you should now see the rough Gyroid structure.
- Add the original Connect boundary object to the Volume Builder as well, and set the Node Mesh’s mode in the Volume Builder list to Divide.
- Add a Fog Smooth modifier at around 50% strength. The result is a smooth Gyroid isosurface.
How to read the figure. The left side is what your Object Manager and Volume Builder panels should look like after step 4. The Xpresso graph on the right is the one link the video adds: a single voxel size value drives the Volume Builder’s Voxel Size and Mesh Point Radius, so when you change the resolution of the points, the fog keeps up. The Fog Smooth filter and the Divide mode live in the Volume Builder’s objects list, not in the Object Manager.
5. Make the Primitive and Diamond surfaces
The graph does not change. Replace the formula with the Primitive form, cos X + cos Y + cos Z, or the Diamond form, cos X cos Y cos Z minus sin X sin Y sin Z (csgrs TPMS source), and keep L and T. Changing the boundary object or the cell size gives very different looks inside the same setup.
Render dense TPMS meshes on several GPUs
A fine voxel size produces a dense mesh, and dense meshes cost VRAM. Two practical points:
- Design coarse, render fine. Keep the voxel size large while you adjust L and T, and only lower it for the final frames.
- Memory is per card. Redshift can render on every GPU in the machine, but each card holds its own copy of the scene (Maxon support). If the final mesh does not fit on one card, more cards will not fix it; a larger voxel size or a smaller boundary will.
TPMS setup checklist
Run through this before the final, fine-voxel render.
SaaS or IaaS render farm for TPMS and volume scenes?
A TPMS setup is procedural: the mesh is rebuilt from the node graph and the Volume Builder when the scene is evaluated. Any farm with your Cinema 4D version can render it. The difference is how you handle the heavy evaluation step and a mesh that may be too large for one GPU.
SaaS or IaaS for TPMS scenes
How each farm model fits a procedural Cinema 4D scene with Scene Nodes and Volumes.
| Your situation | SaaS render farm | IaaS render farm (iRender) |
|---|---|---|
| The structure is final and renders fine on your PC | A good fit: upload the scene, the farm renders the frames | Works too; you open the scene and render it yourself |
| You want to try a finer voxel size than your PC can handle | You find out after submitting whether it fits the farm’s hardware | Open the scene on a 32 GB RTX 5090 server and test the final voxel size there |
| You want to bake the mesh before rendering | Bake locally and upload the larger file | Bake on the server and render from the same drive |
| You have a deadline and need to know when rendering starts and ends | Jobs join the farm’s queue, so the start time depends on how busy the farm is; many farms sell higher-priority plans to start sooner | The server runs only your job from the moment it boots, so you control when rendering starts and can time the whole job |
Simple rule: if the scene already renders on your PC at final quality, a SaaS farm saves you the machine work. If you need more memory or processing to reach the final voxel size, a server you control lets you test it before committing.
A test workflow on an iRender server
- Upload first. Put the .c4d file on iRender Drive before you start a server; transfer and storage are free.
- Pick a server. Cinema 4D and Redshift are pre-installed. An RTX 5090 server gives 32 GB of VRAM per card for dense meshes.
- Test the voxel size. Lower the voxel size step by step and watch memory in Task Manager while the volume rebuilds.
- Render a test frame. Check the Redshift log for all GPUs and the surface at final resolution.
- Render the shot. Save frames to iRender Drive and shut the server down when the job is done; multi-GPU servers are billed per minute.
Frequently asked questions
1. What is a TPMS structure?
A triply periodic minimal surface: a surface with zero mean curvature at every point that repeats in all three directions. The Gyroid, Primitive and Diamond surfaces are the best-known examples.
2. How do you create a Gyroid in Cinema 4D?
Fill a boundary with voxel points in a Node Mesh, evaluate the Gyroid equation on each point with trigonometry nodes, keep the points within the thickness T, and turn them into a surface with a Fog Volume Builder and a Fog Smooth filter.
3. What do the L and T parameters do?
L is the size of one unit cell in each direction. T controls how thick the walls of the structure are.
4. How do I get the Primitive or Diamond surface instead?
Keep the same graph and change only the formula: cos X + cos Y + cos Z for Primitive, and cos X cos Y cos Z minus sin X sin Y sin Z for Diamond.
5. Why use a Fog volume instead of SDF?
The setup produces points, not a closed mesh. A Fog volume stores a density value for each voxel, which a smoothing filter can turn into a clean surface around those points.
6. Why does my TPMS look empty or inverted?
Check the thickness comparison first. The video corrects a mistake in the T logic; a wrong comparison keeps the wrong side of the surface.
7. Will more GPUs help with a very dense TPMS mesh?
More GPUs render faster, but each card must hold the whole scene, because Redshift does not combine GPU memory. If the mesh is too large for one card, use a larger voxel size.
Render your Cinema 4D and Redshift projects on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. Cinema 4D and Redshift are pre-installed, and your server image is saved between sessions.
Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
Two recorded Redshift runs on iRender servers:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Cinema 4D and Redshift render farm page or download the iRender GPU app.




