Node reference

How to use Repeat Input node in Oraphim

Use the Repeat Input node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.repeat.

Updated August 28, 2026

How to use Repeat Input node in Oraphim

Type ID: geometry.repeat
Category: Utility

What this node does

The Repeat Input node is registered in Oraphim's Utility category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 4 sockets and 2 properties for this node. Its main registered inputs are Geometry, Iterations, Selection; 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
Iterations iterations Int
Selection selection Bool

Outputs

Socket Key Type
Geometry out_geometry Geometry3D

Controls

Control Key Type Group Registry default
Iterations iterations Int Inputs 1.0
Selection selection Bool Inputs 1.0

How to use it

  1. Add Repeat Input from node search. Use geometry.repeat 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 Iterations, Selection 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 Repeat Input. Feed a compatible source into Geometry. Change Iterations 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.

Return to the complete Oraphim node reference.