Node reference

How to use Mesh Line node in Oraphim

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

Updated August 28, 2026

How to use Mesh Line node in Oraphim

Type ID: geometry.mesh_primitive_line
Category: Generator

What this node does

The Mesh Line 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 5 sockets and 10 properties for this node. Its main registered inputs are Count, Resolution, Start Location; its main outputs are Mesh. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Count count Int
Resolution resolution Float
Start Location startLocation Vector3
Offset offset Vector3

Outputs

Socket Key Type
Mesh out_geometry Geometry3D

Controls

Control Key Type Group Registry default
Count count Int Inputs 10.0
Resolution resolution Float Inputs 1.0
Start Location X startX Float Inputs 0.0
Start Location Y startY Float Inputs 0.0
Start Location Z startZ Float Inputs 0.0
Offset X offsetX Float Inputs 0.0
Offset Y offsetY Float Inputs 0.0
Offset Z offsetZ Float Inputs 1.0
Mode mode Menu Node OFFSET
Count Mode count_mode Menu Node TOTAL

How to use it

  1. Add Mesh Line from node search. Use geometry.mesh_primitive_line when you need the exact registry entry.
  2. Connect a compatible Int source to Count. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Count, Resolution, Start Location 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 Mesh Line. Feed a compatible source into Count. Change Count 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.