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
Unsolved backburner problems
Hi, still getting non renderable backburner jobs with Command Line rendering.
They can't be assigned to any slaves nor somehow changed (change priority, frames or sth else). They won't render because there are no slaves assigned at start.
For me it seams to be some type of "locked renderjob" kind of problem.
They can only be deleted or (sometimes) suspended.
Bad news
Unfortunately there is serious bug in 3ds max 2013 maxscript. I can't make work batchcam 1.9 with max 2013 so far due to this bug.
I didn't test batchcam2 with max2013, but you can try to use "command line" submit method. "Batchcam1.9 style" submit method is definitely unstable.
In my case max is crashing every time I submit the job.
Oh by the way, by putting the
Oh by the way, by putting the render elements completely into the output EXR files (part of pipeline changes here that were long overdue) ended the RenderElements fuzz/chaos with Batchrender/3dsmax. Please fix the backburner issue mentioned in my last post.
Hi I have here a serious
Hi I have here a serious problem with Batchrender2 under 3dsmax 2013:
The Jobs sent to backburner don't get assigned to any renderslaves, manually assigning them don't do it either.
I was stuck in productions and want to post this for several weeks now, sorry for being so late.
sIBL light problem
Hi some problem I found with render camera batch with sIBL light system a HDRI sunlight system from http://www.hdrlabs.com/sibl
The sIBL script work well on 3dsmax 2011 x64 and vray render system, but when I launch some camera or some frames on batch script (tested on 1.9.7 and 2.0.8) background is not aligned...
attached the differences from render by the standalone camera and from batch render...
Render elements' names is a
Render elements' names is a real pain in the ###. AD changed something again, they don't overwriting when names are set by the user... Still struggling to find some workaround.
Jobs table's size will configurable in next version. Stay tuned ;)
Some minor wishes
Hi,
could we get a bigger renderpresets dialog box?
Using the whole width of the window?
And a higher jobs-window?
We have here a lot of problems with Render Elements. They don't render using the right names, instead they take the names out of the 3dsmax render settings dialog (even if we erase the names there).
Keep up the good work, we are using your batchrenderer all the time.
Thank you for thorough
Thank you for thorough testing Stan!
1.Situation where "automatic paths overwrite scripted paths" looks like a bug.
2. >>At the end, if you rendering 3 passes, the render elements of the passes will not have the correct name (of the cam) and will overwriting themselves.
Could you send me a scene with passes set up, where they're overwriting one another?
I'll think about the rest of your post and write later.
Hi Sergo, I'm using a lot
Hi Sergo,
I'm using a lot your script for the current project, and I came across some feature that is a little bit missing if I way comment :o)
I would be great if there was a way to name the passes.
Because when you have the same camera with different passes you can't really figure out with one is rendering in BB.
Of course for the moment I'm using the edit setting to see the render output but it would be great to have the name of the passe directly in the job name.
Another feature would be to have the ability to expand the view of the passes. For the moment, it's limited to 7 passes and then you have to scroll down.
If I can say also, I found a kind of bug.
If you are rendering with passes, it's working great as long as you don't have any output path in the render element. But the thing is that max/vray is creating automatically a render output path in the render element when you save out a image the "normal way". And that output path is overwriting the output path/name of the render elements of the passes in your script.
At the end, if you rendering 3 passes, the render elements of the passes will not have the correct name (of the cam) and will overwriting themselves.
I just have to be really careful now when I send out passes that I don't have any path in the render elements in max.
Hope it's not too much asked
Cheers
Stan
Great! thanks very much, I'm
Great!
thanks very much,
I'm gonna try that when I have some time.
Cheers
Stan