How to use Renderer 3D node in Oraphim

Type ID: fusion.renderer3d
Category: Utility

What this node does

The Renderer 3D 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 12 properties for this node. Its main registered inputs are Scene Geometry, Volume, Camera; its main outputs are Rendered Image. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Scene Geometry	in_scene	Geometry3D
Volume	in_volume	Volume
Camera	in_camera	Camera3D
Lights	in_light	Light3D
Material Override	in_material	Material
Background	in_background	Image

Outputs

Socket	Key	Type
Rendered Image	out_color	Image

Controls

Control	Key	Type	Group	Registry default
Enable Shadows	enableShadows	Bool	Renderer	1.0
Quality	quality	String	Renderer	Preview
Renderer	rendererBackend	String	Renderer	Auto
Path Samples	samples	Int	Quality	64.0
Volume Steps	volumeSteps	Int	Quality	96.0
Light Bounces	maxBounces	Int	Quality	6.0
Adaptive Bounce Start	russianRouletteDepth	Int	Advanced	3.0
Indirect Clamp	clampIndirect	Float	Advanced	16.0
AO Distance	aoDistance	Float	Advanced	25.0
Render Seed	renderSeed	Int	Advanced	1.0
Render Pass	renderPass	String	Output	Beauty
Transparent Background	transparentBackground	Bool	Renderer	1.0

How to use it

1. Add Renderer 3D from node search. Use fusion.renderer3d when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Scene Geometry. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Enable Shadows, Quality, Renderer first so you can see the node's effect in isolation.
4. Route Rendered Image (Image) 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 Renderer 3D. Feed a compatible source into Scene Geometry. Change Enable Shadows away from its registry default and compare the result. Connect Rendered Image 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

• Utility Effect — fusion.utilityeffect
• Camera 3D — fusion.camera
• Drop Shadow — fusion.dropshadow
• Light 3D — fusion.light
• Particle System — fusion.particle

Return to the complete Oraphim node reference.