 | | 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 (...) (19 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 (19 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 (...) (19 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 (...) (19 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 (...) (19 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 (...) (19 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 (19 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 (19 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 (19 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 (...) (19 years ago, 9-Apr-05, to lugnet.cad.ray)
|
| |
| | Re: Raytracing a primarily black model
|
|
(...) I think I've decided just to use different colors instead of worrying about rendering black. I'll be easier to make it more photo-realistic this way. --Bram (19 years ago, 7-Apr-05, to lugnet.cad.ray, FTX)
|
| |
| | Re: Raytracing a primarily black model
|
|
(...) I've had some success with black parts and radiosity. You can view the results (URL) here> and let me know if you think the radiosity settings that I used would be helpful. Forgive me for inserting unofficial elements into the conversation, (...) (19 years ago, 7-Apr-05, to lugnet.cad.ray, FTX)
|
| |
| | Re: Raytracing a primarily black model
|
|
(...) Right...I was just wondering if anyone had particular settings they used in POV-Ray that worked well. Otherwise it's just that much trial and error on my part, which is really slow when you're using radiosity. --Bram (19 years ago, 7-Apr-05, to lugnet.cad.ray, FTX)
|
| |
| | Re: Raytracing a primarily black model
|
|
(...) Hi Bram, I'm not much of a ray tracing expert, but this is an issue that even LEGO has addressed. When I look at building instructions by LEGO, they translate black parts to a dark gray, almost the same color as the original dark gray. Many (...) (19 years ago, 7-Apr-05, to lugnet.cad.ray, FTX)
|
| |
| | Raytracing a primarily black model
|
|
Anyone have any tips for raytracing a black MOC with radiosity? I'd like some piece definition like this: (URL) What's the secret, Jeroen? Thanks, --Bram (19 years ago, 7-Apr-05, to lugnet.cad.ray, FTX)
|
| |
| | Re: LDraw's Autostep does not work in Lpub? [DAT]
|
|
(...) Autostep is not part of the LDraw file format, but specific to MLCad. Here is a specification of the official LDraw file format: (URL) is not the default in MLCad. At least not on my generic installation of MLCad. (...) Autostep is not a (...) (20 years ago, 21-Mar-05, to lugnet.cad.ray)
|
| |
| | Re: LDraw's Autostep does not work in Lpub?
|
|
(...) Hi Mitchell, LPub has no support for autostep. I didn't even know about it until you mentioned it. LPub supports STEP and ROTSTEP meta commands, but not autostep. If you read the LPub help file you wil find no mention of AUTOSTEP. Having made (...) (20 years ago, 21-Mar-05, to lugnet.cad.ray)
|
| |
| | LDraw's Autostep does not work in Lpub?
|
|
If I understand correctly, LDraw's Autostep is set as the default and requires no other changes (if you will accept a new step after adding each new part). However, I cannot get LPub to render anything but the complete assembly from a model designed (...) (20 years ago, 20-Mar-05, to lugnet.cad.ray)
|
| |
| | Re: Version 512 of the Library is available now.
|
|
(...) Thank you Ross, apparently I forgot that not everybody knows where I "live" on the Internet... :-) Greetz, Anton (20 years ago, 20-Mar-05, to lugnet.cad.ray)
|
| |
| | Re: Version 512 of the Library is available now.
|
|
(...) (URL) for the noobs ;) ROSCO (20 years ago, 20-Mar-05, to lugnet.cad.ray)
|
