Batch Camera Render 1.5.1

2009-06-22

Скачать скрипт

UPDATE 2009-07-01:

  • Исправлена ошибка: режим "Frames" не работает при переключении на него с режима "Anim. Range"

UPDATE 2009-06-22:

  • Добавлен параметр для указания номера одного кадра. Тут же есть кнопка для быстрого указания текущего кадра.

  • Добавлен режим для указания диапазона кадров анимированой камеры - Animation Range. При выборе этого режима будет считаться вся анимации камеры. Диапазон кадров меняется при добавлении/удалении ключей анимации. В таблице номера кадров интерактивно не меняются, но на просчет всегда посылаются правильные кадры. Чтоб обновилась таблица надо закрыть и снова открыть окно скрипта или еще раз выбрать режим Animation Range. Если камера не анимированая, будет считаться кадр 0.

Описание принципа работы и установка можно посмотреть здесь.

Жду замечаний и советов.

комментарии

10 шт.:

cheers, very good script

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!

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.

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

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

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!

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.

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

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 !

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.

Этот адрес не будет нигде показан.
(поддерживается markdown)