Node reference
How to use Store Named Attribute node in Oraphim
Use the Store Named Attribute node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.store_named_attribute.
Updated August 28, 2026How to use Store Named Attribute node in Oraphim
Type ID: geometry.store_named_attribute
Category: Transform
What this node does
The Store Named 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 5 sockets and 5 properties for this node. Its main registered inputs are Geometry, Selection, Name; its main outputs are Geometry. The tables below are generated from the runtime registry rather than a handwritten approximation.
Inputs
| Socket | Key | Type |
|---|---|---|
| Geometry | geometry |
Geometry3D |
| Selection | selection |
Bool |
| Name | name |
String |
| Value | value |
Float |
Outputs
| Socket | Key | Type |
|---|---|---|
| Geometry | out_geometry |
Geometry3D |
Controls
| Control | Key | Type | Group | Registry default |
|---|---|---|---|---|
| Selection | selection |
Bool |
Inputs | 1.0 |
| Name | name |
String |
Inputs | 0.0 |
| Value | value |
Float |
Inputs | 0.0 |
| Data Type | data_type |
String |
Node | 0.0 |
| Domain | domain |
String |
Node | 0.0 |
How to use it
- Add Store Named Attribute from node search. Use
geometry.store_named_attributewhen you need the exact registry entry. - Connect a compatible
Geometry3Dsource to Geometry. Add the other inputs only when the operation needs them. - Start with the registry defaults and adjust Selection, Name, Value first so you can see the node's effect in isolation.
- Route Geometry (
Geometry3D) into a compatible downstream node, viewer, or output path. - 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 Store Named Attribute. Feed a compatible source into Geometry. Change Selection away from its registry default and compare the result. Connect Geometry 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
- Fillet Curve —
geometry.curve_fillet - Resample Curve —
geometry.resample_curve - Resample Path —
geometry.path_resample - Bevel Faces —
geometry.bevel_faces - Clone Elements —
geometry.clone_elements
Return to the complete Oraphim node reference.