How to use Subdivision Surface node in Oraphim

Type ID: geometry.subdivision_surface
Category: Transform

What this node does

The Subdivision Surface node is registered in Oraphim's Transform category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 8 sockets and 6 properties for this node. Its main registered inputs are Mesh, Level, Edge Crease; its main outputs are Mesh. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Mesh	mesh	Geometry3D
Level	level	Int
Edge Crease	edgeCrease	Float
Vertex Crease	vertexCrease	Float
Limit Surface	limitSurface	Bool
UV Smooth	uvSmooth	Menu
Boundary Smooth	boundarySmooth	Menu

Outputs

Socket	Key	Type
Mesh	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Level	level	Int	Inputs	1.0
Edge Crease	edgeCrease	Float	Inputs	0.0
Vertex Crease	vertexCrease	Float	Inputs	0.0
Limit Surface	limitSurface	Bool	Inputs	1.0
UV Smooth	uvSmooth	Menu	Inputs	PRESERVE_BOUNDARIES
Boundary Smooth	boundarySmooth	Menu	Inputs	ALL

How to use it

1. Add Subdivision Surface from node search. Use geometry.subdivision_surface when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Mesh. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Level, Edge Crease, Vertex Crease 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 Subdivision Surface. Feed a compatible source into Mesh. Change Level 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

• Bevel Faces — geometry.bevel_faces
• Fillet Curve — geometry.curve_fillet
• Grid to Points — geometry.grid_to_points
• Merge by Distance — geometry.merge_by_distance
• Mesh Bevel — geometry.mesh_bevel

Return to the complete Oraphim node reference.