 | | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Now that would rock. For my personal use, this would almost entirely solve the problem. I could whip up a single file that contains all the parts I want to fix, run it through L3P, manually fix the parts in the resulting file, and then include (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) I asked Lars a while back if he could wrap all the part definitions with IF NDEF statements so that someone could define the parts they wanted in an external include file and the rest would use the standard L3P code. Hopefully when a new (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Because parts with inline POV code work with the version of L3P that we have now. Why not start by building a library of modified official parts, but with the explicit goal of eventually converting them into POV only parts when L3P or some (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest? [DAT]
|
|
(...) Here is my $0.01.... This is how I have started handling Ldraw/PoV parts: The 3626bp6f.dat is availabe on the parts tracker here: (URL) is some line wrapping happening here, I will need to fix it later) 0 Minifig Head with Female Eyes with Red (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Inline POV code in official parts?
|
|
(...) I agree with Steve on this issue: no POV code in offical parts with the possible exception of primitves. I feel this way for a few reasons: - It could be construed the POV is the Official rendering program of the LDraw.org library. This can (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
