Batch Camera Render

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


  • 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

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-2015. 32-bit and 64-bit.


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
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.

sergo's picture

I've never came across that kind of bug

Let me check on my machine.

The other thing - I've got Vray 3.0 now, so I'll start to update my script soon.

Comment viewing options

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