How to use Stable Random node in Oraphim

Type ID: motion.random.stable
Category: Utility

What this node does

The Stable Random 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 4 sockets and 5 properties for this node. Its main registered inputs are Index; its main outputs are Value, Normalized, Integer. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Index	in_index	Int

Outputs

Socket	Key	Type
Value	out_value	Float
Normalized	out_normalized	Float
Integer	out_integer	Int

Controls

Control	Key	Type	Group	Registry default
Seed	seed	Int	Random	1.0
Index	index	Int	Random	0.0
Channel	channel	Int	Random	0.0
Minimum	minimum	Float	Range	0.0
Maximum	maximum	Float	Range	1.0

How to use it

1. Add Stable Random from node search. Use motion.random.stable when you need the exact registry entry.
2. Connect a compatible Int source to Index. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Seed, Index, Channel 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 Stable Random. Feed a compatible source into Index. Change Seed 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

• Random Distribution — motion.random.distribution
• Attribute Map — motion.geometry.attribute_map
• Boolean Math — motion.logic.boolean
• Clamp — motion.value.clamp
• Compare — motion.logic.compare

Return to the complete Oraphim node reference.