| | Re: L3P Options? Timothy Gould
|
| | (...) That is excellent news! I missed the first post (ref'd above) but that is exactly what I meant. Would it be possible to include a file in the directory with a name like L3Colours.inc or something that declares any modified colours one wishes (...) (20 years ago, 13-Apr-05, to lugnet.cad.ray)
|
| | |
| | | | Re: L3P Options? Lars C. Hassing
|
| | | | (...) There will be the following include file options: -ib<file> include file at beginning of POV file -ic[<file>] no camera, optional include file -il[<file>] no lights, optional include file -ie<file> include file at end of POV file But are you (...) (20 years ago, 13-Apr-05, to lugnet.cad.ray)
|
| | | | |
| | | | | | Re: L3P Options? Ross Crawford
|
| | | | | (...) I would think if any "system-wide" or "shared" files are included they should by default be inlined, as any changes would affect (maybe deterimentally) previous renders. Any project-specific files I create always get saved locally, so I see no (...) (20 years ago, 13-Apr-05, to lugnet.cad.ray)
|
| | | | | |
| | | | | | Re: L3P Options? Timothy Gould
|
| | | | (...) That all sounds perfect. I really like the idea of L3Begin.inc and L3End.inc as well. I think that is a brilliant solution. As for the inline/not-inline option, for L3Begin, L3End and L3Colours I think it should default to inline but be (...) (20 years ago, 14-Apr-05, to lugnet.cad.ray)
|
| | | | |