How to use Array Modifier node in Oraphim

Type ID: motion.layout.blender_array
Category: Transform

What this node does

The Array Modifier node is registered in Oraphim's Transform category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 6 sockets and 25 properties for this node. Its main registered inputs are Geometry, Fit Curve, Start Cap; its main outputs are Geometry, Count. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Geometry	in_geometry	Geometry3D
Fit Curve	in_fit_curve	Path
Start Cap	in_start_cap	Geometry3D
End Cap	in_end_cap	Geometry3D

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D
Count	out_count	Int

Controls

Control	Key	Type	Group	Registry default
Fit Type	fitType	String	Fit	Fixed Count
Count	count	Int	Fit	2.0
Length	fitLength	Float	Fit	10.0
Relative Offset	relativeOffset	Bool	Offset	1.0
Relative X	relativeOffsetX	Float	Offset	1.0
Relative Y	relativeOffsetY	Float	Offset	0.0
Relative Z	relativeOffsetZ	Float	Offset	0.0
Constant Offset	constantOffset	Bool	Offset	0.0
Constant X	constantOffsetX	Float	Offset	0.0
Constant Y	constantOffsetY	Float	Offset	0.0
Constant Z	constantOffsetZ	Float	Offset	0.0
Object Offset	objectOffset	Bool	Object Offset	0.0
Translation X	objectOffsetX	Float	Object Offset	0.0
Translation Y	objectOffsetY	Float	Object Offset	0.0
Translation Z	objectOffsetZ	Float	Object Offset	0.0
Rotation X	objectRotationX	Float	Object Offset	0.0
Rotation Y	objectRotationY	Float	Object Offset	0.0
Rotation Z	objectRotationZ	Float	Object Offset	0.0
Scale X	objectScaleX	Float	Object Offset	1.0
Scale Y	objectScaleY	Float	Object Offset	1.0
Scale Z	objectScaleZ	Float	Object Offset	1.0
Merge	merge	Bool	Merge	0.0
First and Last Copies	mergeFirstLast	Bool	Merge	0.0
Distance	mergeDistance	Float	Merge	0.009999999776482582
Realize Mesh	realize	Bool	Output	1.0

How to use it

1. Add Array Modifier from node search. Use motion.layout.blender_array 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 Fit Type, Count, Length 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 Array Modifier. Feed a compatible source into Geometry. Change Fit Type 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

• Motion Array — motion.layout.repeater
• Grid Array — motion.layout.grid
• Radial Array — motion.layout.radial
• Blend Transforms — motion.transform.blend
• Compose Matrix — motion.matrix.compose

Return to the complete Oraphim node reference.