Node reference
How to use Mesh to Points node in Oraphim
Use the Mesh to Points node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.mesh_to_points.
Updated August 28, 2026How to use Mesh to Points node in Oraphim
Type ID: geometry.mesh_to_points
Category: Transform
What this node does
Converts incoming data with the Mesh to Points operation for use later in the graph.
The current Oraphim runtime registers 5 sockets and 6 properties for this node. Its main registered inputs are Mesh, Selection, Position; its main outputs are Points. The tables below are generated from the runtime registry rather than a handwritten approximation.
Inputs
| Socket | Key | Type |
|---|---|---|
| Mesh | mesh |
Geometry3D |
| Selection | selection |
Bool |
| Position | position |
Vector3 |
| Radius | radius |
Float |
Outputs
| Socket | Key | Type |
|---|---|---|
| Points | out_geometry |
Geometry3D |
Controls
| Control | Key | Type | Group | Registry default |
|---|---|---|---|---|
| Selection | selection |
Bool |
Inputs | 1.0 |
| Position X | positionX |
Float |
Inputs | 0.0 |
| Position Y | positionY |
Float |
Inputs | 0.0 |
| Position Z | positionZ |
Float |
Inputs | 0.0 |
| Radius | radius |
Float |
Inputs | 0.05000000074505806 |
| Mode | mode |
String |
Node | VERTICES |
How to use it
- Add Mesh to Points from node search. Use
geometry.mesh_to_pointswhen 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 Selection, Position X, Position Y first so you can see the node's effect in isolation.
- Route Points (
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 Mesh to Points. Feed a compatible source into Mesh. Change Selection away from its registry default and compare the result. Connect Points 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
- Extrude Mesh —
geometry.extrude_mesh - Instances to Points —
geometry.instances_to_points - Scale Elements —
geometry.scale_elements - Bevel Faces —
geometry.bevel_faces - Bounding Box —
geometry.bounding_box
Return to the complete Oraphim node reference.