How to use For Each Geometry Element Output node in Oraphim

Type ID: geometry.foreach_geometry_element_output
Category: Utility

What this node does

The For Each Geometry Element Output 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 7 sockets and 1 properties for this node. Its main registered inputs are __extend__main, Geometry, __extend__generation; its main outputs are Geometry, __extend__main, Geometry. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
__extend__main	__extend__main	Metadata
Geometry	generation_0	Geometry3D
__extend__generation	__extend__generation	Metadata

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D
__extend__main	__extend__main	Metadata
Geometry	generation_0	Geometry3D
__extend__generation	__extend__generation	Metadata

Controls

Control	Key	Type	Group	Registry default
Domain	domain	Menu	Node	POINT

How to use it

1. Add For Each Geometry Element Output from node search. Use geometry.foreach_geometry_element_output when you need the exact registry entry.
2. Connect a compatible Metadata source to __extend__main. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Domain first so you can see the node's effect in isolation.
4. Route Geometry (Geometry3D) 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 For Each Geometry Element Output. Feed a compatible source into __extend__main. Change Domain 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

• Filter List — geometry.filter_list
• Get List Item — geometry.list_get_item
• List Length — geometry.list_length
• Repeat Output — geometry.repeat_output
• Simulation Output — geometry.simulation_output

Return to the complete Oraphim node reference.