Node reference

How to use Curve Line node in Oraphim

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

Updated August 28, 2026

How to use Curve Line node in Oraphim

Type ID: geometry.curve_primitive_line
Category: Generator

What this node does

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

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

Inputs

Socket Key Type
Start start Vector3
End end Vector3
Direction direction Vector3
Length length Float

Outputs

Socket Key Type
Curve out_geometry Geometry3D

Controls

Control Key Type Group Registry default
Mode mode String Node 0.0
Start X startX Float Inputs 0.0
Start Y startY Float Inputs 0.0
Start Z startZ Float Inputs 0.0
End X endX Float Inputs 0.0
End Y endY Float Inputs 0.0
End Z endZ Float Inputs 1.0
Direction X directionX Float Inputs 0.0
Direction Y directionY Float Inputs 0.0
Direction Z directionZ Float Inputs 1.0
Length length Float Inputs 1.0

How to use it

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