Node reference
How to use Points to Vertices node in Oraphim
Use the Points to Vertices node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.points_to_vertices.
Updated August 28, 2026How to use Points to Vertices node in Oraphim
Type ID: geometry.points_to_vertices
Category: Transform
What this node does
Converts incoming data with the Points to Vertices operation for use later in the graph.
The current Oraphim runtime registers 3 sockets and 1 properties for this node. Its main registered inputs are Points, Selection; its main outputs are Mesh. The tables below are generated from the runtime registry rather than a handwritten approximation.
Inputs
| Socket | Key | Type |
|---|---|---|
| Points | points |
Geometry3D |
| Selection | selection |
Bool |
Outputs
| Socket | Key | Type |
|---|---|---|
| Mesh | out_geometry |
Geometry3D |
Controls
| Control | Key | Type | Group | Registry default |
|---|---|---|---|---|
| Selection | selection |
Bool |
Inputs | 1.0 |
How to use it
- Add Points to Vertices from node search. Use
geometry.points_to_verticeswhen you need the exact registry entry. - Connect a compatible
Geometry3Dsource to Points. Add the other inputs only when the operation needs them. - Start with the registry defaults and adjust Selection first so you can see the node's effect in isolation.
- Route Mesh (
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 Points to Vertices. Feed a compatible source into Points. Change Selection away from its registry default and compare the result. Connect Mesh 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 - Bounding Box —
geometry.bounding_box - Curve to Mesh —
geometry.curve_to_mesh - Deactivate Voxels —
geometry.grid_deactivate_voxels - Delete Geometry —
geometry.delete_geometry
Return to the complete Oraphim node reference.