CompuServe Messages

That's one of the things I'm working on. First of all, there is a new name. It is now called PAROUT as it is specific to the PAR. PAROUR doesn't create any temp files. I rely on the *.DAT file 3D Studio creates at the end of each render. That way, you can have multiple projects queued up and PAROUT will take care of them all in the right order (i.e. those projects that have PAROUT as the last process on the VP queue). I've also eliminated all questions. If you just click on PAROUT it will start working. No need to setup anything (though you still can go in and set "advanced" parameters). PAROUT know which machine has the PAR so you don't have to set the NETNAME. It also knows where the image files are being created and the file name used. No need to specify that. It knows how many frames there are, the step count, and it will properly wait for the last frame to be ready so there will not be a problem of missing a couple of frames at the end of a batch process. It creates a log file that can pinpoint any problem that might occur so trouble shooting will be very simple (famous last words). There is massive amounts (proportionally speaking) of AI in this new (totally rewriten) code. I'm sure it will make everyone pleased.