Node reference
How to use Points to SDF Grid node in Oraphim
Use the Points to SDF Grid node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.points_to_sdf_grid.
Updated August 28, 2026How to use Points to SDF Grid node in Oraphim
Type ID: geometry.points_to_sdf_grid
Category: Transform
What this node does
Converts incoming data with the Points to SDF Grid operation for use later in the graph.
The current Oraphim runtime registers 4 sockets and 2 properties for this node. Its main registered inputs are Points, Radius, Voxel Size; its main outputs are SDF Grid. The tables below are generated from the runtime registry rather than a handwritten approximation.
Inputs
| Socket | Key | Type |
|---|---|---|
| Points | points |
Geometry3D |
| Radius | radius |
Float |
| Voxel Size | voxelSize |
Float |
Outputs
| Socket | Key | Type |
|---|---|---|
| SDF Grid | out_geometry |
Grid |
Controls
| Control | Key | Type | Group | Registry default |
|---|---|---|---|---|
| Radius | radius |
Float |
Inputs | 0.5 |
| Voxel Size | voxelSize |
Float |
Inputs | 0.30000001192092896 |
How to use it
- Add Points to SDF Grid from node search. Use
geometry.points_to_sdf_gridwhen 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 Radius, Voxel Size first so you can see the node's effect in isolation.
- Route SDF Grid (
Grid) 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 SDF Grid. Feed a compatible source into Points. Change Radius away from its registry default and compare the result. Connect SDF Grid 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
- Advect Grid —
geometry.grid_advect - Bevel Faces —
geometry.bevel_faces - Clone Elements —
geometry.clone_elements - Cluster by Distance —
geometry.cluster_by_distance - Curve to Mesh —
geometry.curve_to_mesh
Return to the complete Oraphim node reference.