How to use Set Mesh Normal node in Oraphim

Type ID: geometry.set_mesh_normal
Category: Transform

What this node does

Changes mesh normal on incoming geometry and passes the edited result downstream.

The current Oraphim runtime registers 6 sockets and 7 properties for this node. Its main registered inputs are Mesh, Remove Custom, Edge Sharpness; 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
Remove Custom	removeCustom	Bool
Edge Sharpness	edgeSharpness	Bool
Face Sharpness	faceSharpness	Bool
Custom Normal	customNormal	Vector3

Outputs

Socket	Key	Type
Mesh	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Mode	mode	String	Node	0.0
Remove Custom	removeCustom	Bool	Inputs	1.0
Edge Sharpness	edgeSharpness	Bool	Inputs	0.0
Face Sharpness	faceSharpness	Bool	Inputs	0.0
Custom Normal X	normalX	Float	Inputs	0.0
Custom Normal Y	normalY	Float	Inputs	0.0
Custom Normal Z	normalZ	Float	Inputs	1.0

How to use it

1. Add Set Mesh Normal from node search. Use geometry.set_mesh_normal 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 Mode, Remove Custom, Edge Sharpness 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 Set Mesh Normal. Feed a compatible source into Mesh. Change Mode 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

• Bounding Box — geometry.bounding_box
• Extrude Mesh — geometry.extrude_mesh
• Instance on Points — geometry.instance_on_points
• Instances to Points — geometry.instances_to_points
• Mesh to Points — geometry.mesh_to_points

Return to the complete Oraphim node reference.