Node reference

How to use Edge Paths to Selection node in Oraphim

Use the Edge Paths to Selection node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.edge_paths_to_selection.

Updated August 28, 2026

How to use Edge Paths to Selection node in Oraphim

Type ID: geometry.edge_paths_to_selection
Category: Utility

What this node does

The Edge Paths to Selection node is registered in Oraphim's Utility category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 3 sockets and 2 properties for this node. Its main registered inputs are Start Vertices, Next Vertex Index; its main outputs are Selection. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Start Vertices startVertices Bool
Next Vertex Index nextVertexIndex Int

Outputs

Socket Key Type
Selection selection Bool

Controls

Control Key Type Group Registry default
Start Vertices startVertices Bool Inputs 0.0
Next Vertex Index nextVertexIndex Int Inputs 0.0

How to use it

  1. Add Edge Paths to Selection from node search. Use geometry.edge_paths_to_selection when you need the exact registry entry.
  2. Connect a compatible Bool source to Start Vertices. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Start Vertices, Next Vertex Index first so you can see the node's effect in isolation.
  4. Route Selection (Bool) 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 Paths to Selection. Feed a compatible source into Start Vertices. Change Start Vertices away from its registry default and compare the result. Connect Selection 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.