Batch Camera Render 2
Batch Camera Render maxscript version 2 - reworked and improved version of Batch Camera Render maxscript. The main imporvement is the ability to assign different settings to one camera, just as in standard 3ds max's Batch Render.
Take a note that it is still in beta stage!
Voted suggestion could be placed here - Google Moderator BatchCam2 Сategory
Current Version: 2.0.9
Release Date: 4 January 2013
Bugfix:
- Corrupted other script's custom attributes stored in a scene.
Release Date: 14 January 2012
Improvements:
- Preview button added- it renders only current frame without saving anything - no images, no vray maps,no elements. Note that if output file is specified in standard Render Setup script saves rendered image in preview mode.
Bugfixes
- Frame Range Type "Frames" didn't recognized - fixed
- Resolution changing in certain conditions caused error message - fixed
- Netrender with Command-Line-Commit didn't worked well - fixed
- Some of the Clear buttons didn't work as expected - fixed
Release Date: 21 November 2011
Bugfixes:
- startup error in 3ds max versions <2012
- render preset not found error fixed
- animation ranges detection now works as expected and camera target's animation is also considered
- clear settings in resolution and frame ranges
Improvements:
- Render method from the version 1.9.x (fewer problems with gamma expected but not confirmed)
- Vray section from the version 1.9.x
- Orthographic camera mode in Vray section - turns Physical camera into orho mode (and any other cameras)
- Nth Frame property can be set for each preset independently (useful for Vray Irmap calculation)
- Render Preset property is now saved not as just a name of preset but as a full file path to ensure scene consistency across the network, different projects and 3ds max versions.
- Render Element property is available, but only in 1.9.x render method. Render commit method can be choosed in Options rollout.
Small fixes:
- Frame ranges are now remembered as you choose different range types.
- Checked state of the render preset is also saving, so you don't have to recheck the presets when you're making many test renders.
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.
This page http://www.sergepogosyan.com/scripts/BatchCameraRender2/ will not be available for some time.
| Attachment | Size |
|---|---|
| batchcam2.0.9.ms | 174.78 KB |
Comments
Did you try "BatchCam1.9.x
Did you try "BatchCam1.9.x Style" without "Show Submit Dialog" option?
It was broken in 2013, I almost gave up with hope that my script will work with new 3ds max, but I didn't try it with 2014.
issue with Render Commit Method
When you choose "Command-Line-Commit" Render Commit Method and use different Scene States and render in DR mode => result is bad. Main computer is rendering good, other net computers are rendering only original scene state.
But with "BatchCam1.9.x Style" Render Commit Method all is perfect except canceling all of the Batch by one click)
P.S. using 3DS Max 2014 64-bit and vray 2.40.03
*.bat
Hi, is there an option to export everything into a *.bat file? OK, I can copy it from the TEMP folder, found it, but its a bit to intricate :)
thx
vray render elements
I can't seem to get the vray render elements to save to file. I know it worked for me as some point, I think on the original Batchcam script.
Thanks
Thanks for the fix, that was fast! :-)
Tim
www.timsportfolio.co.uk
Fixed and attached.
Thank you Tim!
Very severe bug, sorry if corrupted your scenes. Fixed and attached fixed version.
Sergo.
Rewriting other attributes stored on RootNode
Hi Sergo,
Very interesting tool. Great work :-)
I was linked to your plugin by a user experiencing problems with a tool I have written, and after investigating the issue it looks like your tool is overwriting (redefining) all custom attributes stored on the rootNode, including the ones I have stored for my tool. I had a look through the code and I think you need to add a few name checks before redefining the custom attributes to make sure other attribues not associated with your script are not redefined. I have attached a maxscript file that shows exactly what happens:
1. Run the top part of attached script to add a custom attribute with 5 paramaters
2. Open Batch Camera Render 2
3. Click 'Add'
4. Custom attributes made in step 1 have now been redefined, 5 paramaters deleted and replaced with batch camera paramaters.
Cheers
Tim
www.timsportfolio.co.uk
3ds max 2013
I didn't know you're trying to make it work under max 2013. I couldn't manage to test it with recent update yet, but without that update both the scripts don't work as expected.
Try to install update 5 from AD support site.
Hi,I never changed job type
Hi,
I never changed job type to 32 bit in BatchRender2 settings, always using 64bin max with 64bit jobs and 64bit slaves. Just set 32 and back to 64 to force the script. Leads to nothing.
Submitting "command style" in 2013 64bit still leads to non changeable jobs assigned to no slaves.
IMPORTANT!!!!!
Checking "Show Submit Dialog" and sending jobs "BatchCam 1.9"-style leads to working renderable jobs!!! Only the renderdialog+connect+save times/clicks are highly annoying.
Using command-line + "Show Submit Dialog" freeze max or freeze the cmd window.
64-bit job to 32-bit servers
That happenning sometimes when you submit 64-bit job to 32-bit servers or otherwise. Could you check the settings in script's Options rollout?