Scene assembly and lighting

1. Add an Assembler node and load one or more USD files.
2. Connect nodes in the order the scene should be prepared.
3. Add Manipulator, Creator, Shaderverse Read, or Light Linking work where needed.
4. Connect the final scene stream into a Render node.

1. Create an Assembler node from the toolbar, canvas menu, or Add Node menu.
2. Select the Assembler and use Add or Browse to choose .usd, .usda, or .usdc files.
3. Keep the main shot files in one Assembler unless a branch needs to stay separate for a clear reason.
4. Save the graph so the USD list travels with the .rj file and farm renders see the same inputs.

Tip: If a downstream node has no hierarchy, select the Assembler and confirm its file list is still valid. The downstream graph only sees USD that reaches it through connected nodes.

• Drag from an upstream output handle to a downstream input handle. The downstream node receives the composed scene stream.
• Use one readable main line for normal shots: input, edits, look, render, bake.
• Use Merge when separate branches need to feed one Render or Bake node.
• Use Backdrop, Group, and Super Group to keep large graphs readable without changing scene output.
• When debugging, select a node and check its incoming connection, bypass state, and upstream USD refs first.

The Assembler node is the entry point for USD files. The loaded file list should be saved in the graph so UI renders and farm renders see the same scene.

• Use Add to load more than one USD into the same Assembler.
• Keep paths portable through project settings when possible.
• Connect the Assembler output into downstream scene nodes or directly into a Render node.
• Automation should read the saved USD list from node data, not from the file browser state.

Manipulator nodes author changes on top of incoming USD data. Keep changes in graph nodes so the render package can explain where overrides came from.

• Use Manipulator for transforms, visibility, metadata, light attributes, and other scene overrides.
• Keep each logical change in a clear node so it can be enabled, disabled, copied, or debugged.
• Connect Manipulators in order when a shot needs a controlled override chain.

Use the Outliner to see what prims exist after the graph has composed the current node. It is the fastest way to confirm paths for cameras, lights, and CEL selections.

• Select prims to inspect their type and attributes.
• Copy useful prim paths when setting camera paths or linking rules.
• Check whether imported USD lights, cameras, and geometry are present before rendering.

Creator nodes add new scene items into the graph. Use them when a shot needs Roji-authored lights, cameras, shapes, or helpers.

• Created lights should be selectable and visible in the 3D Viewer.
• Created lights should expose lightgroup assignment in the same way imported USD lights do.
• Created cameras should be saved into the graph before farm rendering.

The Render node receives the composed scene from upstream graph nodes. Each Render node can be rendered locally or on the farm.

• Connect the scene stream into the Render node.
• Set output folder, camera, quality, AOVs, and render options on the node.
• Use the render node name or id for headless graph render.

Shaderverse Read connects a saved Shaderverse look package into the graph. The selected look should be a json file that records its source Shaderverse graph.

• Connect Shaderverse Read into the graph before the Render node.
• Use Open Shaderverse to launch Shaderverse and open the original look graph.
• Keep the look json in the project assets or looks folder.