DreamRender is lightweight render farm software for small Cinema 4D 2026 setups using Redshift or Octane. It is built for artists who have a few powerful machines at home or in a small studio and want any available machine to pick up frames automatically.
It follows a Deadline-style render manager workflow, but keeps the architecture simple: every machine points to the same DreamRender share, and workers join or leave without a database server.
New install? Follow the artist-friendly guide:
DreamRender uses a clean desktop app shell. See DreamRender App for architecture and development notes.
That guide covers:
- installing regular Python
- setting up the DreamRender app
- choosing the shared queue folder
- installing the Cinema 4D plugin from the app
- starting workers on render machines
- submitting from Cinema 4D
- fixing the most common setup problems
- A Cinema 4D submitter plugin with a scene checker.
- A desktop control app, so workers do not need command-line use.
- An integrated dashboard for jobs, takes, workers, progress, logs, previews, frame ownership, and render statistics.
- Frame batching, so heavy scenes do not reload for every single frame.
- Marked-take submission, grouped in the dashboard.
- Worker colors, job status labels, folder open actions, archive/requeue/cancel controls, and stale-worker recovery.
- App health diagnostics for missing Cinema 4D paths, plugin install state, queue write access, worker heartbeat loss, failed frames, and stale locks.
- Failed frames stay failed until you intentionally repair or requeue them, so broken frames do not loop forever in the background.
- Cinema 4D output paths are preserved from Render Settings, including common Cinema 4D tokens.
Use the same project path on every machine. For example, if the project is on
drive P:\ on the workstation, map it as P:\ on the render node too.
Use one shared queue folder that every machine can read and write:
DreamRenderShare/
jobs/
workers/
The queue folder can live on a NAS, a shared drive, or one of the machines.
- Start
START_DREAMRENDER.vbs. - Set the shared queue folder and Cinema 4D Commandline path.
- Click
Install C4D Pluginonce per workstation. - Make sure the
Healthpanel is OK. - Click
Start DreamRenderon every machine that should render. - In Cinema 4D, open
Extensions > DreamRender Submit Render. - Click
Check Scene. - Click
Submit Project. - Confirm
Savewhen DreamRender asks to save the scene. - Watch the integrated dashboard.
Use START_DREAMRENDER.vbs for normal work. It opens the native DreamRender app
without showing a console window. The app keeps the proven Python renderfarm
engine underneath, but gives artists one clean control surface.
Advanced scripts live in scripts\advanced. Use
ADVANCED_Worker_Only_C4D2026.bat only when you deliberately want a visible
troubleshooting console.
Install the plugin from the DreamRender App with Install C4D Plugin.
Restart Cinema 4D 2026 after installing. The command appears as:
Extensions > DreamRender Submit Render
The submitter reads the active Cinema 4D Render Settings for:
- frame range
- output path
- output format
- Redshift, Octane, and multipass settings
- marked takes and take-specific render settings
DreamRender saves the current scene, then creates a separate job-scene copy in a
DreamRenderJobs folder near the project. Workers render that copy, while output
still goes to the path set in Cinema 4D Render Settings.
DreamRender supports Cinema 4D command-line rendering for Redshift and Octane. The render engine must be installed and licensed on every worker machine.
For Octane jobs submitted from the Cinema 4D plugin, DreamRender stores the detected renderer in the job metadata. Workers then use Octane's recommended Cinema 4D command-line module path pattern so the C4D Octane plugin can load in background renders. Octane jobs also receive an explicit command-line output path because Octane can hide Cinema 4D's standard Save controls.
The dashboard is opened from the DreamRender app. It shows:
- grouped jobs and marked takes
- current worker activity
- done/rendering/queued/error states
- progress bars and render timing
- frame ownership by worker color
- logs and browser-friendly previews
- archive, requeue, cancel, pause, resume, and priority controls
- drag priority controls plus explicit Up/Down buttons as a reliable fallback
PNG, JPG, WebP, and GIF previews display directly in the browser. EXR/TIFF files need a converter on the monitor machine for thumbnails, such as ImageMagick, OpenImageIO, or ffmpeg.
The app is the preferred workflow. These commands are mainly for troubleshooting or automation.
Run the app without a console:
START_DREAMRENDER.vbsThe commands below are advanced troubleshooting fallbacks and may show a console.
Run a worker:
scripts\advanced\ADVANCED_Worker_Only_C4D2026.bat "\\RenderServer\DreamRender"Run the monitor:
scripts\advanced\ADVANCED_Monitor_Only.bat "\\RenderServer\DreamRender"Check queue status:
scripts\advanced\ADVANCED_Command_Line.bat status --share "\\RenderServer\DreamRender"For editable Python development:
python -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e .DreamRender can also run without installing the Python package because the
launchers set PYTHONPATH to the local src folder.
DreamRender is released under the MIT License. See LICENSE.
Cinema 4D, Redshift, Octane, Maxon, and OTOY product names belong to their respective owners. DreamRender does not include Cinema 4D, Redshift, Octane, plugins, render licenses, or third-party assets.
- Use regular Python 3.10 or newer from python.org. Do not use Cinema 4D
c4dpy.exefor the worker. - Keep Cinema 4D, Redshift/Octane, plugins, OCIO, fonts, caches, and assets consistent across machines.
- Renderer licensing must allow command-line rendering on each worker.
- Map project folders identically on every machine for the most predictable output and asset behavior.