Node reference
How to use Edge Paths to Curves node in Oraphim
Use the Edge Paths to Curves node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.edge_paths_to_curves.
Updated August 28, 2026How to use Edge Paths to Curves node in Oraphim
Type ID: geometry.edge_paths_to_curves
Category: Transform
What this node does
The Edge Paths to Curves node is registered in Oraphim's Transform category and performs the graph operation represented by its sockets and controls below.
The current Oraphim runtime registers 4 sockets and 2 properties for this node. Its main registered inputs are Mesh, Start Vertices, Next Vertex Index; its main outputs are Curves. The tables below are generated from the runtime registry rather than a handwritten approximation.
Inputs
| Socket | Key | Type |
|---|---|---|
| Mesh | mesh |
Geometry3D |
| Start Vertices | startVertices |
Bool |
| Next Vertex Index | nextVertexIndex |
Int |
Outputs
| Socket | Key | Type |
|---|---|---|
| Curves | out_geometry |
Geometry3D |
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
- Add Edge Paths to Curves from node search. Use
geometry.edge_paths_to_curveswhen you need the exact registry entry. - Connect a compatible
Geometry3Dsource to Mesh. Add the other inputs only when the operation needs them. - Start with the registry defaults and adjust Start Vertices, Next Vertex Index first so you can see the node's effect in isolation.
- Route Curves (
Geometry3D) 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 Edge Paths to Curves. Feed a compatible source into Mesh. Change Start Vertices away from its registry default and compare the result. Connect Curves 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
- Bevel Faces —
geometry.bevel_faces - Duplicate Elements —
geometry.duplicate_elements - Fillet Curve —
geometry.curve_fillet - Grid to Points —
geometry.grid_to_points - Instance on Points —
geometry.instance_on_points
Return to the complete Oraphim node reference.