CompuServe Thread

Dave, John beat me to the punch-line while I was typing. Well, here's some things I've learned. There are two ways to render from DOS outlined in the Advanced User Guide, Batch Rendering and Network Rendering (you don't need a "network" to do network rendering). I use both depending on my current situation. Here's an example batch file: 3ds set=bigjob.set render /w640 /h480 /8Cpal2.flc bigjob.prj /Itest1.flc /#0,90,1 This should be easy to understand by following the command table in the manual. I have set this up to use my custom SET file, to render a 640×480 flic from BIGJOB.PRJ, use the custom palette PAL2.flc (using the procedure recommended for custom palettes), render frames 0-90 with a step rate of 1 to TEST1.flc. I might use this kind of batch file when I can't setup the network queue. Note that most of these parameters are remembered if you save them with the PRJ file. NOTE: If you have liquid speed and you do not have the hardware key installed, it will stall the batch process and make you press a key to continue. This makes running multiple batch files unattended impossible. The only way around this is to MOVE the LSPEED.RES and VGLSPEED.VLM out of the 3DS root directory. Move them to a temporary directory like LSPEED, and copy them back when you need them. The most effecient way of DOS rendering is the NET QUEUE. You can do this on a single computer. As you work during the day, you can batch jobs, samples, tests, etc. in the NET QUEUE. At the end of the day, if you need to move your hardware key to another computer – go to DOS and type 3DS SLAVE. Be aware of the same lspeed problem. byron