Node reference

How to use Torus node in Oraphim

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

Updated August 28, 2026

How to use Torus node in Oraphim

Type ID: geometry.mesh_primitive_torus
Category: Generator

What this node does

The Torus 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 4 properties for this node. Its main registered inputs are Major Radius, Minor Radius, Major Segments; its main outputs are Mesh. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Major Radius majorRadius Float
Minor Radius minorRadius Float
Major Segments majorSegments Int
Minor Segments minorSegments Int

Outputs

Socket Key Type
Mesh out_geometry Geometry3D

Controls

Control Key Type Group Registry default
Major Radius majorRadius Float Inputs 1.0
Minor Radius minorRadius Float Inputs 0.25
Major Segments majorSegments Int Quality 48.0
Minor Segments minorSegments Int Quality 12.0

How to use it

  1. Add Torus from node search. Use geometry.mesh_primitive_torus when you need the exact registry entry.
  2. Connect a compatible Float source to Major Radius. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Major Radius, Minor Radius, Major Segments 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 Torus. Feed a compatible source into Major Radius. Change Major Radius 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.