 | | Re: Set 8652 Render
|
|
(...) How did this post slip under my radar? Sorry for the delay in replying. Anyway, yes I will share the MPD. Give me a week (I promise). -Orion (20 years ago, 25-Apr-05, to lugnet.cad.ray)
|
| |
| | Re: Set 8652 Render
|
|
(...) Any chance you can share the DAT files? (20 years ago, 17-Apr-05, to lugnet.cad.ray)
|
| |
| | Re: L3P Options?
|
|
(...) I'd be willing to look at a beta version. I'm even happy to look at code (assuming its in something I know) if you like. Tim (20 years ago, 14-Apr-05, to lugnet.cad.ray)
|
| |
| | Re: L3P Options?
|
|
(...) 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)
|
| |
| | Re: L3P Options?
|
|
(...) 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?
|
|
(...) I'd be willing to try and give it a go. I'm still working on a new front end to it (allows automation and a few other things specified in the draw file itself) The current build is at: (URL) Dean Earley, Dee (dean@earlsoft.co.uk) irc: (...) (20 years ago, 13-Apr-05, to lugnet.cad.ray)
|
| |
| | Re: L3P Options?
|
|
(...) Sure, I already had you and a few others in mind, exactly because I'm aware of your "dissection" and others heavy color redefinition. But if anyone else is ready to spend some time with a beta, and give some feedback, please send me a mail. (...) (20 years ago, 13-Apr-05, to lugnet.cad.ray)
|
| |
| | Re: L3P Options?
|
|
(...) 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?
|
|
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)
|
| |
| | Re: L3P Options?
|
|
(...) Sorry! I guess I didn't make my question clear enough. I'd like to substitute the primitives still, but with those of my own creation, rather than those that L3P creates. For example I think a stud looks better with a slightly rounded top (a (...) (20 years ago, 12-Apr-05, to lugnet.cad.ray, FTX)
|
| |
| | Re: L3P Options?
|
|
(...) Yep. -p Don't substitute any primitives in the P directory with POV equivalents ---...--- In order to have a nicer looking image some parts (primitives) in the P directory are by default substituted with POV equivalents. E.g. 4-4cyli.dat is (...) (20 years ago, 12-Apr-05, to lugnet.cad.ray)
|
| |
| | L3P Options?
|
|
Dear Lars (and anyone who can answer my questions) I was wondering if there was a way to use L3P so that it does NOT include its primitives in the final .pov file? The reason for this question is that I'd like to be able to adjust some of the (...) (20 years ago, 12-Apr-05, to lugnet.cad.ray)
|
| |
| | Version 513 of my Library is available now.
|
|
Version 513 of the Library can be found on my website now, 9 new pieces have been added. As always you can find all of the changes to the Library in the included "considerations.txt" file. The address is: (URL) Anton (20 years ago, 10-Apr-05, to lugnet.cad.ray)
|
| |
| | Re: Raytracing a primarily black model
|
|
(...) (URL) only is white on red easier to render than blue on black, it will probably show the detail better in print. Thanks for the suggestions though, --Bram (20 years ago, 9-Apr-05, to lugnet.cad.ray)
|
| |
| | Re: Raytracing a primarily black model
|
|
"Bram Lambrecht" <lego@bldesign.org> schreef in bericht news:IEL8K5.36t@lugnet.com... (...) Ah c'mon Bram, don't give up so easily! Show us your secret project! Jeroen (20 years ago, 9-Apr-05, to lugnet.cad.ray)
|
| |
| | Re: Raytracing a primarily black model
|
|
"Bram Lambrecht" <lego@bldesign.org> schreef in bericht news:IEKDJ4.ro1@lugnet.com... (...) Hi Bram, The secret is: don't use radiosity! Haha. But seriously: as far as I remember the Hudson posters are done without radiosity. It can be done but you (...) (20 years ago, 9-Apr-05, to lugnet.cad.ray)
|
