Node reference

How to use Spiral node in Oraphim

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

Updated August 28, 2026

How to use Spiral node in Oraphim

Type ID: geometry.curve_primitive_spiral
Category: Generator

What this node does

The Spiral 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 7 sockets and 6 properties for this node. Its main registered inputs are Resolution, Rotations, Start Radius; its main outputs are Curve. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Resolution resolution Int
Rotations rotations Float
Start Radius startRadius Float
End Radius endRadius Float
Height height Float
Reverse reverse Bool

Outputs

Socket Key Type
Curve out_geometry Geometry3D

Controls

Control Key Type Group Registry default
Resolution resolution Int Inputs 32.0
Rotations rotations Float Inputs 2.0
Start Radius startRadius Float Inputs 1.0
End Radius endRadius Float Inputs 2.0
Height height Float Inputs 2.0
Reverse reverse Bool Inputs 0.0

How to use it

  1. Add Spiral from node search. Use geometry.curve_primitive_spiral when you need the exact registry entry.
  2. Connect a compatible Int source to Resolution. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Resolution, Rotations, Start Radius 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 Spiral. Feed a compatible source into Resolution. Change Resolution 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.