Node reference

How to use Edge Angle node in Oraphim

Use the Edge Angle node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.input_mesh_edge_angle.

Updated August 28, 2026

How to use Edge Angle node in Oraphim

Type ID: geometry.input_mesh_edge_angle
Category: Input

What this node does

Provides edge angle 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 Unsigned Angle, Signed Angle. 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
Unsigned Angle unsignedAngle Float
Signed Angle signedAngle Float

Controls

This node has no registered editable properties; use its sockets and graph context.

How to use it

  1. Add Edge Angle from node search. Use geometry.input_mesh_edge_angle 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 socket/context behavior first so you can see the node's effect in isolation.
  4. Route Unsigned Angle (Float) 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 Edge Angle. Connect Unsigned Angle 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.