How to use Curve Circle node in Oraphim

Type ID: geometry.curve_primitive_circle
Category: Generator

What this node does

The Curve Circle 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 7 sockets and 12 properties for this node. Its main registered inputs are Resolution, Point 1, Point 2; its main outputs are Curve, Center. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Resolution	resolution	Int
Point 1	point1	Vector3
Point 2	point2	Vector3
Point 3	point3	Vector3
Radius	radius	Float

Outputs

Socket	Key	Type
Curve	out_geometry	Geometry3D
Center	center	Vector3

Controls

Control	Key	Type	Group	Registry default
Mode	mode	String	Node	0.0
Resolution	resolution	Int	Inputs	32.0
Point 1 X	point1X	Float	Inputs	-1.0
Point 1 Y	point1Y	Float	Inputs	0.0
Point 1 Z	point1Z	Float	Inputs	0.0
Point 2 X	point2X	Float	Inputs	0.0
Point 2 Y	point2Y	Float	Inputs	1.0
Point 2 Z	point2Z	Float	Inputs	0.0
Point 3 X	point3X	Float	Inputs	1.0
Point 3 Y	point3Y	Float	Inputs	0.0
Point 3 Z	point3Z	Float	Inputs	0.0
Radius	radius	Float	Inputs	1.0

How to use it

1. Add Curve Circle from node search. Use geometry.curve_primitive_circle 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, Point 1 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 Curve Circle. 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.

Related nodes

• Arc — geometry.curve_primitive_arc
• Cone — geometry.mesh_primitive_cone
• Cylinder — geometry.mesh_primitive_cylinder
• Distribute Points in Grid — geometry.distribute_points_in_grid
• Distribute Points in Volume — geometry.distribute_points_in_volume

Return to the complete Oraphim node reference.