How to use Trails / Echo node in Oraphim

Type ID: motion.vfx.trails_echo
Category: Time

What this node does

The Trails / Echo 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 5 properties for this node. Its main registered inputs are Geometry, Layer; its main outputs are Geometry, Layer. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Geometry	in_geometry	Geometry3D
Layer	in_layer	Object

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D
Layer	out_layer	Object

Controls

Control	Key	Type	Group	Registry default
Samples	samples	Int	Echo	12.0
Time Offset	timeOffset	Float	Echo	-2.0
Decay	decay	Float	Echo	0.8199999928474426
Blend Mode	blendMode	String	Echo	0.0
Preserve Alpha	preserveAlpha	Bool	Echo	1.0

How to use it

1. Add Trails / Echo from node search. Use motion.vfx.trails_echo 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 Samples, Time Offset, Decay 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 Trails / Echo. Feed a compatible source into Geometry. Change Samples 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

• 2D / 3D Layer Bridge — motion.vfx.layer_bridge
• ADSR Envelope — motion.signal.envelope
• Frame Driver — motion.input.frame
• Interpolate — motion.animate.interpolate
• Loop Time — motion.time.loop

Return to the complete Oraphim node reference.