Node reference

How to use Layer Transform Animator node in Oraphim

Use the Layer Transform Animator node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID motion.transform.layer.

Updated August 28, 2026

How to use Layer Transform Animator node in Oraphim

Type ID: motion.transform.layer
Category: Transform

What this node does

The Layer Transform Animator node is registered in Oraphim's Transform 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 Layer, Progress; its main outputs are Layer, Transform. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Layer in_layer Object
Progress in_progress Float

Outputs

Socket Key Type
Layer out_layer Object
Transform out_transform Transform

Controls

Control Key Type Group Registry default
Space space String Target 0.0
Stagger Frames staggerFrames Float Timing 8.0
Position affectPosition Bool Channels 1.0
Scale affectScale Bool Channels 1.0
Rotation affectRotation Bool Channels 1.0
Opacity affectOpacity Bool Channels 1.0

How to use it

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