Node reference
How to use Normal node in Oraphim
Use the Normal node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.input_normal.
Updated August 28, 2026How to use Normal node in Oraphim
Type ID: geometry.input_normal
Category: Input
What this node does
Provides normal data to downstream geometry operations.
The current Oraphim runtime registers 2 sockets and 0 properties for this node. Its main registered inputs are no fixed inputs; its main outputs are Normal, True Normal. 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 |
|---|---|---|
| Normal | normal |
Vector3 |
| True Normal | trueNormal |
Vector3 |
Controls
This node has no registered editable properties; use its sockets and graph context.
How to use it
- Add Normal from node search. Use
geometry.input_normalwhen you need the exact registry entry. - Place the node as a source/context operation; it has no fixed input socket in the current registry.
- Start with the registry defaults and adjust socket/context behavior first so you can see the node's effect in isolation.
- Route Normal (
Vector3) into a compatible downstream node, viewer, or output path. - 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 Normal. Connect Normal 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
- Curve Handle Positions —
geometry.input_curve_handles - Curve Tangent —
geometry.input_tangent - Edge Vertices —
geometry.input_mesh_edge_vertices - Position —
geometry.input_position - Active Camera —
geometry.input_active_camera
Return to the complete Oraphim node reference.