 | | Re: Anatomy of a POV file (e.g. L3P suggestions) —Tore Eriksson
|
| | | (...) Optional, yes that would be nice. But I also see the strength in the fact that all data needed are gathered in the same file. I have downloaded so many pov-files just to discover that they have references to inc files I fail to find on the (...) (20 years ago, 20-Jan-05, to lugnet.cad.dev)
|
| | | |
| | | | | Re: Anatomy of a POV file (e.g. L3P suggestions) —Lars C. Hassing
|
| | | | | (...) For newbies I think it's nice that the POV file is self-contained and ready-to-render. However, using certain coming options you can exclude camera and lights. Why would you like submodels in separate .inc files ? Only to have a smaller (...) (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: Anatomy of a POV file (e.g. L3P suggestions) —Tore Eriksson
|
| | | | | | | (...) I am anything but an expert on this area, but will not the parts, 3001_dot_dat and so on, also be defined multiple times? (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| | | | | | | |
| | | | | | | Re: Anatomy of a POV file (e.g. L3P suggestions) —Kevin L. Clague
|
| | | | | | (...) Hi Lars, I'd prefer that the format is unchanged. Right now LPub post-proceses the one file, greying parts as needed, adjusting camera settings for orthographic, and creating new colors for the greyed pieces.... I'd really rather *not* have to (...) (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| | | | | | |
| | | | | Re: Anatomy of a POV file (e.g. L3P suggestions) —James Reynolds
|
| | | | (...) When you really get into POV-Ray, you have to deal with multiple files. If you ever include a graphic as a texture, or a height field, there is nothing you can do. You can't combine an image into a text file and have it work well. If you have (...) (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| | | | |
