How to use Camera 3D node in Oraphim

Type ID: fusion.camera
Category: Utility

What this node does

The Camera 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 0 sockets and 19 properties for this node. Its main registered inputs are no fixed inputs; its main outputs are no fixed outputs. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

This node has no fixed input sockets in the current runtime registry.

Outputs

This node has no fixed output sockets in the current runtime registry.

Controls

Control	Key	Type	Group	Registry default
Position X	positionX	Float	Transform	0.0
Position Y	positionY	Float	Transform	0.0
Position Z	positionZ	Float	Transform	-500.0
Target X	targetX	Float	Transform	0.0
Target Y	targetY	Float	Transform	0.0
Target Z	targetZ	Float	Transform	0.0
Up X	upX	Float	Transform	0.0
Up Y	upY	Float	Transform	-1.0
Up Z	upZ	Float	Transform	0.0
Field Of View	fov	Float	Lens	50.0
Focal Length	focalLength	Float	Camera	35.0
Sensor Width	sensorWidth	Float	Lens	36.0
Sensor Height	sensorHeight	Float	Lens	24.0
Near Plane	nearPlane	Float	Clipping	10.0
Far Plane	farPlane	Float	Clipping	100000.0
Depth Of Field	depthOfField	Bool	Camera	0.0
Focus Distance	focusDistance	Float	Camera	1000.0
Aperture	aperture	Float	Camera	2.799999952316284
Blur Strength	blurStrength	Float	Camera	1.0

How to use it

1. Add Camera 3D from node search. Use fusion.camera when you need the exact registry entry.
2. Place the node as a source/context operation; it has no fixed input socket in the current registry.
3. Start with the registry defaults and adjust Position X, Position Y, Position Z first so you can see the node's effect in isolation.
4. Because there is no fixed output socket, validate the graph context or downstream resource that this node is intended to affect.
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 Camera 3D. Change Position X away from its registry default and compare the result. 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

• Drop Shadow — fusion.dropshadow
• Light 3D — fusion.light
• Renderer 3D — fusion.renderer3d
• Utility Effect — fusion.utilityeffect
• 3D Camera Tracker — fusion.cameratracker

Return to the complete Oraphim node reference.