Node reference

How to use Curve Handle Positions node in Oraphim

Use the Curve Handle Positions node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.input_curve_handles.

Updated August 28, 2026

How to use Curve Handle Positions node in Oraphim

Type ID: geometry.input_curve_handles
Category: Input

What this node does

Provides curve handle positions data to downstream geometry operations.

The current Oraphim runtime registers 3 sockets and 1 properties for this node. Its main registered inputs are Relative; its main outputs are Left, Right. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Relative relative Bool

Outputs

Socket Key Type
Left left Vector3
Right right Vector3

Controls

Control Key Type Group Registry default
Relative relative Bool Inputs 0.0

How to use it

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