How to use Spring Animator node in Oraphim

Type ID: motion.animate.spring
Category: Time

What this node does

The Spring 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 4 sockets and 6 properties for this node. Its main registered inputs are Value, Frame; its main outputs are Progress, Animated Value. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Value	in_value	Float
Frame	in_frame	Int

Outputs

Socket	Key	Type
Progress	out_progress	Float
Animated Value	out_value	Float

Controls

Control	Key	Type	Group	Registry default
Start Frame	startFrame	Int	Timing	24.0
Duration	durationFrames	Int	Timing	48.0
Damping	damping	Float	Spring	16.0
Stiffness	stiffness	Float	Spring	90.0
Mass	mass	Float	Spring	0.8999999761581421
Clamp Overshoot	overshootClamp	Bool	Spring	0.0

How to use it

1. Add Spring Animator from node search. Use motion.animate.spring when you need the exact registry entry.
2. Connect a compatible Float source to Value. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Start Frame, Duration, Damping first so you can see the node's effect in isolation.
4. Route Progress (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 Spring Animator. Feed a compatible source into Value. Change Start Frame away from its registry default and compare the result. Connect Progress 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

• Stagger — motion.animate.stagger
• Interpolate — motion.animate.interpolate
• Frame Driver — motion.input.frame
• Loop Time — motion.time.loop
• Pulse Event — motion.event.pulse

Return to the complete Oraphim node reference.