Scripts] Batch Camera Render

 

 

 

New version release - 1.9.6.5 - More new keywords

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.

UPDATE 21 March 2011


New keywords:

• %mainoutput% and %renderfile% returns only file name of the main file output. In this version %mainoutput% and %renderfile% can be used in all fields except the main ouput path and filename.
• %mainpath% and %renderpath% returns path of the main file. Combined with %up% keyword this keyword is very helpful for specifing paths relative to the main output. This keyword is also works in all fields except the main ouput path and filename.

For a more detailed description see my blog page.

UPDATE 13 March 2011

Main New Features and Improvements:
 

Many new keywords added:

• %scenepath% and %scenefolder% - returns full path of the scene.
• %projectpath% added as an alias for the %projectfolder% -returns full path of the 3ds max project.
• %elementname% and %elementtype% - return type and name of the Render Element, works only in the Render Element (Sub)Folder field and in Render Elements name template described later.
• %up% - this keyword changes the preceding path by going up-folder. Example: C:\Users\Documents\3dsMax\scenes\%up%\render returns C:\Users\Documents\3dsMax\render. Very helpful for specifing paths relative to the scene root.

 
New elements in Options rollout (formely System Options):

Render Try Counter - counts how many times the Render button was pressed and %trynum% keyword.
 
User Key and User Value parameters. These fields allow user to define custom template keywords. For example if you want to use username in the file or folder name you just enter word "username" to the User Key and sysInfo.username expression to the User Value field. After that %username% keyword will be replaced with actual username of the user who sends the job to the rendering.  
 
Backburnder job name and Render Elements name templates. Now you can specify your own templates by using all available keywords, and new %mainoutput% keyword for the Render Elements Name template. This keyword returns main output file name.
 
Minor improvements:
 

• Paths of Vray maps are now treated as relative if non-absolute path entered. Empty fields mean that maps will placed in main output folder.
• The Render Setup window is now closed without a warning before the rendering starts.
• Rendered camera becomes visible (if it is hidden) before the rendering to make 3ds max always consider correction/vertical shift parameters.
• No paths are created if Save File checkbox is unchecked in main output section. And render elements are not rendered in this case too.

Different fixes:
 

• All paths are checked for the leading and trailing spaces.
• By design script stores all the parameters before the rendering and restores them after the rendering. Also it creates temporary render preset with all sections including environment. But loading render preset with environment resets the environment map settings, so in this version render presets are restored (reloaded) only if render preset parameter is set in the script by the user. So, if render preset is specified environment map settings are still reset. It is not good solution, rather quick-fix. The possible way to prevent this kind of bug is to analyze all the cameras and to save only those section of render preset which is set by the user, or to not save environment section at all. Any feedback on this question is much appreciated.
• The Lighting state is also restored only if specified in the script. This will make script a little faster. In future versions I'm planning to get rid of this section. By introducing scene state section Lighting State section became redundant. Ironically Lighting section was the main reason I started to write this script.
• This version of the script is no longer compatable with older (pre-1.9.2) versions of the script. In newer versions User Properties was replaced by AppData to store script settings, and some compatability kept by checking User Property values. Now this checking is no longer happens, and that should improve script's performance.

Additional Info: 

Installation:

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.

Usage:

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

 

Full and new description : http://sergepogosyan.com/scripts/BatchCameraRender/

Version Requirement: 

3ds max 9, 3ds max 2008-2011. 32-bit and 64-bit.