How to use Torus Knot node in Oraphim

Type ID: geometry.curve_primitive_torus_knot
Category: Generator

What this node does

The Torus Knot 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 9 sockets and 8 properties for this node. Its main registered inputs are Resolution, Major Radius, Knot Radius; its main outputs are Curve. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Resolution	resolution	Int
Major Radius	majorRadius	Float
Knot Radius	minorRadius	Float
Loops	p	Int
Twists	q	Int
Depth Scale	depthScale	Float
Phase	phase	Float
Reverse	reverse	Bool

Outputs

Socket	Key	Type
Curve	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Resolution	resolution	Int	Quality	384.0
Major Radius	majorRadius	Float	Knot	2.3499999046325684
Knot Radius	minorRadius	Float	Knot	0.9200000166893005
Loops	p	Int	Topology	2.0
Twists	q	Int	Topology	3.0
Depth Scale	depthScale	Float	Knot	1.0
Phase	phase	Float	Knot	0.0
Reverse	reverse	Bool	Topology	0.0

How to use it

1. Add Torus Knot from node search. Use geometry.curve_primitive_torus_knot 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 Resolution, Major Radius, Knot Radius 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 Torus Knot. Feed a compatible source into Resolution. Change Resolution 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 on Faces — geometry.distribute_points_on_faces
• Shape to Geometry — geometry.layer_shape_to_geometry

Return to the complete Oraphim node reference.