How to use Primitive node in Oraphim

Type ID: motion.geometry.primitive
Category: Generator

What this node does

The 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 13 properties for this node. Its main registered inputs are no fixed inputs; its main outputs are Geometry, Dimension, Shape. 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
Geometry	out_geometry	Geometry3D
Dimension	out_dimension	String
Shape	out_shape	String

Controls

Control	Key	Type	Group	Registry default
Dimension	dimension	String	Primitive	3D
Shape	shape2D	String	Primitive	Rectangle
Shape	shape3D	String	Primitive	Cube
Width	width	Float	Size	2.0
Height	height	Float	Size	2.0
Depth	depth	Float	Size	2.0
Radius	radius	Float	Size	1.0
Secondary Radius	secondaryRadius	Float	Size	0.30000001192092896
Segments	segments	Int	Resolution	32.0
Rings	rings	Int	Resolution	16.0
Subdivisions	subdivisions	Int	Resolution	2.0
Segments X	segmentsX	Int	Resolution	1.0
Segments Y	segmentsY	Int	Resolution	1.0

How to use it

1. Add Primitive from node search. Use motion.geometry.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 Dimension, Shape, Shape first so you can see the node's effect in isolation.
4. Route Geometry (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 Primitive. Change Dimension away from its registry default and compare the result. Connect Geometry 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

• Curve Primitive — motion.geometry.curve_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.