CompuServe Messages

<<why don't you simply render 4 viewports to the queue?>> Lots of reasons, none compelling, perhaps, but you asked. – I don't like to move the dongle around to different systems (to set up an independent render queue), and I don't do most renders on the modelling system. (I did read here once something about setting up a queue on each system using the dongle, then taking the dongle off an putting it on the next system to repeat the process). – I find it a little annoying, and pretty pointless to have to keep saving project files for network rendering when the only thing being changed is shading mode, or resolution, or output file type. I can write a batch file for that much faster than I can create a network queue, having to wait for the save of the project file each time I change a rendering option. – If I batch/command-line render, I can be varying options on the fly and rendering on one sys, and be working on different project files on the main sys … if I use the network, and decide I want to add something to the queue that doesn't happen to be the project I'm currently working on, I have to save, load the other project, save it for the net queue, reload the first project …. – I have a network, but don't like to be obliged to use it (Lantastic), and especially don't like to have to keep the main system on if I have started network rendering with the other systems as slaves. – I can see that the network rendering option, with it's detailed activity report as being invaluable, even on a single system, for "final" rendering, tracking missed frames, exact rendering times, etc., but for a fast, flexible way to compare renders on independent systems by changing those parameters available through switches, batch "when it works" (!), is great. – Also I'm a little bit stubborn ,:)