How to use Motion Animator node in Oraphim

Type ID: geometry.motion_animator
Category: Time

What this node does

The Motion Animator 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 10 sockets and 8 properties for this node. Its main registered inputs are Geometry, Mode, Amplitude X; 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
Amplitude X	amplitudeX	Float
Amplitude Y	amplitudeY	Float
Amplitude Z	amplitudeZ	Float
Speed	speed	Float
Delay	delay	Float
Duration	duration	Float
Phase	phase	Float

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Mode	mode	String	Inputs	Stagger
Amplitude X	amplitudeX	Float	Inputs	0.0
Amplitude Y	amplitudeY	Float	Inputs	1.0
Amplitude Z	amplitudeZ	Float	Inputs	0.0
Speed	speed	Float	Inputs	1.0
Delay	delay	Float	Inputs	0.05000000074505806
Duration	duration	Float	Inputs	1.0
Phase	phase	Float	Inputs	0.0

How to use it

1. Add Motion Animator from node search. Use geometry.motion_animator 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, Amplitude X, Amplitude 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 Motion Animator. 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

• Timeline Elements — geometry.timeline_elements
• Timing — geometry.timing
• Clone Elements — geometry.clone_elements
• Fillet Curve — geometry.curve_fillet
• Glyphs on Elements — geometry.glyphs_on_elements

Return to the complete Oraphim node reference.