Node reference
How to use Advect Grid node in Oraphim
Use the Advect Grid node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.grid_advect.
Updated August 28, 2026How to use Advect Grid node in Oraphim
Type ID: geometry.grid_advect
Category: Transform
What this node does
Processes grid, volume, or SDF data with the Advect Grid operation.
The current Oraphim runtime registers 5 sockets and 3 properties for this node. Its main registered inputs are Geometry, Offset X, Offset Y; its main outputs are Geometry. The tables below are generated from the runtime registry rather than a handwritten approximation.
Inputs
| Socket | Key | Type |
|---|---|---|
| Geometry | geometry |
Geometry3D |
| Offset X | offsetX |
Float |
| Offset Y | offsetY |
Float |
| Offset Z | offsetZ |
Float |
Outputs
| Socket | Key | Type |
|---|---|---|
| Geometry | out_geometry |
Geometry3D |
Controls
| Control | Key | Type | Group | Registry default |
|---|---|---|---|---|
| Offset X | offsetX |
Float |
Inputs | 1.0 |
| Offset Y | offsetY |
Float |
Inputs | 0.0 |
| Offset Z | offsetZ |
Float |
Inputs | 0.0 |
How to use it
- Add Advect Grid from node search. Use
geometry.grid_advectwhen you need the exact registry entry. - Connect a compatible
Geometry3Dsource to Geometry. Add the other inputs only when the operation needs them. - Start with the registry defaults and adjust Offset X, Offset Y, Offset Z first so you can see the node's effect in isolation.
- Route Geometry (
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 Advect Grid. Feed a compatible source into Geometry. Change Offset X away from its registry default and compare the result. Connect Geometry 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 - Clone Elements —
geometry.clone_elements - Cluster by Distance —
geometry.cluster_by_distance - Curve to Mesh —
geometry.curve_to_mesh - Curve to Points —
geometry.curve_to_points
Return to the complete Oraphim node reference.