Node reference

How to use UV Sphere node in Oraphim

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

Updated August 28, 2026

How to use UV Sphere node in Oraphim

Type ID: geometry.mesh_primitive_uv_sphere
Category: Generator

What this node does

The UV Sphere 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 3 properties for this node. Its main registered inputs are Segments, Rings, Radius; 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
Segments segments Int
Rings rings Int
Radius radius Float

Outputs

Socket Key Type
Mesh out_geometry Geometry3D
UV Map uv_map Vector3

Controls

Control Key Type Group Registry default
Segments segments Int Inputs 32.0
Rings rings Int Inputs 16.0
Radius radius Float Inputs 1.0

How to use it

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