Batch Camera Render
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.
1.18:
- Support for 3ds max 2023 Update fixed
1.17:
- Corona and Vray Sun inside Daylight System fixed (thanks to busseynova for reporting)
1.16:
- CoronaSun supported inside Daylight System
1.15:
- 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: http://usakhelo.github.io/batchcam/batchcam-1.9.20.html
Script's website - http://usakhelo.github.io/batchcam/
Github - https://github.com/usakhelo/batchcam
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.
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
| Attachment | Size |
|---|---|
| batchcamerarender_1.17.ms | 245.88 KB |
| batchcamerarender_1.18.ms | 245.92 KB |
Comments
Suggestion: Autoload Scene state that has identical name
as the camera :)
That would be perfect fit for my workflow.
You can have that option
You can have that option checked in standard render dialog, it will not be touched by the script.
Here is my quick setup that saves lightcache and irmap using camera name as filename, hope that helps:
'Use camera path' option for vray GI solution calculations
I have a scene with 10 to 20 animated vray cameras. I need to create a solution for each camera (using lightcache and irmap). Normally, when I do them one at a time by hand, I have the options checked to 'use camera path' for the solution.
This means the GI solution is only caluculated for what the camera 'sees'.
Could this option be added to Batch Camera Render?
(I've just tested a batch job where I told each of my 3 animated cameras to save the lightcache and irmaps. They don't appear to have saved them. Any ideas why?)
----------------------
www.blinkimage.com
Attached script to post
Hi guys!
That broken link forced me to update the script. I've listed some of the most visible new features, later I'll add all new features and update description (hopefully).
Enjoy and happy holidays!
link is dead
can any one give me link ?? link is dead
You can use Vray commands
renderers.current.saveIrradianceMap "filename.vrmap"
renderers.current.loadIrradianceMap "filename.vrmap"
To register that commands as callbacks run this code before rendering starts
callbacks.addScript #postRenderFrame "renderers.current.saveIrradianceMap (\"file_path_and_name\" + ((currentTime as integer) as string) + \".vrmap\")"
But you should manually delete that command to not have irmaps resaved after each and every render in current scene
callbacks.removeScripts #postRenderFrame
file name + current frame number
Hello, thank you Sergo for that great script.
Do anybody of you have a idea how to implement the current frame number to a file name ?
I try to save a range of numbered Irradiance map and LC-files from a short animation (a camera movement with five different camera and sun positions) like: House_LC_0001.vrlmap , House_LC_0002.vrlmap ....
I set the custom Keyword:
framenr = (currentTime.frame as integer) as string
Unfortunelya file name "House_LC_%framenr%.vrlmap" gives me just the nr of the first used frame.
I see, there is a method with a callback, but I do not have a idea, how to use this
((callbacks.notificationParam())[13].Frame as string)
Kind regards
Alex
%cameraname%. jpg
Are you using %cameraname% keyword for your file name?
problem
Hello
sometime, in some project i have a problem with 1.9.8.1 version.
I render 10 cameras for example,
cam1: frame 10
cam2: frame 5
cam3: frame 15
...
..
result of image are for example always cam2(frame 10-5-15....)
why? exist a solution?
I use batchcamera to rendering images with diferent light direction.
Well done. This is a great
Well done. This is a great script, although I couldn't use it much.
Basically I am rendering various scenes on different cameras.
Due to the large number of objects, I cannot batch render all of my cameras because if I turn all lights on, the render time increases dramatically.
This script could be a perfect solution and I could set all lights to get ON and OFF as needed. But As I start setting up the lights in "BATCH CAMERA RENDER", it freezes and I need to restart 3DMax. I'm not sure if this is the script's bug or 3DMax limits.
Again, thanks for dedicating your time to develop such a useful script.