How to use 2D / 3D Layer Bridge node in Oraphim

Type ID: motion.vfx.layer_bridge
Category: Layer

What this node does

The 2D / 3D Layer Bridge 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 Layer, Geometry; its main outputs are Layer, Geometry. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Layer	in_layer	Object
Geometry	in_geometry	Geometry3D

Outputs

Socket	Key	Type
Layer	out_layer	Object
Geometry	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Space	space	String	Layer	0.0
Preserve Layer Transform	preserveLayerTransform	Bool	Layer	1.0
Camera Aware	cameraAware	Bool	3D	1.0

How to use it

1. Add 2D / 3D Layer Bridge from node search. Use motion.vfx.layer_bridge 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, Preserve Layer Transform, Camera Aware 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 2D / 3D Layer Bridge. 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.

Related nodes

• Trails / Echo — motion.vfx.trails_echo
• Layer Input — motion.input.layer
• Apply To Layer — motion.output.apply_layer
• Array Modifier — motion.layout.blender_array
• Attribute Map — motion.geometry.attribute_map

Return to the complete Oraphim node reference.