How to use Remesh node in Oraphim

Type ID: geometry.remesh
Category: Transform

What this node does

The Remesh node is registered in Oraphim's Transform category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 4 sockets and 3 properties for this node. Its main registered inputs are Mesh, Target Edge Length, Iterations; its main outputs are Mesh. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Mesh	mesh	Geometry3D
Target Edge Length	targetEdgeLength	Float
Iterations	iterations	Int

Outputs

Socket	Key	Type
Mesh	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Target Edge Length	targetEdgeLength	Float	Inputs	0.5
Iterations	iterations	Int	Quality	1.0
Relax	relax	Float	Quality	0.07999999821186066

How to use it

1. Add Remesh from node search. Use geometry.remesh when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Mesh. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Target Edge Length, Iterations, Relax first so you can see the node's effect in isolation.
4. Route Mesh (Geometry3D) into a compatible downstream node, viewer, or output path.
5. Preview a representative frame, change one input/control at a time, and save/reopen reusable graphs to verify persistence.

Practical example

Create a small test graph with Remesh. Feed a compatible source into Mesh. Change Target Edge Length away from its registry default and compare the result. Connect Mesh to a compatible downstream stage so the result is visible. Keeping this test graph small makes socket-type, context, and parameter mistakes easier to diagnose before the node is used in a production graph.

Troubleshooting

• If a connection is rejected, compare the exact socket data types in the tables above; Oraphim graph connections are typed.
• If the result looks unchanged, confirm this node is on the active path to the viewer/output and that the expected graph/resource is selected.
• If a control is unavailable, check required inputs and whether the property belongs to an internal or mode-dependent group.
• If a saved graph behaves differently later, reopen it and verify node identity, connections, and edited property values before rendering.

Related nodes

• Bevel Faces — geometry.bevel_faces
• Clone Elements — geometry.clone_elements
• Curve to Points — geometry.curve_to_points
• Fillet Curve — geometry.curve_fillet
• Grid to Points — geometry.grid_to_points

Return to the complete Oraphim node reference.