How to use Radial Array node in Oraphim

Type ID: motion.layout.radial
Category: Generator

What this node does

The Radial Array 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 4 sockets and 22 properties for this node. Its main registered inputs are Geometry; its main outputs are Instances, Count, Metadata. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Geometry	in_geometry	Geometry3D

Outputs

Socket	Key	Type
Instances	out_geometry	Geometry3D
Count	out_count	Int
Metadata	out_metadata	Metadata

Controls

Control	Key	Type	Group	Registry default
Copies	count	Int	Radial	12.0
Axis Plane	axis	String	Radial	XY
Primary Radius	radius	Float	Radial	4.0
Secondary Radius	radiusSecondary	Float	Radial	4.0
Spiral Radius Step	radiusStep	Float	Radial	0.0
Axis Step	axialStep	Float	Radial	0.0
Start Angle	startAngle	Float	Angles	0.0
Arc Angle	arcAngle	Float	Angles	360.0
Close Loop	closeLoop	Bool	Angles	1.0
Face Center	faceCenter	Bool	Orientation	1.0
Orientation Offset	rotationOffset	Float	Orientation	0.0
Base Rotation X	rotationX	Float	Orientation	0.0
Base Rotation Y	rotationY	Float	Orientation	0.0
Base Rotation Z	rotationZ	Float	Orientation	0.0
Center X	centerX	Float	Center	0.0
Center Y	centerY	Float	Center	0.0
Center Z	centerZ	Float	Center	0.0
Scale Step	scaleStep	Float	Scale	0.0
Angle Jitter	randomAngle	Float	Random	0.0
Radius Jitter	randomRadius	Float	Random	0.0
Scale Jitter	randomScale	Float	Random	0.0
Seed	seed	Int	Random	1.0

How to use it

1. Add Radial Array from node search. Use motion.layout.radial when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Geometry. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Copies, Axis Plane, Primary Radius first so you can see the node's effect in isolation.
4. Route Instances (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 Radial Array. Feed a compatible source into Geometry. Change Copies away from its registry default and compare the result. Connect Instances 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

• Grid Array — motion.layout.grid
• Motion Array — motion.layout.repeater
• Array Modifier — motion.layout.blender_array
• Bar Chart Generator — motion.chart.bar
• Data Chart — motion.chart.data

Return to the complete Oraphim node reference.