How to use Layout Elements node in Oraphim

Type ID: geometry.layout_elements
Category: Transform

What this node does

The Layout Elements 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 14 sockets and 12 properties for this node. Its main registered inputs are Geometry, Mode, Count; its main outputs are Geometry. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Geometry	geometry	Geometry3D
Mode	mode	String
Count	count	Int
Columns	columns	Int
Spacing X	spacingX	Float
Spacing Y	spacingY	Float
Spacing Z	spacingZ	Float
Radius	radius	Float
Turns	turns	Float
Width	width	Float
Height	height	Float
Depth	depth	Float
Seed	seed	Int

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Mode	mode	String	Inputs	Linear
Count	count	Int	Inputs	8.0
Columns	columns	Int	Inputs	4.0
Spacing X	spacingX	Float	Inputs	1.0
Spacing Y	spacingY	Float	Inputs	1.0
Spacing Z	spacingZ	Float	Inputs	0.0
Radius	radius	Float	Inputs	2.0
Turns	turns	Float	Inputs	1.0
Width	width	Float	Inputs	4.0
Height	height	Float	Inputs	4.0
Depth	depth	Float	Inputs	0.0
Seed	seed	Int	Inputs	1.0

How to use it

1. Add Layout Elements from node search. Use geometry.layout_elements 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 Mode, Count, Columns 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 Layout Elements. Feed a compatible source into Geometry. Change Mode 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

• Clone Elements — geometry.clone_elements
• Fillet Curve — geometry.curve_fillet
• Motion FX — geometry.motion_fx
• Path to Points — geometry.path_to_points
• Resample Curve — geometry.resample_curve

Return to the complete Oraphim node reference.