Batch Camera Render

266 votes
Date Updated: 
Author Name: 
Sergo Pogosyan

This script aims to replace standard 3dsmax's Batch Render and imitates Houdini Output Node workflow. Using it you can specify rendering parameters - frame size, frame number, output path - directly to camera object, so every camera in scene 'knows' what it intended to render. Additional functionality is Lighting Assignment - you can specify which light will be turn on or off for selected camera during the rendering.

1.13 Bugfix:

  • Deadline submission should work now

1.12 New Feature:

  • Deadline support.
    Very basic imlementation, it allows you to submit your jobs on a deadline server. Enter deadline repository address and check "Use Deadline" checkbox. Other checkbox doesn't matter in this case ("Net render", "Show Submit Dialog").
    Probably it requires Deadline 3ds max Submitter installed. I didn't have a chance to check it on a clean machine.

1.11 Features and fixes:

  • State sets support added
  • "projectname" keyword added which resolves to project's folder name
  • other fixes and improvements

1.10.3b Fixes:

  • Crash when vray ir/lcache maps are set to auto-save
  • Region render was not set properly during the rendering

This is major update of the script, so it may not be as stable as before. Backup scenes or cameras at least before running this version. More information can be found here - 1.10b Multiple presets for each camera

Previous updates:

1.10.2b Fixes:

  • Problems with render elements paths
  • Copy/paste of render region settings
  • Properly convert render region values when change resolution

New features:

  • Multiple presets for each camera
  • New keyword %presetname% to support multiple presets
  • Distributed rendering checkbox added to vray common settings
  • Bugfix - Net render not starting after cancelling during local rendering.
  • Improved performance with scenes with lots of cameras
  • Added support of Vray RT as a production renderer
  • Added support of using MFRender script to render scenes through BatchCamera script.
  • Bugfix - Error was popping up sometimes during drag-n-drop
  • Bugfix - Render elements didn't render in certain conditions
  • Bugfix - Pre-render/post-render scripts didn't work on network rendering
  • Bugfix - Select All and Toggle All buttons didn't work properly

Here are some details:

Script's website -

Github -

2015 Updates

  • Region render parameter can be specified for each camera
  • Set Viewport button sets viewport camera and resolution and aspect as well
  • It is possible now to specify backburner servers and server groups for silent rendering submit (code editing required)
  • Vray Elements fixed for Vray 3 and Vray output saving with VFB color correction
  • Cancelling of rendering of multiple cameras at once,
  • Hierarchical ini files

2013 Updates

  • Drag-n-drop of cameras in list
  • Camera list window size can be changed (script restart required)
  • When committing region render it is possible to switch to view render without restarting the render
  • Keyword syntax can be used in Scene State names - thanks to Stefan Runevik for suggestion

2011 Updates

  • Preview button added - renders only current frame without saving anything - no images, no vray maps, no scripts running, no elements.
  • Ortho mode added to Vray rollout - it turns any camera to orthographic, including Vray Physical camera.
  • Copy/Paste from one camera to one/several cameras - use new buttons at the top of the window.
  • Submit Scripts section - you can assign script files that will run on each render submit. Per Submit script runs once per render submit and Per Camera script runs for each camera before submit. All these scripts run on local machine, not on render server.
  • Last Rendered Location field - here is stored last render file location. Very useful for locating last-time rendered images.
Additional Info: 


Run this script with Maxscript -> Run Script command from any folder on your hard drive, then go to the *'Customize User Interface' -> 'Toolbars'*, browse to category 'Sergo Pogosyan' and add 'Render scene cameras...' button to the toolbar or to the menu.


When you start this script it iterate over all cameras in scene and list them in the dialog box. To each of these cameras you can assign frame resolution, number of frames to render including nonsequential frames, output file location and lighting setup. All these properties can be changed for one or several selected cameras. Output file location is split to folder path and file name, so you can specify new folder for all selected cameras in scene. 'Lighting assignement' section contains three list: Solo light list contains lights that will be only lights turned on during the rendering, 'Forced On' and 'Forced Off' lights are turned on or off respectively during the rendering. After all these setting will be set up (if some properties is not set value from the Render Setup will be used), check the camera(s) in the list and hit Render button. Check Net Render checkbox to submit network render job.

Supported lights: All bundled 3ds max lights, all Vray Lights
Supported cameras: All bundled 3ds max cameras, Vray PhysicalCamera

Version Requirement: 
3ds max 2008-2018
batchcamerarender_1.13.ms235.58 KB


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
SUPERCOMBO's picture


The settings of LightSelect elements delete max preset option, not Batch Camera Render, sorry about I had not noticed it before. Script is awesome, may thanks!

sergo's picture

never tested it with Corona

I've never tested it with Corona, so thanks for reminding me. I'll check. Can't believe script actually deletes anything on purpose, but some render elements are weird, so let me see...

SUPERCOMBO's picture

Corona light mix problem

After setting up light elements on render ellement window and pressing render, Batch Camera Render delete all lights in eveti element.

blacklead2_-_teamviewer_-_besplatnaya_licenziya_tolko_nekommercheskoe_ispolzovanie_2017-02-24_09.22.58.png 124.61 KB
Dariusz's picture

Can it use camera name?


Can this script use camera name and prefix? - it can. Amazing piece of code!!! THANK YOU!


happydaydreamer's picture

State set

Maybe I misunderstand you, but the scene states and state sets are two different things.
Try to make two different scene states (not state sets) and see if that works.

Best regards,

pixelab's picture

I made some tests and I

I made some tests and I can't, so I guess it's linked to my file. Will retry more and let you know

sergo's picture

Can you reproduce the error?

I could not model the case to make that string in the script to fail. Is the crash random or it happens all the time?

pixelab's picture

unknnow system exception

I got this error, and it points to line 1123 when I try to submit 10 render to backburner

1123 render_servers = batchManager.GetServers()

Also, the "custom keyword and name" is a bit confusing, is there where you put backbuner job name ? syntax is like file names ? %cmameraname% will work ?

To get the alpha with the render, should I use max render elements, or will it work with VRAy ?

You should do a FAQ on your site, and a donate button :)

mali's picture


Oh man, I feel silly now. I never thought of doing it like that :D Thanks a lot for the tip!

sergo's picture

need to check state sets

@Angrymodeler, @koltscho - I need some time to learn how to use state sets. If they work in the way old-style scene states work then it will be possible to add them.

@mali - 1) If I understand correctly you can just select all the presets and change the path for all of them.
2) FOV parameter adding is possible, but requires some time. Let's see if any more people request it.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.