|
| | Re: L3P Options?
|
| In lugnet.cad.ray, Lars C. Hassing wrote: <snip> (...) Hi Lars, Before you release, would it be possible for me to have an advanced copy of L3P, so I can adjust LPub to handle the new format? LPub does post processing of the L3P generated POV file (...) (20 years ago, 13-Apr-05, to lugnet.cad.ray)
| | | | Re: L3P Options?
|
| (...) 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?
|
| (...) You'll be happy to know that the coming L3P (yes, I know I've said that too often) has #ifndef's around everything, e.g.: //// Primitive stud.dat #ifndef (stud_dot_dat) #macro stud_dot_dat(L3ArgTe...,L3ArgMat) L3MacroBegin("stud_dot_dat") #if (...) (20 years ago, 12-Apr-05, to lugnet.cad.ray)
| | | | Re: Raytracing a primarily black model
|
| OK, you did that on purpose! Given the title of the folder, I've gotta ask - What Magazine? (great renders, btw) James Wilson Dallas, TX (20 years ago, 12-Apr-05, to lugnet.cad.ray)
| | | | Re: L3P Options?
|
| (...) You got it. 0 L3P IFPOV meta-statements are probably the way to accomplish what you want. Hmm, thinking more about it (I could just go try it), you'll probably still need l3p's -p parameter, or l3p probably won't even look at the primitive (...) (20 years ago, 12-Apr-05, to lugnet.cad.ray)
| |