Batch Camera Render

270 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.


  • CoronaSun supported inside Daylight System


  • Don't Save Render Elements Checkbox (Thanks to antomor)
  • Limited support for camera objects in xref scene files (Only root objects in first level xrefs. Cameras in nested xrefs not supported)

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-2019
batchcamerarender_1.15.ms245.66 KB
batchcamerarender_1.16.ms245.73 KB


Comment viewing options

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

+1 for Save and Load

+1 for Save and Load Irradiance and Lightcache maps. Awesome script!

sergo's picture

Thank you Track! It works!

Thank you Track!

It works! Cool! :) Will point guys from chaosgroup to this post.

my scripts and tips/tricks:

Kstudio's picture

>>The only bug that I could

>>The only bug that I could not solve is that Render Elements don't render when "Enable VFB" is on.
>>I've posted the problem on and on but there is no answer yet.
>>Any help is much appreciated.

Hi Sergo.
I had the same problem in my script VrayMultiStageRender
I found the solution:

bm_filename = sysInfo.tempdir + "tmp.jpg"
bm=Bitmap 10 10 fileName: bm_filename
save bm
close bm
deleteFile bm_filename


FilePathFinder-for search, relink, collect, sort and rename asset filles...

sergo's picture

Hi pifitas! > -

Hi pifitas!

> - Automatically add name to cameras / files instead one by one as well as

> automatically use current folder to save. 

Did you try to use keywords in filenames, such as %cameraname%? Using keywords you can set output for all your cameras at once - just select them all and type  %cameraname%.ext to the file name! One thing you have to do is to name correctly your cameras - I'm using names such "livingroom", "outside" etc. And this should be done one time! Normally you don't want to rename your output.

As for me, I don't even change file extension - I'm always render to .exr. For previews I'm using relatively small resolution.


my scripts and tips/tricks:

pifitas's picture

Hello again Sergey Nice

Hello again Sergey

Nice update :)

I'm still wondering if my suggestions can be cosidered in coming versions:

 - Save / Load VRL and VR vray Maps PLEASE PLEASE :(

- Override format output for all files, instead slecting one by one

- Automatically add name to cameras / files instead one by one as well as automatically use current folder to save.

- Area selection (View, region, etc)

- Force to Hide / Unhide objetcs (like lights) (NEW SUGGESTION)

By adding names to cameras and output files, as well as override output file format, practically you simplify job in 3 STEPS:

Open batch render

1) select cameras (they already have camera's name and output format name)

2)override format and output path

3)Render... :) easy.

BTW Congratulation for this amazing script :D!!!!

fajar's picture

Ahh......Im so

Ahh......Im so relieve......if this become comercial i dont have any money to get it! hehehehe.......

 But I'll be happy to make money with scripting, and if some studio needs to implement something totally customized, it not strange to do it for some reward.

I agree with you, no offend!

and thank for 1.8 update!!

sergo's picture

No, no.  I didn't say that.

No, no.  I didn't say that. I don't like that "became popular - become commercial" situation. But I'll be happy to make money with scripting, and if some studio needs to implement something totally customized, it not strange to do it for some reward.

And it doesn't mean that sun/sky setting is something strange. It's ok, and it will be added, sooner or later.

my scripts and tips/tricks:

fajar's picture

Become comercial ?

Become comercial ?

sergo's picture

Didn't try under max 9, but

Didn't try under max 9, but I guess it should work. Why not?...

I add sun/sky setting to the todo list. If there would more people demanding such setting that feature will get higher priority. Can not say that there is too many people with suggestions, but anyway, there are some features I've already planned to implement.

I hope scriptspot will have voting system in near future, so it would be easier to decide which feature is most popular. Until that time (and after that too) I'm ready to customize (or to build from scratch) scripts for the inhouse use, as a paid job, of course.

my scripts and tips/tricks:

birket's picture

Fair enough - it was only a

Fair enough - it was only a suggestion.

We always use the sun system as our clients demand that we use correct (realistic) times of day for their images.


Comment viewing options

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