Node reference

How to use Shape to Geometry node in Oraphim

Use the Shape to Geometry node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.layer_shape_to_geometry.

Updated August 28, 2026

How to use Shape to Geometry node in Oraphim

Type ID: geometry.layer_shape_to_geometry
Category: Generator

What this node does

The Shape to Geometry node is registered in Oraphim's Generator category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 8 sockets and 7 properties for this node. Its main registered inputs are Shape, Width, Height; its main outputs are Geometry. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Shape shapeType String
Width width Float
Height height Float
Vertices vertices Int
Inner Radius innerRadius Float
Curve Radius curveRadius Float
Fill fill Bool

Outputs

Socket Key Type
Geometry out_geometry Geometry3D

Controls

Control Key Type Group Registry default
Shape shapeType String Inputs 0.0
Width width Float Inputs 2.0
Height height Float Inputs 2.0
Vertices vertices Int Inputs 64.0
Inner Radius innerRadius Float Inputs 0.5
Curve Radius curveRadius Float Inputs 0.014999999664723873
Fill fill Bool Inputs 1.0

How to use it

  1. Add Shape to Geometry from node search. Use geometry.layer_shape_to_geometry when you need the exact registry entry.
  2. Connect a compatible String source to Shape. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Shape, Width, Height 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 Shape to Geometry. Feed a compatible source into Shape. Change Shape 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.

Return to the complete Oraphim node reference.