CompuServe Messages

Nik, Thanks for your reply. It turned out to be a problem with the way DOS interprets the "=" sign in a batch file. The "=" is dropped….. Maybe this could be wishlist requirement: maybe change the command line parameters for a future 3D Studio. I'd suggest something more along the lines of a unix "switch" thing: 3DS -s M64.set That way, there's no characters that get dropped by dos or unix in case of a batch file or a script file, respectively. This could be improved a little further: just make some environment variables that could carry this info, similar to what AutoCAD does. For example, I would suggest two things: – Use a variable to find an alternate "SET" thing. This would be the default that could be overridden by the switches on the command line. For example: set 3DSCFG=D:\3ds4\Config1\M64.SET An advantage: the SET file could then be anywhere on the system. – Use a variable to point to a directory where it can find the 3DSNET.SET file. For example: set 3DSNET=D:\NET This would work quite well, and will avoid the problem of having 3D Studio loaded on EVERY machine you want to use for rendering. What if you want to run 3DS for Network rendering from a common network installation? Curently, you have to run it locally in order for it to have a different 3dsnet.set file for each machine. A royal pain. I'd appreciate knowing if this is something that makes sense, or it is just me going around the bend? I'd love to hear from you and Brian and anyone else on this matter. Mark K. Please see my reply to Brian Rudolph on this.