How to use Mesh Bevel node in Oraphim

Type ID: geometry.mesh_bevel
Category: Transform

What this node does

The Mesh Bevel 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 17 sockets and 11 properties for this node. Its main registered inputs are Mesh, Selection, Start Left Offset; its main outputs are Mesh, Vertex Face, Edge Face. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Mesh	mesh	Geometry3D
Selection	selection	Bool
Start Left Offset	startLeftOffset	Float
Start Right Offset	startRightOffset	Float
End Left Offset	endLeftOffset	Float
End Right Offset	endRightOffset	Float
Offset	offset	Float
Miter	miter	Bool
Spread	spread	Float
Segments	segments	Int
Shape	shape	Float
Profile	profile	Geometry3D

Outputs

Socket	Key	Type
Mesh	out_geometry	Geometry3D
Vertex Face	vertexFace	Bool
Edge Face	edgeFace	Bool
Outer Edge	outerEdge	Bool
Mid Edge	midEdge	Bool

Controls

Control	Key	Type	Group	Registry default
Selection	selection	Bool	Inputs	1.0
Affect Kind	affectKind	Menu	Node	EDGES
Start Left Offset	startLeftOffset	Float	Inputs	0.10000000149011612
Start Right Offset	startRightOffset	Float	Inputs	0.10000000149011612
End Left Offset	endLeftOffset	Float	Inputs	0.10000000149011612
End Right Offset	endRightOffset	Float	Inputs	0.10000000149011612
Miter	miter	Bool	Inputs	0.0
Spread	spread	Float	Inputs	0.10000000149011612
Offset	offset	Float	Inputs	0.10000000149011612
Segments	segments	Int	Inputs	1.0
Shape	shape	Float	Inputs	0.5

How to use it

1. Add Mesh Bevel from node search. Use geometry.mesh_bevel 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 Selection, Affect Kind, Start Left Offset 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 Mesh Bevel. Feed a compatible source into Mesh. Change Selection 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
• Random Elements — geometry.random_elements
• Resample Curve — geometry.resample_curve

Return to the complete Oraphim node reference.