Node reference

How to use Grid node in Oraphim

Use the Grid node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.mesh_primitive_grid.

Updated August 28, 2026

How to use Grid node in Oraphim

Type ID: geometry.mesh_primitive_grid
Category: Generator

What this node does

The Grid node is registered in Oraphim's Generator category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 6 sockets and 4 properties for this node. Its main registered inputs are Size X, Size Y, Vertices X; its main outputs are Mesh, UV Map. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Size X sizeX Float
Size Y sizeY Float
Vertices X verticesX Int
Vertices Y verticesY Int

Outputs

Socket Key Type
Mesh out_geometry Geometry3D
UV Map uv_map Vector3

Controls

Control Key Type Group Registry default
Size X sizeX Float Inputs 1.0
Size Y sizeY Float Inputs 1.0
Vertices X verticesX Int Inputs 3.0
Vertices Y verticesY Int Inputs 3.0

How to use it

  1. Add Grid from node search. Use geometry.mesh_primitive_grid when you need the exact registry entry.
  2. Connect a compatible Float source to Size X. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Size X, Size Y, Vertices X first so you can see the node's effect in isolation.
  4. Route Mesh (Geometry3D) into a compatible downstream node, viewer, or output path.
  5. 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. Feed a compatible source into Size X. Change Size X 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.

Return to the complete Oraphim node reference.