Triangulate3D

Triangulate3D is a processor rather than a generator. Its required SceneInput accepts classic Fusion scene3d from Shape3D, Text3D, imported geometry, Merge3D or another compatible 3D tool. Output remains scene3d; normal RGBA pixels appear only after Renderer3D.

Blackmagic describes the tool in unusually concise terms: Triangulate3D has no node-specific working controls and triangulates quads or convex polygons. The empty Controls tab in the bundled Resolve capture is therefore expected behavior rather than a missing Inspector.

Triangulation changes face topology rather than the intended shape. A quad gains a diagonal and becomes two triangle faces; a larger convex polygon becomes a set of triangles. If the surface is planar and downstream shading is insensitive to the diagonal, the silhouette and beauty render can look almost unchanged.

Triangulate3D is not Subdivide or Remesh. Do not present it as a way to increase geometry density: it changes the face split of existing polygons but does not automatically create a uniformly denser mesh for demanding deformation. If the source lacks enough vertices, triangulation alone does not solve that problem.

The limitation in Blackmagic's wording matters: quads or convex polygons. Do not promise automatic repair of arbitrary concave or self-intersecting n-gons, damaged mesh topology or bad imports. Those cases need separate inspection and may require cleanup in a modeling tool or another 3D operation.

The order of Triangulate3D relative to geometry processors can be part of the result. If a quad is deformed until its four vertices are no longer coplanar and a diagonal is chosen afterward, the resulting surface can differ from a pipeline where triangle topology was fixed first. 'Before or after the deformer' is therefore an A/B topology decision, not a cosmetic reorder.

This is why Triangulate3D is useful as an explicit topology boundary before a downstream operation that cares about faces. You decide where triangle primitives become explicit instead of leaving the split to a later stage in the pipeline.

With Displace3D, Bender3D and similar processors, keep two concerns separate: topology determinism and mesh density. Triangulate3D can make face structure explicit, but smooth high-amplitude deformation still depends on the number and distribution of source vertices.

Triangulate3D is not ReplaceNormals3D. A topology change can make lighting or shading reveal triangle boundaries differently, especially on non-planar geometry. If the issue looks like normals or smoothing, diagnose that separately with the appropriate downstream normals workflow.

Triangulate3D is not Weld3D either. Split vertices, seams, or nearby but disconnected points are not automatically welded because faces became triangles. Vertex welding/fracturing and face triangulation are separate topology operations.

The tool also does not create UV mapping. Existing texture coordinates remain part of the incoming geometry data, but Triangulate3D does not replace UVMap3D and exposes no planar, cylindrical or spherical mapping controls. Diagnose UV issues independently.

A classic Fusion 3D Viewer is most useful here in wireframe or another mesh-oriented display. That view exposes the difference between a quad or convex polygon and triangle faces much more clearly than a smoothly shaded surface. The tool should not be judged only from an unchanged silhouette.

If the image looks unchanged after Triangulate3D, that does not prove the tool did nothing. Planar convex faces can represent the same visible surface before and after triangulation. Validation should inspect topology and downstream behavior rather than a single RGB still.

If a visible diagonal or faceting appears after the node, do not search for a nonexistent Amount slider. Check whether the source polygon was non-planar, how downstream interpolation handles the triangles, and whether normals/smoothing are appropriate for the new face structure.

For imported geometry, a clean technical Flow is Import/Mesh source → cleanup/topology → materials/deformers → Merge3D. A named Triangulate3D node makes the exact topology boundary obvious and easy to A/B with bypass.

Do not place Triangulate3D after Renderer3D. At that point scene3d has already become a 2D image/RGBA stream and polygon topology is no longer available to normal image nodes. Both sides of Triangulate3D belong to the scene3d domain.

Do not feed MediaIn, Background or another image output into SceneInput. Even if the visual goal is 'triangles from an image', Triangulate3D processes 3D polygon geometry rather than pixels. Use an appropriate geometry workflow such as ImagePlane3D when the task is genuinely spatial.

Triangulate3D.Output can feed Transform3D, Merge3D, Renderer3D and other compatible classic Fusion 3D processors. The output is not a special triangle-stream data type; it is normal scene3d whose applicable geometry now uses triangulated faces.

A reliable diagnostic baseline is: verify the original geometry first, insert Triangulate3D at one deliberate topology boundary, compare wireframe before/after, then inspect deformation, normals, UVs and material response separately. This keeps one cause from masking another.

The bundled screenshot confirms an empty Controls tab for Triangulate3D in the project's current capture. Live Resolve 21/21.1 execution was not performed in this pass, so representative target-build mesh output and complex-face behavior remain honest live-verification items rather than claimed certification.