How to use Bézier Segment node in Oraphim

Type ID: geometry.curve_primitive_bezier_segment
Category: Generator

What this node does

The Bézier Segment 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 6 sockets and 14 properties for this node. Its main registered inputs are Resolution, Start, Start Handle; 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
Start	start	Vector3
Start Handle	startHandle	Vector3
End Handle	endHandle	Vector3
End	end	Vector3

Outputs

Socket	Key	Type
Curve	out_geometry	Geometry3D

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
Start Handle X	startHandleX	Float	Inputs	-0.5
Start Handle Y	startHandleY	Float	Inputs	0.5
Start Handle Z	startHandleZ	Float	Inputs	0.0
End Handle X	endHandleX	Float	Inputs	0.0
End Handle Y	endHandleY	Float	Inputs	0.0
End Handle Z	endHandleZ	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

How to use it

1. Add Bézier Segment from node search. Use geometry.curve_primitive_bezier_segment 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 Bézier Segment. 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
• Cube — geometry.mesh_primitive_cube
• Curve Circle — geometry.curve_primitive_circle
• Cylinder — geometry.mesh_primitive_cylinder

Return to the complete Oraphim node reference.