Triangulate 3D Node

Triangulation is a topological operation: any polygon with more than 3 sides is broken down into triangles. The look of the mesh doesn't change (it is the same surface), but its internal structure becomes uniform.

It is a simple pass-through node: no controls, no settings - it is either on or off. Sometimes essential in a pipeline, often invisible.

• Effects Library: Tools > 3D > Triangulate 3D
• Quick add: right-click in the Node Editor → Add Tool > 3D > Triangulate 3D

Three common reasons to use it:

1. Preparing a mesh before deformation - Displace 3D, Custom Vertex 3D and the other deformation nodes work per vertex. On a non-triangulated quad, the deformation can create a bad twist (the 4 points of a quad are no longer coplanar after deformation). Triangulating first avoids this trap.
2. Compatibility with some workflows - a few renderers or exporters prefer (or require) triangulated meshes. Inserting a Triangulate 3D beforehand removes any surprises.
3. Topology debugging - viewing a triangulated mesh in wireframe helps you understand its internal structure, which is useful to diagnose shading issues.

• SceneInput (orange) - required. Mesh or 3D scene to triangulate. Only objects with polygon geometry are affected; cameras and lights pass through unchanged.

Insert Triangulate 3D after the geometry source that needs it and before the node that requires triangulation (Displace, exporter, etc.).

FBX Mesh 3D → Triangulate 3D → Displace 3D → Merge 3D

No interactive controls. The node triangulates automatically as soon as it is in the stream. Nothing to adjust.

• Before a Displace 3D - an imported FBX mesh can contain quads. A Displace applied to it gives a "zigzag" look along the quad diagonals. Triangulate first → each triangle is deformed independently, with no twist.
• Before exporting to a strict OBJ exporter - some engines or tools only accept triangles. A Triangulate before the FBX Exporter 3D guarantees compatibility.
• Normalizing a mixed asset - an FBX that mixes quads and triangles becomes uniform after Triangulate → more predictable in the downstream pipeline.
• Wireframe low-poly look - triangulating a low-poly mesh and rendering it in wireframe gives a distinct "geometric" look, with every diagonal visible.
• Shading glitch workaround - if you see shading artifacts on non-planar polygons (twisted quads), triangulating splits them into flat triangles that render correctly.

• No visual impact on its own - a triangulated mesh renders exactly like its non-triangulated version. The impact comes from the downstream nodes (deformation, export).
• No going back - triangulation can't be undone in the stream. If you need the original quad mesh further down, keep a non-triangulated branch in parallel.
• Doubles the face count - a 100% quad mesh becomes 200% triangles. On very heavy scenes, this can affect rendering.
• Typical pairing with Replace Normals - after Triangulate, the normals may need recomputing (especially if the original quads had smooth groups). Chain a Replace Normals 3D if the shading looks faceted.
• Useful on Alembic meshes - Alembic caches often store quads. A Triangulate before Displace or Custom Vertex guarantees a clean deformation.
• Useless on Fusion primitives (Shape 3D, Cube 3D), which are already triangulated internally - it adds nothing but noise to the graph.

The Settings tab has the controls shared by 3D nodes.