 | | Re: First version of DAT2RAV File
|
|
(...) I love the idea of using Anton's LIB but I have lots of questions like: What coordination system I should or can use? . The L3P coordination system as we are doing until now? . Or anton's ways? I prefer the old way as we are just to. Same with (...) (21 years ago, 24-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | First version of DAT2RAV File
|
|
Here's the initial version of a compatibility wrapper, allowing you to easily use parts from Anton Raves' POV-Ray library in L3P-generated model files. Save the following text to a file, add a #include statement to your L3P model file, and then (...) (21 years ago, 24-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) Good point. As I wrote in another post, we could keep the individual part files on a dev server, and distribute a single combined file. Or store all the individual definitions in a SQL database. (...) Ack! I better post my work soon, or it (...) (21 years ago, 24-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) AFAIK, they have to be explicitly included. (...) Not really, because then there'd be an issue of search order order, too much complication. (...) I prefer to keep it simple -- either one big file with everything in it, or one master file that (...) (21 years ago, 24-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) For one, I'm not keen on putting POV-Ray code in LDraw part files. Besides complicating the review/certification process, it also ties the LDraw library to one specific renderer, in an official way. Steve (21 years ago, 24-Jul-03, to lugnet.cad.dat.parts)
|
