Node reference

How to use Curve to Mesh node in Oraphim

Use the Curve to Mesh node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.curve_to_mesh.

Updated August 28, 2026

How to use Curve to Mesh node in Oraphim

Type ID: geometry.curve_to_mesh
Category: Transform

What this node does

Converts incoming data with the Curve to Mesh operation for use later in the graph.

The current Oraphim runtime registers 5 sockets and 2 properties for this node. Its main registered inputs are Curve, Profile Curve, Scale; its main outputs are Mesh. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Curve curve Geometry3D
Profile Curve profileCurve Geometry3D
Scale scale Float
Fill Caps fillCaps Bool

Outputs

Socket Key Type
Mesh out_geometry Geometry3D

Controls

Control Key Type Group Registry default
Scale scale Float Inputs 1.0
Fill Caps fillCaps Bool Inputs 0.0

How to use it

  1. Add Curve to Mesh from node search. Use geometry.curve_to_mesh when you need the exact registry entry.
  2. Connect a compatible Geometry3D source to Curve. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Scale, Fill Caps 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 Curve to Mesh. Feed a compatible source into Curve. Change Scale 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.

Return to the complete Oraphim node reference.