How to use Repeater node in Oraphim

Type ID: geometry.motion_repeater
Category: Transform

What this node does

The Repeater 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 3 sockets and 10 properties for this node. Its main registered inputs are Geometry, 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
Count	count	Int

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Count	count	Int	Inputs	5.0
Offset X	offsetX	Float	Transform	1.0
Offset Y	offsetY	Float	Transform	0.0
Offset Z	offsetZ	Float	Transform	0.0
Rotation X	rotationX	Float	Transform	0.0
Rotation Y	rotationY	Float	Transform	0.0
Rotation Z	rotationZ	Float	Transform	0.0
Scale X	scaleX	Float	Transform	1.0
Scale Y	scaleY	Float	Transform	1.0
Scale Z	scaleZ	Float	Transform	1.0

How to use it

1. Add Repeater from node search. Use geometry.motion_repeater 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 Count, Offset X, Offset Y 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 Repeater. Feed a compatible source into Geometry. Change Count 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

• Bevel Faces — geometry.bevel_faces
• Clip Grid — geometry.grid_clip
• Clone Elements — geometry.clone_elements
• Curve to Points — geometry.curve_to_points
• Duplicate Elements — geometry.duplicate_elements

Return to the complete Oraphim node reference.