Node reference

How to use Points to Curves node in Oraphim

Use the Points to Curves node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.points_to_curves.

Updated August 28, 2026

How to use Points to Curves node in Oraphim

Type ID: geometry.points_to_curves
Category: Transform

What this node does

Converts incoming data with the Points to Curves operation for use later in the graph.

The current Oraphim runtime registers 4 sockets and 2 properties for this node. Its main registered inputs are Points, Curve Group ID, Weight; its main outputs are Curves. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Points points Geometry3D
Curve Group ID curveGroupId Int
Weight weight Float

Outputs

Socket Key Type
Curves out_geometry Geometry3D

Controls

Control Key Type Group Registry default
Curve Group ID curveGroupId Int Inputs 0.0
Weight weight Float Inputs 0.0

How to use it

  1. Add Points to Curves from node search. Use geometry.points_to_curves when you need the exact registry entry.
  2. Connect a compatible Geometry3D source to Points. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Curve Group ID, Weight first so you can see the node's effect in isolation.
  4. Route Curves (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 Points to Curves. Feed a compatible source into Points. Change Curve Group ID away from its registry default and compare the result. Connect Curves 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.