How to use Layer Input node in Oraphim

Type ID: motion.input.layer
Category: Layer

What this node does

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

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

Inputs

This node has no fixed input sockets in the current runtime registry.

Outputs

Socket	Key	Type
Layer	out_layer	Object
Geometry	out_geometry	Geometry3D
Transform	out_transform	Transform
Metadata	out_metadata	Metadata

Controls

Control	Key	Type	Group	Registry default
Target	target	String	Layer	0.0
Include 2D	include2D	Bool	Layer	1.0
Include 3D	include3D	Bool	Layer	1.0

How to use it

1. Add Layer Input from node search. Use motion.input.layer when you need the exact registry entry.
2. Place the node as a source/context operation; it has no fixed input socket in the current registry.
3. Start with the registry defaults and adjust Target, Include 2D, Include 3D 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 Input. Change Target 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

• Frame Driver — motion.input.frame
• 2D / 3D Layer Bridge — motion.vfx.layer_bridge
• Apply To Layer — motion.output.apply_layer
• Attribute Map — motion.geometry.attribute_map
• Bar Chart Generator — motion.chart.bar

Return to the complete Oraphim node reference.