Node reference

How to use Blur Attribute node in Oraphim

Use the Blur Attribute node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.blur_attribute.

Updated August 28, 2026

How to use Blur Attribute node in Oraphim

Type ID: geometry.blur_attribute
Category: Transform

What this node does

The Blur Attribute 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 4 sockets and 4 properties for this node. Its main registered inputs are Value, Iterations, Weight; its main outputs are Value. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Value value Float
Iterations iterations Int
Weight weight Float

Outputs

Socket Key Type
Value outValue Float

Controls

Control Key Type Group Registry default
Value value Float Inputs 0.0
Iterations iterations Int Inputs 1.0
Weight weight Float Inputs 1.0
Data Type dataType String Node 0.0

How to use it

  1. Add Blur Attribute from node search. Use geometry.blur_attribute when you need the exact registry entry.
  2. Connect a compatible Float source to Value. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Value, Iterations, Weight 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 Blur Attribute. Feed a compatible source into Value. Change Value 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.

Return to the complete Oraphim node reference.