[FREE-BETA] Scene Assembler — Node-Based Scene Assembly & Render Queue for Blender 5.1+

Scene Assembler — Node-Based Scene Assembly & Render Queue for Blender 5.1+

[Download link] · Scene Assembler_52_v002
Docs - Addon Documentation
Discord server - Scene Assembler Discord server


What is Scene Assembler?

Scene Assembler is a Blender addon that lets you build complex multi-layer render pipelines through a node editor, then send them to a local render queue — all without leaving Blender.

The core idea: instead of manually duplicating scenes, toggling visibility, and switching cameras for every render variation, you wire it up once as a node graph. Collections come in, overrides are layered on top, and render jobs go out. The queue manager handles the rest while you keep working.

It also adds a lot of override functionality that just isn’t present in the default Blender workflow.

It started as a tool to solve my own production headaches — managing dozens of render variations across multiple scenes was becoming unworkable with vanilla Blender. After months of development and several weeks of real-world production testing, it’s now open for anyone to try.


Highlights

Assembly
Wire collections into view layers visually. Connect sources (current file or external .blend, Linked or Appended), route through View Layer nodes, and into Scene nodes — each with independent output settings. A Scheduler node queues or renders all connected scenes in one click.

Marker-aware scene import
Already using Blender’s own markers to switch cameras mid-animation? Create from Scene detects them automatically and offers to convert your existing setup into a ready-to-render node graph in one click — either a Camera Sequence node (single shared scene, camera switches exactly as your markers already do) or a Timeline node (a separate scene per camera segment, each with its own overrides and render settings). Both stay in sync with the real timeline afterward — Sync to Scene / Sync from Scene let you keep editing visually, in either direction, any time.

Native multi-view-layer rendering
When the view layers under a Scene node share camera, world, and render settings with no per-object overrides, Scene Assembler renders them as one native Blender multi-view-layer pass instead of N separate throwaway scenes — a real speedup on heavy scenes, since the expensive BVH build / shader compile only happens once instead of once per layer. Full support for Cryptomatte, AOVs, and light groups in the merged path.

Per-layer overrides
Every override is non-destructive and isolated to its view layer: transform, shader/material, visibility, light properties, animation, world/HDRI, camera, render settings, render passes, and arbitrary RNA properties. Per-pass file format overrides let you output EXR multilayer for compositing passes and PNG for beauty in the same job.

Queue manager
Local render queue with pause, resume, reorder, delete, priority ordering, and auto-retry on crash (with same-frame detection to prevent loops). Run Now jumps a job to the front without losing the queue. ETA display tracks progress. A web UI is accessible from a browser while renders run.

Camera Burst
Drop a collection of cameras into a Scene node and render one still per camera automatically — no manual camera switching, no duplicated jobs. The preview scene places timeline markers at frames 1–N so you can scrub between angles live in the viewport.

Preview scene
Build Preview Scene creates a preview scene in Blender to check the node graph as a normal Blender scene.

Output control
Token-based filenames ({scene}_{layer}_{camera}_{frame}), tree-wide defaults via an Output Defaults node, selective per-scene overrides for path, format, resolution, and frame range.

Documentation
Full documentation site covering every node, the queue manager, and advanced workflows.


Known Limitations

These are real constraints, not bugs — worth knowing before you test:

  • Blender 5.1+ only. No plans to backport.
  • Preview scene is a simplified view. Any override that isn’t possible in vanilla Blender won’t be present in the preview scene. Actual renders are always correct.
  • No network rendering support yet. Local queue only. Flamenco integration is planned but not started.
  • Freestyle and Grease Pencil settings have limited support — basic flags work, advanced options are still alpha.
  • Overrides on Linked external collections don’t work yet. Append mode supports the full override system; Linked collections don’t (Blender’s own data-linking model requires Library Overrides for this, which isn’t implemented yet). This is caught cleanly with a clear warning before render, not a crash — but it doesn’t apply. Planned, not near-term.
  • No multi-scene/multi-view-layer compositing. A job’s compositor tree can reference exactly one Render Layers node.

Open Beta — free to use, no application

The beta is now a straight, open download — no forms, no DMs, nothing to apply for. Grab it and use it.

What this means:

  • Free to use in full, including production work, for the duration of the beta.
  • A commercial license will be required once Scene Assembler goes public.
  • The beta will end as soon as I feel the addon is solid enough — I hope in about a month or so.

Join the Discord: Scene Assembler Discord server — not required to use the addon, but it’s where I’m posting updates, taking bug reports, and where you can ask questions directly. If you hit something broken or confusing, that’s the fastest way to reach me.


Requirements

  • Blender 5.1 or later
  • Windows, macOS, and Linux are all welcome — the addon has been developed and tested on Windows, so reports from other platforms are especially valuable

Looking forward to hearing what you think — and to the bugs you’ll inevitably find that I haven’t! If you’ve ever wished Blender had a better way to manage complex multi-scene files, give it a try.

4 Likes

Hey Bernardo, great to see this. I want to test it. Will DM you!

1 Like

new features highlight video:

Also added in the main opening post.

1 Like

Scene Assembler is now a free, open beta — no application needed.

A while back I posted here asking for 10 beta testers to apply via DM. That approach didn’t really work — so I’m dropping the gate entirely. Download it, use it, no forms.

**What’s new since the original post:**

- **Marker-aware scene import** — if you’re already using Blender’s markers to switch cameras, Create from Scene now converts that setup into a ready-to-render node graph in one click, either as a Camera Sequence (single shared scene) or a Timeline (separate scene per camera) — and both stay editable afterward, synced back and forth with the real timeline markers.

- **Native multi-view-layer rendering** — view layers that share camera/world/render settings now render together as one native Blender pass instead of N separate scenes, meaningfully faster on heavy files. Full Cryptomatte/AOV/light-group support included.

- **External collections** can now be Linked or Appended, your choice, per node.

- A long list of smaller fixes and polish from several weeks of real production testing.

**BETA:**

- Free to use in full — including real production work — for the beta period.

- A license will be required once it goes public.

- The beta will end as soon as I feel the addon is solid enough. I hope in about a month or so.

**Discord:** Scene assembler discord server — this is where I’m posting updates and taking bug reports directly. Not required to use the addon, just the fastest way to reach me if something breaks or feels off.

If you manage multi-scene, multi-camera, or multi-variation renders and vanilla Blender has been fighting you on it, give it a shot: SCENE ASSEMBLER BETA - Download

1 Like

I am also adding a link for the addon documentation:

1 Like

Hi there! v142 is out, this is the change log
Scene assembler beta v142

New: Output Defaults Override node
Apply the same set of overrides (path, tokens, format, frame range, resolution, camera, world, render settings, passes, compositor, Freestyle) to a group of Scene nodes at once — without editing tree-wide Output Defaults (which affects everything) or setting each Scene node individually.

  • Add it from the new Graph Settings menu category, alongside Output Defaults.
  • Give it a name directly on the node (defaults to Defaults_Override, auto-numbered if you add more than one).
  • On any Scene node, tick Override Output Defaults and pick which one to use from the dropdown.
  • You can create as many of these as you like in one graph, and reuse the same one across as many Scene nodes as you like.

Resolution multiplier can now go above 100%
The percentage field in Output Defaults, Scene node, Output Defaults Override, and Playblast is no longer capped — supersampling above 100% now works like it does natively in Blender.

Fixed: Timeline mode from “Create from Scene” wasn’t actually using the timeline
Scene nodes built by “Create from Scene” in Timeline mode looked correct but were silently rendering with the wrong frame range/mode instead of following their Timeline strip. This is now fixed — Timeline-created graphs render correctly right away, no manual toggling needed.

Fixed: broken Timeline links can now be repaired
If a Scene node ever loses its connection to its Timeline node (e.g. after an undo), a “Repair Timeline Link” (or “Find Timeline Strip”) button now appears directly on the Scene node to reconnect it automatically — no more deleting and rebuilding the graph.

Fixed: auto-generated names no longer contain spaces or brackets
Scene names created by “Create from Scene” in Timeline mode are now clean, e.g. SceneA_Camera instead of SceneA [Camera].

1 Like

Here’s another update! The coolest thing added IMO is the fact that now you can use the render queue even with traditional blender scenes.

Scene Assembler v148

Render Queue: priority control
Jobs in the render queue can now be prioritized (0–100 scale, higher = renders sooner). Set it directly on the Scene node, on the Scheduler node’s per-job sockets, or inline from the queue panel. Reordering the queue by dragging only affects the job you move — it no longer reshuffles everyone else’s priority. Raising a queued job’s priority above the one currently rendering now actually pauses that job and lets the higher-priority one jump in; you can choose whether that pause happens immediately or waits for the current frame to finish (new preference).

Faster log access
Done/failed jobs now have a one-click shortcut to open the render log directly in your text editor, instead of navigating through the queue UI to find it.

Render your current scene without a node graph
New: a Render Queue panel added directly to Blender’s native Render Properties tab. You can now send whatever scene is currently open straight to the background render queue — no Scene Assembler node tree required.

1 Like

the beta has been ported for blender 5.2LTS, few bug fixes here. Still compatible with 5.1.

Scene Assembler_52_v002

1 Like