Node reference

How to use Stagger node in Oraphim

Use the Stagger node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID motion.animate.stagger.

Updated August 28, 2026

How to use Stagger node in Oraphim

Type ID: motion.animate.stagger
Category: Time

What this node does

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

The current Oraphim runtime registers 3 sockets and 4 properties for this node. Its main registered inputs are Index, Count; its main outputs are Delay. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Index in_index Int
Count in_count Int

Outputs

Socket Key Type
Delay out_delay Float

Controls

Control Key Type Group Registry default
Stagger Frames staggerFrames Float Timing 10.0
Reverse reverse Bool Timing 0.0
Randomize randomize Float Timing 0.0
Seed seed Float Timing 1.0

How to use it

  1. Add Stagger from node search. Use motion.animate.stagger when you need the exact registry entry.
  2. Connect a compatible Int source to Index. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Stagger Frames, Reverse, Randomize first so you can see the node's effect in isolation.
  4. Route Delay (Float) 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 Stagger. Feed a compatible source into Index. Change Stagger Frames away from its registry default and compare the result. Connect Delay 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.