Node reference

How to use Points of Curve node in Oraphim

Use the Points of Curve node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.curve_topology_points_of_curve.

Updated August 28, 2026

How to use Points of Curve node in Oraphim

Type ID: geometry.curve_topology_points_of_curve
Category: Utility

What this node does

The Points of Curve node is registered in Oraphim's Utility category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 5 sockets and 3 properties for this node. Its main registered inputs are Curve Index, Weights, Sort Index; its main outputs are Point Index, Total. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Curve Index curveIndex Int
Weights weights Float
Sort Index sortIndex Int

Outputs

Socket Key Type
Point Index pointIndex Int
Total total Int

Controls

Control Key Type Group Registry default
Curve Index curveIndex Int Inputs 0.0
Weights weights Float Inputs 0.0
Sort Index sortIndex Int Inputs 0.0

How to use it

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