Node reference

How to use Curve of Point node in Oraphim

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

Updated August 28, 2026

How to use Curve of Point node in Oraphim

Type ID: geometry.curve_topology_curve_of_point
Category: Utility

What this node does

The Curve of Point 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 3 sockets and 1 properties for this node. Its main registered inputs are Point Index; its main outputs are Curve Index, Index in Curve. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Point Index pointIndex Int

Outputs

Socket Key Type
Curve Index curveIndex Int
Index in Curve indexInCurve Int

Controls

Control Key Type Group Registry default
Point Index pointIndex Int Inputs 0.0

How to use it

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