Node reference

How to use Active Camera node in Oraphim

Use the Active Camera node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.input_active_camera.

Updated August 28, 2026

How to use Active Camera node in Oraphim

Type ID: geometry.input_active_camera
Category: Input

What this node does

Provides active camera data to downstream geometry operations.

The current Oraphim runtime registers 2 sockets and 1 properties for this node. Its main registered inputs are Camera; its main outputs are Geometry. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Camera camera String

Outputs

Socket Key Type
Geometry out_geometry Geometry3D

Controls

Control Key Type Group Registry default
Camera camera String Inputs 0.0

How to use it

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