Subject:
|
Re: L3P, an apology (Was: lgeo library)
|
Newsgroups:
|
lugnet.cad.ray
|
Date:
|
Mon, 2 Sep 2002 12:06:13 GMT
|
Viewed:
|
1153 times
|
| |
|
|
In lugnet.cad.ray, Jeroen de Haan writes:
> 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 POV-Ray version
> 3.1 and POV-Ray 3.5 can generate errors when parsing this code.
> These errors (or actually this error) only occurs when you use the
> LGEO-parts and can be cured by the small tweak mentioned in my last post.
Actually I think the problem lies in PovRay.
A while ago Brian Ulmer pointed to a PovRay bug-report at
http://news.povray.org/povray.general/25705/
where 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 Colors_Inc_Temp = version;)
I inserted the "#version 3.5;" and haven't seen any problems so far.
> I hope I didn't upset Lars (or anyone else) with my last post and I want to
> apologies if I did; L3P is a fine piece of software which adds a lot to the
> LDraw community.
No it's OK, I haven't tested ALL variants of L3P output,
so please let me know if you find some 3.5 issues.
/Lars
|
|
Message is in Reply To:
 | | 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)
|
11 Messages in This Thread:
   
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
