Batch Camera Render

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


  • Support for 3ds max 2023 Update fixed


  • Corona and Vray Sun inside Daylight System fixed (thanks to busseynova for reporting)


  • 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-202x
batchcamerarender_1.17.ms245.88 KB
batchcamerarender_1.18.ms245.92 KB


Comment viewing options

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

Thanks for the answer

Thanks for the answer, knowing about this feature I will use either copies of cameras in one place, tying them to each other or tying the necessary parameters through wire parametrs

sergo's picture

Unfortunately no fix for instanced camera issue right now

Hi locb
Unfortunately that is how the script works right now. I don't see how it can be fixed for camera instances.
If you are interested in technical details this is what's happening: Additional camera presets are store on the special object called CustomAttribute. When you add CustomAttribute to the instance, all the instances basically share the same custom object. That's why you see multiple additional items, but it's actually the same custom attribute that all the instances share.

It's annoying I agree. I will keep that issue in mind and I'll fix it if I find the solution.

locb's picture

Unfortunately, the problem

Unfortunately, the problem was repeated in max 2016, physical camera.
When I create a camera, then make its instance copy 2 times, then when I click add I get 2 copies of the last copied.
But when copying without instance everything works as it should. (screen of batchrender window)
Maybe it can be fixed?

locb's picture

Exactly. In the 5-camera

In the 5-camera scene, all the instances.
In the script, you can see all of them.
But when I try to make a duplicate of all cameras, instead of 5 duplicates of each camera I get five duplicates of one of them.
In a clean scene I have the same.
An earlier version of the script behaves the same way.
Maybe the reason for my version I will try to remove ENU and maybe this will help.

sergo's picture

Hi, @locb, I don't really


@locb, I don't really understand what's the problem. Are you trying to add 5 instanced cameras and it doesn't work?

@pfbelesa, I'll check the script with 2021 Max, see if I can reproduce this.

Thanks for reporting!

pfbelesa's picture

I got error with 1.16

Got an Unknown property error "NumRenderElements" is undefided

2021-03-06_09_48_44-c__program_files_autodesk_3ds_max_2021_scripts_web_batchcamerarender_1.16.ms_-_m.png 38.58 KB
locb's picture

HI. I got problem,when i

I got problem,when i click add in scene where 5 instanced cameras dublecated only one camera but 5 times? when cameras unique add work well (windows 10, physical cameras)
What i do wrong?

sergo's picture

Have you tried it?

I think it's working that way already. Check the list of keywords:

Also you can duplicate the camera and use different state on each preset. That would save you from flicking the scene state.

THINKTANK's picture

still use this regularly,

still use this regularly, such a great script!

do you think you could get Scene states to do a cycle on a camera? that way I could have same camera once, then just flick off and on different layers (using state scenes), if you could include a outputname like %scenestates% that would save the name of the state that has just cycled.

would love that feature :)D

ChinmayT's picture

Unable to save gamma..


I am unable to save gamma type while saving render..

Could you please guide me..
how to save output gamma to override 1.0 instead of automatic 2.2

Right now render is washed out.. automatic mode. I need override mode.

Thank you for the script.. :)

Comment viewing options

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