 | | Anatomy of a POV file (e.g. L3P suggestions) —Michael Horvath
|
| | | Here are the basic components of a POV file, as it is generated by default by L3P. Materials Color declarations Stud-tops Finishes Render-Detail Options Qual SW Bumps etc. Scene-Level Objects Camera Lights Floor Background Parts & Primitives Models (...) (20 years ago, 20-Jan-05, to lugnet.cad.dev)
|
| | | |
| | | | | Re: Anatomy of a POV file (e.g. L3P suggestions) —Tore Eriksson
|
| | | | | (...) Optional, yes that would be nice. But I also see the strength in the fact that all data needed are gathered in the same file. I have downloaded so many pov-files just to discover that they have references to inc files I fail to find on the (...) (20 years ago, 20-Jan-05, to lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: Anatomy of a POV file (e.g. L3P suggestions) —Lars C. Hassing
|
| | | | | | | (...) For newbies I think it's nice that the POV file is self-contained and ready-to-render. However, using certain coming options you can exclude camera and lights. Why would you like submodels in separate .inc files ? Only to have a smaller (...) (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| | | | | | | |
| | | | | | | | | Re: Anatomy of a POV file (e.g. L3P suggestions) —Tore Eriksson
|
| | | | | | | | | (...) I am anything but an expert on this area, but will not the parts, 3001_dot_dat and so on, also be defined multiple times? (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| | | | | | | | | |
| | | | | | | | | Re: Anatomy of a POV file (e.g. L3P suggestions) —Kevin L. Clague
|
| | | | | | | | (...) Hi Lars, I'd prefer that the format is unchanged. Right now LPub post-proceses the one file, greying parts as needed, adjusting camera settings for orthographic, and creating new colors for the greyed pieces.... I'd really rather *not* have to (...) (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| | | | | | | | |
| | | | | | | Re: Anatomy of a POV file (e.g. L3P suggestions) —James Reynolds
|
| | | | | | (...) When you really get into POV-Ray, you have to deal with multiple files. If you ever include a graphic as a texture, or a height field, there is nothing you can do. You can't combine an image into a text file and have it work well. If you have (...) (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| | | | | | |
| | | | | l3p as open source (was: Re: Anatomy of a POV file (e.g. L3P suggestions)) —Niels Bugge
|
| | | | I don't know if this is besides the topic, but what I would really like was the ability to edit the "text" with the default settings l3p uses to create the pov-file (after all, it's a program that converts a textfile into another textfile). When (...) (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)) —Kevin L. Clague
|
| | | | | (...) 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)
|
| | | | | |
| | | | | | | Re: l3p as open source (was: Re: Anatomy of a POV file (e.g. L3P suggestions)) —Niels Bugge
|
| | | | | | | (...) 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 —Mark Tarrabain
|
| | | | | | (...) A nice thing about open source would be that it would be possible for other people to work on ports to different architectures other than the microsoft-based platform. While emulators may exist to allow people to get by for the time being, (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| | | | | | |
| | | | | | | | Re: l3p as open source —Kevin L. Clague
|
| | | | | | (...) L3P is available for the Mac and Linux.... Kevin (20 years ago, 29-Jan-05, to lugnet.cad.dev)
|
| | | | | | |
| | | | | | Re: l3p as open source (was: Re: Anatomy of a POV file (e.g. L3P suggestions)) —James Reynolds
|
| | | | (...) 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: l3p as open source (was: Re: Anatomy of a POV file (e.g. L3P suggestions)) —Niels Bugge
|
| | | | (...) I knew I'd forgotten something in here! That function sounds interesting and could help a bit, but I'm not sure it's possible to turn an .inc around, but I'll look into it when I get the time. Thanks -NB (20 years ago, 27-Jan-05, to lugnet.cad.dev)
|
| | | | |
