How to use Procedural Noise node in Oraphim

Type ID: motion.noise.procedural
Category: Utility

What this node does

The Procedural Noise node is registered in Oraphim's Utility 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 Position, Time; its main outputs are Value, Normalized, Gradient. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Position	in_position	Vector3
Time	in_time	Float

Outputs

Socket	Key	Type
Value	out_value	Float
Normalized	out_normalized	Float
Gradient	out_gradient	Vector3
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Mode	mode	String	Noise	fBm
Seed	seed	Int	Noise	1.0
Frequency	frequency	Float	Noise	1.0
Octaves	octaves	Int	Fractal	5.0
Lacunarity	lacunarity	Float	Fractal	2.0
Gain	gain	Float	Fractal	0.5
Amplitude	amplitude	Float	Output	1.0
Position X	x	Float	Position	0.0
Position Y	y	Float	Position	0.0
Position Z	z	Float	Position	0.0
Offset X	offsetX	Float	Offset	0.0
Offset Y	offsetY	Float	Offset	0.0
Offset Z	offsetZ	Float	Offset	0.0
Animation Rate	animationRate	Float	Animation	0.0

How to use it

1. Add Procedural Noise from node search. Use motion.noise.procedural when you need the exact registry entry.
2. Connect a compatible Vector3 source to Position. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Mode, Seed, Frequency first so you can see the node's effect in isolation.
4. Route Value (Float) 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 Procedural Noise. Feed a compatible source into Position. Change Mode away from its registry default and compare the result. Connect Value 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

• Boolean Math — motion.logic.boolean
• Clamp — motion.value.clamp
• Compare — motion.logic.compare
• Curve Map — motion.value.curve
• Formula — motion.expression.formula

Return to the complete Oraphim node reference.