 | | Re: Parts editing made easy, anyone?
|
|
(...) Yes, since it is text based. Also, a most new authors learn by examining the code. (...) Unneccessary memory usage and file size. (...) L3P (and other converters/viewers) detect these primitives and convert them to smooth objects (e.g. L3P (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: l3p as open source (was: Re: Anatomy of a POV file (e.g. L3P suggestions))
|
|
(...) Why don't you create your main scene file that never changes and then just include the l3p output file into your scene file. I believe Lars is working on options that leave out the povray code that is required to be in the main file (like (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) Why? Is the .DAT file supposed to be readable by humans? Why? ;) What's wrong with the larger number of polygons? What positives (from the side of the automated rendering process) does bring the existence of primitives? What's wrong with the (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: l3p as open source (was: Re: Anatomy of a POV file (e.g. L3P suggestions))
|
|
(...) Hi Kevin Thanks for your tip, but even though it seems to solve the amb/dif/reflection-problem, it unfortunately doesn't cover the need for special pov-ray objects like special lights, fog etc, as it's also based on L3p. Another thing I just (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev, FTX)
|
| |
| | Re: l3p as open source (was: Re: Anatomy of a POV file (e.g. L3P suggestions))
|
|
(...) An alternative to open source is to post process l3p output to change things the way you want. This is what I do in LPub. L3P output is simple text and extremely consistant, making it easy to modfiy the contents. Kevin (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
