 | | Re: lgeo library
|
|
(...) 1) Are you using POV-Ray 3.1g? 2) Did you provide POV-Ray with the following in the commandline? +L<LGEO file path> NO SPACE BETWEEN +L and <LGEO file path> 3) Can you send me your POV file and your .ldr file to me so I can see. -AHui LDraw (...) (22 years ago, 2-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: lgeo library
|
|
here are the steps that i'm taking 1. convert model from .dat to .pov with -l 2. load file into POV-Ray 3.5 for windows 3. hit the Ini button 4. use command; +LC:\LDRAW\lgeo 5. hit set but don't render 6. hit run. a file is opened in POV-ray called (...) (22 years ago, 2-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: lgeo library
|
|
(...) There are some new options in POV-Ray 3.5 that confict with POV-code that L3P writes and is used in the LGEO parts, but there is a solution. Read it here: (URL) isn't it! Jeroen (22 years ago, 2-Sep-02, to lugnet.cad.ray)
|
| |
| | L3P, an apology (Was: lgeo library)
|
|
Hi, In my last post I may have given the impression that L3P writes "bad" POV-code that doesn't work. This isn't so of course and it wasn't my intention to give anyone that impression. What I wanted to say was that L3P writes code optimized for (...) (22 years ago, 2-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: L3P, an apology (Was: lgeo library)
|
|
(...) Actually I think the problem lies in PovRay. A while ago Brian Ulmer pointed to a PovRay bug-report at (URL) the 3.5 inlcude file colors.inc was reported to be missing a #version 3.5; at the top of the file (after line 9 (#declare (...) (22 years ago, 2-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: lgeo library
|
|
(...) use -lgeo if you want Lgeo parts -l means "use light.dat files" as light sources. (...) See fix in (URL) (22 years ago, 2-Sep-02, to lugnet.cad.ray)
|
