|
| | Re: Batch .pov file creation?
|
| (...) It might be easier to move the camera according to the clock variable, and go with the filenames POV gives you (e.g. scene001.tga, scene002.tga, etc.) If that doesn't work for you, I might be able to whip up a quickie Perl script that will (...) (23 years ago, 28-Sep-01, to lugnet.cad.ray)
| | | | Batch .pov file creation?
|
| Can anyone tell me how to create a series of .pov files all with a slightly different name (i.e. file01.pov, file02.pov, etc.) that has slightly different camera coordinates for each file? Basically I am trying to create a series of rendered images (...) (23 years ago, 28-Sep-01, to lugnet.cad.ray)
| | | | Re: Smooth surfaces
|
| (...) I agree with Steve. My program is processing mesh by mesh, try it by using the clipboard-feature. You would give away control facilities if there's no control in the dat-file. I'm not familiar with the dat-fileformat and the processing of L3P, (...) (23 years ago, 28-Sep-01, to lugnet.cad.ray)
| | | | Re: Smooth surfaces
|
| My thought was that the smoothing could be turned on and off, as appropriate. That would require metastatements in the parts files. Extra metastatements will slow down processing, but not by very much. They will also increase file size, but again, (...) (23 years ago, 24-Sep-01, to lugnet.cad.ray)
| | | | Re: Smooth surfaces
|
| Instead of shoving all these metastatements into files, maybe a file conversion utility (DAT -> POV) should keep an INI file that records which parts can be processed in this way, and which cannot. I'm basing this suggestion on the assumption that (...) (23 years ago, 22-Sep-01, to lugnet.cad.ray)
| |