How to use Apply To Layer node in Oraphim

Type ID: motion.output.apply_layer
Category: Output

What this node does

The Apply To Layer node is registered in Oraphim's Output category and performs the graph operation represented by its sockets and controls below.

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

Inputs

Socket	Key	Type
Layer	in_layer	Object
Transform	in_transform	Transform
Geometry	in_geometry	Geometry3D
Metadata	in_metadata	Metadata

Outputs

Socket	Key	Type
Layer	out_layer	Object

Controls

Control	Key	Type	Group	Registry default
Mode	mode	String	Apply	0.0
Preserve User Overrides	preserveUserOverrides	Bool	Apply	1.0
Undo Transaction	createUndoTransaction	Bool	Apply	1.0

How to use it

1. Add Apply To Layer from node search. Use motion.output.apply_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 Mode, Preserve User Overrides, Undo Transaction 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 Apply To Layer. Feed a compatible source into Layer. Change Mode 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.

Related nodes

• Viewer — geometry.viewer
• Layer Input — motion.input.layer
• 2D / 3D Layer Bridge — motion.vfx.layer_bridge
• Attribute Map — motion.geometry.attribute_map
• Bar Chart Generator — motion.chart.bar

Return to the complete Oraphim node reference.