Node reference
How to use Grid Dilate & Erode node in Oraphim
Use the Grid Dilate & Erode node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.grid_dilate_erode.
Updated August 28, 2026How to use Grid Dilate & Erode node in Oraphim
Type ID: geometry.grid_dilate_erode
Category: Transform
What this node does
Processes grid, volume, or SDF data with the Grid Dilate & Erode operation.
The current Oraphim runtime registers 5 sockets and 4 properties for this node. Its main registered inputs are Grid, Connectivity, Tiles; its main outputs are Grid. The tables below are generated from the runtime registry rather than a handwritten approximation.
Inputs
| Socket | Key | Type |
|---|---|---|
| Grid | grid |
Geometry3D |
| Connectivity | connectivity |
String |
| Tiles | tiles |
String |
| Steps | steps |
Int |
Outputs
| Socket | Key | Type |
|---|---|---|
| Grid | out_geometry |
Geometry3D |
Controls
| Control | Key | Type | Group | Registry default |
|---|---|---|---|---|
| Data Type | dataType |
String |
Node | 0.0 |
| Connectivity | connectivity |
String |
Inputs | 0.0 |
| Tiles | tiles |
String |
Inputs | 0.0 |
| Steps | steps |
Int |
Inputs | 1.0 |
How to use it
- Add Grid Dilate & Erode from node search. Use
geometry.grid_dilate_erodewhen you need the exact registry entry. - Connect a compatible
Geometry3Dsource to Grid. Add the other inputs only when the operation needs them. - Start with the registry defaults and adjust Data Type, Connectivity, Tiles first so you can see the node's effect in isolation.
- Route Grid (
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 Grid Dilate & Erode. Feed a compatible source into Grid. Change Data Type away from its registry default and compare the result. Connect 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
- Clone Elements —
geometry.clone_elements - Fillet Curve —
geometry.curve_fillet - Layout Elements —
geometry.layout_elements - Motion FX —
geometry.motion_fx - Path to Points —
geometry.path_to_points
Return to the complete Oraphim node reference.