CompuServe Messages

Actually, I'm going Gary's route and using the net queue, which will work great for rendering multiple files in one shot (I guess it wouldn't work for you if you had to pull the lock). Hopefuly I won't have to deal with the command line problem, because it had me baffled. I tried rendering to different drives and directories, but the files always ended up in the image sub directory, even when I changed the default in both the set file and project file. 1600 frames in one night? To complicate things, its a single shot and the original mesh file is almost 22 megs, but this rendering is just a final motion test done full res, G shaded and no antialiasing or maps and works out to 25 sec/frame or 11 hours total. Even with 40 megs RAM, it had to be broken into 5 separate files to keep from paging. And storage? I'm rendering straight to a PAR drive, so thats not a problem. Whats going to be real interesting is the final render's requirements with 3-4 VP layers (tons of storage…. I can easily clear up about 1.5 gigs HD space, but even with that my little Colorado 250 is going to be seeing alot of use), and I estimate about 120 – 140 hours rendering time. It would be real nice to have more than one machine at times like these, of course, I wouldn't mind a house or… lets say… a million dollors either! <g>