[casey]

Currently it is a very cumbersome manual process to launch a net render, and there doesn't seem to be any way to accelerate it because the user must manually operate the GUI of "mxcl -display" to launch network render jobs. It would be much more convenient if the user could simply leave "mxcl -display" running, and be able to automatically launch network jobs from their favorite 3D package by executing, say, "mxcl -netjobadd (some mxs file) -anyavailable -cooperative", etc., etc. Then they can switch to the mxcl GUI to see how the jobs are coming any time they want.

We can then write all kinds of scripts with MAXScript or MEL or whathaveyou to launch renders however we want, and they will be properly distributed to the farm and so on.

- Casey

[Maxer]

We need a simple GUI with a simple and easy workflow process; you should look at the way 3D Studio and Backburner work together. Right now the process is so complicated it will be a nightmare to use on any sizable render farm. Think simple not complex.

[casey]

We need a simple GUI with a simple and easy workflow process; you should look at the way 3D Studio and Backburner work together. Right now the process is so complicated it will be a nightmare to use on any sizable render farm. Think simple not complex.

I'm neither thinking simple nor complex, I'm just thinking of the easiest thing they could add to their current setup that would allow me to make a functional rendering farm. Right now there's no way I can automatically take user-generated jobs and spin them to the farm. If there was mxcl command line ability to add jobs, I could build my own GUI in MAXScript and be done.

- Casey