Node reference

How to use Field Variance node in Oraphim

Use the Field Variance node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.field_variance.

Updated August 28, 2026

How to use Field Variance node in Oraphim

Type ID: geometry.field_variance
Category: Utility

What this node does

The Field Variance 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 2 properties for this node. Its main registered inputs are Group ID, Value; its main outputs are Standard Deviation, Variance. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Group ID groupId Int
Value value Float

Outputs

Socket Key Type
Standard Deviation standardDeviation Float
Variance variance Float

Controls

Control Key Type Group Registry default
Group ID groupId Int Inputs 0.0
Value value Float Inputs 0.0

How to use it

  1. Add Field Variance from node search. Use geometry.field_variance when you need the exact registry entry.
  2. Connect a compatible Int source to Group ID. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Group ID, Value first so you can see the node's effect in isolation.
  4. Route Standard Deviation (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 Field Variance. Feed a compatible source into Group ID. Change Group ID away from its registry default and compare the result. Connect Standard Deviation 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.

Return to the complete Oraphim node reference.