How to use Cone node in Oraphim

Type ID: geometry.mesh_primitive_cone
Category: Generator

What this node does

The Cone 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 11 sockets and 7 properties for this node. Its main registered inputs are Vertices, Side Segments, Fill Segments; its main outputs are Mesh, Top, Bottom. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Vertices	vertices	Int
Side Segments	sideSegments	Int
Fill Segments	fillSegments	Int
Radius Top	radiusTop	Float
Radius Bottom	radiusBottom	Float
Depth	depth	Float

Outputs

Socket	Key	Type
Mesh	out_geometry	Geometry3D
Top	top	Bool
Bottom	bottom	Bool
Side	side	Bool
UV Map	uv_map	Vector3

Controls

Control	Key	Type	Group	Registry default
Vertices	vertices	Int	Inputs	32.0
Side Segments	sideSegments	Int	Inputs	1.0
Fill Segments	fillSegments	Int	Inputs	1.0
Radius Top	radiusTop	Float	Inputs	0.0
Radius Bottom	radiusBottom	Float	Inputs	1.0
Depth	depth	Float	Inputs	2.0
Fill Type	fill_type	Menu	Node	NGON

How to use it

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

Related nodes

• Arc — geometry.curve_primitive_arc
• Cylinder — geometry.mesh_primitive_cylinder
• Distribute Points on Faces — geometry.distribute_points_on_faces
• Curve Circle — geometry.curve_primitive_circle
• Distribute Points in Grid — geometry.distribute_points_in_grid

Return to the complete Oraphim node reference.