Node reference

How to use Bounding Box node in Oraphim

Use the Bounding Box node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.bounding_box.

Updated August 28, 2026

How to use Bounding Box node in Oraphim

Type ID: geometry.bounding_box
Category: Transform

What this node does

The Bounding Box 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 1 properties for this node. Its main registered inputs are Geometry, Use Radius; its main outputs are Bounding Box, Min, Max. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Geometry geometry Geometry3D
Use Radius useRadius Bool

Outputs

Socket Key Type
Bounding Box boundingBox Geometry3D
Min min Vector3
Max max Vector3

Controls

Control Key Type Group Registry default
Use Radius useRadius Bool Inputs 1.0

How to use it

  1. Add Bounding Box from node search. Use geometry.bounding_box when you need the exact registry entry.
  2. Connect a compatible Geometry3D source to Geometry. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Use Radius first so you can see the node's effect in isolation.
  4. Route Bounding Box (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 Bounding Box. Feed a compatible source into Geometry. Change Use Radius away from its registry default and compare the result. Connect Bounding Box 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.