How to use Curve Primitive node in Oraphim

Type ID: motion.geometry.curve_primitive
Category: Generator

What this node does

The Curve Primitive 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 3 sockets and 16 properties for this node. Its main registered inputs are no fixed inputs; its main outputs are Curve, Curve, Curve Type. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

This node has no fixed input sockets in the current runtime registry.

Outputs

Socket	Key	Type
Curve	out_geometry	Geometry3D
Curve	out_curve	Curve
Curve Type	out_shape	String

Controls

Control	Key	Type	Group	Registry default
Curve Type	shape	String	Curve	Line
Start X	startX	Float	Line	-1.0
Start Y	startY	Float	Line	0.0
Start Z	startZ	Float	Line	0.0
End X	endX	Float	Line	1.0
End Y	endY	Float	Line	0.0
End Z	endZ	Float	Line	0.0
Outer Radius	radius	Float	Shape	1.0
Inner Radius	innerRadius	Float	Shape	0.44999998807907104
Star Points	points	Int	Star	5.0
Turns	turns	Float	Spiral	3.0
Knot P	knotP	Int	Torus Knot	2.0
Knot Q	knotQ	Int	Torus Knot	3.0
Vertical Scale	verticalScale	Float	Torus Knot	1.0
Resolution	resolution	Int	Resolution	64.0
Rotation	rotation	Float	Shape	0.0

How to use it

1. Add Curve Primitive from node search. Use motion.geometry.curve_primitive when you need the exact registry entry.
2. Place the node as a source/context operation; it has no fixed input socket in the current registry.
3. Start with the registry defaults and adjust Curve Type, 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 Primitive. Change Curve Type 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.

Related nodes

• Primitive — motion.geometry.primitive
• Attribute Map — motion.geometry.attribute_map
• Bar Chart Generator — motion.chart.bar
• Data Chart — motion.chart.data
• Grid Array — motion.layout.grid

Return to the complete Oraphim node reference.