[greg3000]

Thinking about automation I had an idea:

What if we could make a script that would recognize when an MXS file is moved into a specified folder, renders it, then moves it and it's results to a complete folder? We (the forum) have already made a batch file for rendering a series of MXS files, this would take it one step further.


1st step: Chose a scripting platform -- I've used AutoIt before and found it pretty straightforward, as well there is a good forum to support it

2nd step: figuring out how to recognize when a new file appears in a directory

3rd step: figure out how to make an update-able batch file for rendering images... maybe a batch file that runs a second batch file? The first batch file would search for and run other batch files? The second batch file would be the command string that iniated the render?

Anyone want to work on this as a team?
Greg

[blueplanetdesign]

Greg,

I'm curious as to the motivation for the development
of such a facility. Do you have a specific need in mind?

[greg3000]

Hi Steven,

My family's business is all CAD now and we needed a engine that could appropriately render our products. We produce about 5 new ones each week and have about 500 needing render at the moment. I began to create mxs files for each, then small batch files and was thinking of how I could further facilitate the process.



Greg

[blueplanetdesign]

On another note all together...

have you set up a batch file to render a variety of cameras in one file?

S

[greg3000]

I read in the forum that the network render does not really work, but as a render queue management, rendering on the local processor, it is very useful for batch rendering.
What functionnalities would the projected script add to it ?

Possibly none, I'll look into it and write back. -thanks!