Batch Camera Render 1.5.1

2009-06-22

Download Script

UPDATE 2009-07-01:

Bug fixed: "Frames" render type doesn't work if previous render type was "Anim.Range".

UPDATE 2009-06-22:

Added single frame range parameter to specify single frame. There is also button to quickly specify current frame.
Added Animation Range parameter to render only camera's animation range. Animation range is changing when you edit camera's keyframes. Table in the script window doesn't refresh until you restart script or click on Anim. Range once more but when you hit render button script reevaluates animation range of the camera and sends to render proper frames. If camera is not animated frame 0 will be rendered.

Full description and installation procedure can be found here.

Bug reports and suggestions are welcome.

previous article:Batch Camera Render ...

next article:Batch Camera Render ...

10 comments:

sheikh

2009-07-21 05:28

cheers, very good script

Enrique

2009-07-21 16:48

Awesome Script! I just installed it (Vista x64 for 2009 3DS Max64). I'd like to request some of the basic Max Batch Render options, such as 'Name', 'Add...', 'Duplicate', and 'Delete'

I look forward to using this script since, like you, wanted the features of 3DS Max's basic Batch Render, with better control of frames (animated, nth frame, etc.)

Thanks again for your effort!

Enrique

2009-07-21 16:58

Ah, I just read the detailed description under 1.4

I would actually need many different settings for 1 camera, which you chose not to script since you didn't need it. Well, I look forward to this script if you can change that. If not, I'll look elsewhere.

Thanks again.

Sergo

2009-07-22 14:50

You can add different settings to one camera by cloning that camera several times :)

Enrique

2009-07-23 08:59

Thanks for the suggestion! Unfortunately, I have a scene that will require hundreds of scene states, so that won't work for me.

aubrey

2009-08-07 17:27

Hi Sergo,

Thanks for writing this great tool!

I'm only using it for the first time today. My initial suggestion is to have automatic job naming and submission. I'll be poking at this in the future, and would be happy to test or give in-depth feedback. We wrote something like this where I used to work, with some major additions (Xref state, and custom render style management). Thanks again!

Sergo

2009-08-10 13:14

Hy aubrey!

Automatic naming and submission requires exclusive queue control. It means that you can not submit your render job if someone else controls render queue at the moment. It is serious limitation for me and I don't know other method in maxscript to do it.

Almost every feature request contains automatic job naming, so I would be happy to implement it. If you know some workaround, please let me know.

Thank you.

Fabrice

2009-08-11 15:41

Sergo, glad to hear you're working on this! for me, I always have queue control so it wouldn't be a problem. perhaps for now you can just flag an error if no queue control is available? thanks, fabrice

dorham

2009-08-31 01:35

Sergo, Great script !!! Thanks a lot it saves me a lot of time, scenes states are now very useful for me(matte object...)!

I suggest you to add a "Shutdown computer after rendering is done" in the params. Thanks again !

Sergo

2009-08-31 23:13

Thank you!

In few days I'll upload new version with automatic naming and submission and some more features.

Shutdown after rendering is one of the top TODO feature, it'll be done very soon. But in more general way - "run script after the last job" or "attach post-render script to the last job" - for the more flexible way to control render servers.