Batch Camera Render

Date Updated: 
Author Name: 
Sergo Pogosyan

You can also try new beta of Batch Camera Render 2 - multiple setting for one camera and new render submit procedure.

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.

This bug fixed -

UPDATE 15  December 2013

There are several new features I've added since 1.9.81, but I put the list of most visible ones for now. Later I'll add full list of new features.

  • 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
  • ini files parsing updated - more details later
  • Keyword syntax can be used in Scene State names - thanks to Stefan Runevik for suggestion

UPDATE 23 November 2011

  • Preview button added - renders only current frame without saving anything - no images, no vray maps, no scripts running, no elements.


UPDATE 17 November

  • Ortho mode added to Vray rollout - it turns any camera to orthographic, including Vray Physical camera.


  • Animated Ranges now evaluated correctly - animation of camera target is taken in account.
  • Vray parameters restored after each camera for correct process of undefined properties.

UPDATE 22 June 2011 

Script is under GPL v2 license from now on.

UPDATE 05 July 2011

New Features:

  • 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.
  • I hope many of you use Global Defaults INI file during the each day work. If so, I'm sure you'll find useful new feature - Local Defaults!
    Using this feature you can set default values for the current scene, project or some other group of files. Local default values override the values from Global INI file. They are defined in local INI file. Path of local INI file is set in the Local INI Path field in the Options rollout and it  can contain global keywords (%scenepath%, %projectpath% for example). To save some property value as local defaults press "To Local Defaults" button in property's section. After that all new cameras in current scene will have default values defined in saved section.
    Local INI Path can be saved in Global INI file, so by using relative keywords (%scenepath%, %projectpath%) each scene and project will use their own Local INI file automaticaly.
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-2014. 32-bit and 64-bit.
batchcamerarender_1.9.10.ms211.22 KB


Comment viewing options

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

Suggestion : Match resolution when setting viewport

First of all thank you for this very useful script.
I noticed that when I click the "Set Viewport" button, the viewport is assigned the selected camera as intended. But the output resolution is not reflected. So I have to click on a second button in another rollout : Output Size>to Max.
Wouldn't it make more sense to change the camera AND its corresponding output resolution at once ?

sergo's picture

Maxscript doesn't control backburner.ini

Unfortunately I can't make 3ds max to read or to not read backburner.ini file. At least I don't know the legal maxscript way of doing this.

chris erskine's picture

backburner ini not being used unless show dialog enabled

I'm trying to set my renders up so I don't need to edit each render to change the timeout on high res stills.

I've managed to change my backburner.ini file, and i've gotten it work through the standard network render. and it will also work when show submit dialog is enabled.

but it won't use those settings when I submit the renders in the normal way.

I'm using batch cam 1.9.10 3dsmax 2015, vray 2.5



sergo's picture

Nice job fajar!

Thanks for contributing!
I didn't check it but I'm happy you have the courage to deal with this horrible code :)

fajar's picture

Hey Sergo , Thanks for the

Hey Sergo , Thanks for the script, I made little fix to save render element, it now can save render element on vray 3.xx too [hope I didnt mess up here], its support vray version 2.2 to vray 3, about vray 1.5 sp xxx, it dont, I dont own those vray version. Btw you can check the code simply by search "tagged by fajar".

batchcamerarender_1.9.13.mcr 213.68 KB
mali's picture

render elements in vray3

There are scene states, I put my shortcuts back on the quad menu.
Sergo, any news on the update? I noticed now when I switched to vray 3 and max 2015 that render elements are not saved. Thank you for your scripts!
EDIT: Now I see that when I disable VFB in the script, it renders out all the passes, but it saves them double as tga and without AA. I can't see where I would change this setting...

tomaszzero's picture


Hey Sergo, thanx for this great script. I have one problem with both Camera Batch render and Camera Batch Render 2. When i render the pic with vray frame buffer enabled it is much darker than it should be, and when i render it without vfb it is brighter. I think it is some gamma problem. I found your advice to save renders as exr with gamma set to 1 and also your workaround method in Camera Batch Render 2 thread, but nothing worked for me... Help please, because this is the best batch camera script so far...

I've just noticed, that when max is computing irr map and light cache it looks similar (i mean brightness) for renders with script and without it - so there is problem probably with only final render's brightnes. When i enable vfb in script also IRRmap and LC looks darker when processing... Weird

The problem occurs only in frame window while computing rendering. Saved file has gamma = 1 while i need it to be gamma 2.2.

Edit 3:
I figured out what about your workaround method and it worked but image was saved with gamma 2.2 and this gamma is the same as in frame buffer - too bright (normally, rendering without script is darker - this is proper brightness)

sergo's picture

No scenestates in max2014? What the ...!!!

Sorry guys, but I'm still using 2012, so I have no idea what's going on newer verions.
There are scenestate commands in Customize->Toolbars but they don't seem to work. Why they kept toolbar commands then?!

jnknll's picture

Thinkbox Deadline Support?

Since we had troubles with backburner, we switched to thinkbox deadline. Are you considering doing a support for that too?

@asymptote: Scene States do not open in 3dsmax2014 any more, the only way to get working states is starting your scene with at least one state in 2012 or 2013 and then open the (empty) scene in 2014. (but I didn't try 2015)

asymptote's picture

"so I'll start to update my

"so I'll start to update my script soon."

This is good news indeed!

Is it just me or do Scene States not work with Max 2014 ? I never get any in the drop down, no matter how many I set up in the scene.

Comment viewing options

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