Node reference

How to use Arc node in Oraphim

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

Updated August 28, 2026

How to use Arc node in Oraphim

Type ID: geometry.curve_primitive_arc
Category: Generator

What this node does

The Arc 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 14 sockets and 17 properties for this node. Its main registered inputs are Resolution, Start, Middle; its main outputs are Curve, Center, Normal. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Resolution resolution Int
Start start Vector3
Middle middle Vector3
End end Vector3
Radius radius Float
Start Angle startAngle Float
Sweep Angle sweepAngle Float
Offset Angle offsetAngle Float
Connect Center connectCenter Bool
Invert Arc invertArc Bool

Outputs

Socket Key Type
Curve out_geometry Geometry3D
Center center Vector3
Normal normal Vector3
Radius radiusOut Float

Controls

Control Key Type Group Registry default
Mode mode String Node 0.0
Resolution resolution Int Inputs 16.0
Start X startX Float Inputs -1.0
Start Y startY Float Inputs 0.0
Start Z startZ Float Inputs 0.0
Middle X middleX Float Inputs 0.0
Middle Y middleY Float Inputs 2.0
Middle Z middleZ Float Inputs 0.0
End X endX Float Inputs 1.0
End Y endY Float Inputs 0.0
End Z endZ Float Inputs 0.0
Radius radius Float Inputs 1.0
Start Angle startAngle Float Inputs 0.0
Sweep Angle sweepAngle Float Inputs 5.4977898597717285
Offset Angle offsetAngle Float Inputs 0.0
Connect Center connectCenter Bool Inputs 0.0
Invert Arc invertArc Bool Inputs 0.0

How to use it

  1. Add Arc from node search. Use geometry.curve_primitive_arc when you need the exact registry entry.
  2. Connect a compatible Int source to Resolution. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Mode, Resolution, Start X first so you can see the node's effect in isolation.
  4. Route Curve (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 Arc. Feed a compatible source into Resolution. Change Mode away from its registry default and compare the result. Connect Curve 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.