|
|
 | | Re: L3P Warnings
|
| (...) LDView already has the ability to do this automatic replacement during POV export: Create a POV directory inside your LDraw directory Put p an parts directories in the POV directory Drop in POV files with the same filenames as the original (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray, FTX)
| | | | | Re: L3P Warnings
|
| (...) Thanks, but no, I don't get irritated so no need for yet another parameter to silence certain warnings. I was just a little worried. And if a future version of L3P will no longer support inline code, I'll probably stick to 1.4 Beta - if not (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| In lugnet.cad.ray, Dave Schuler wrote: <snip> (...) See also my reply on Tore Eriksson message. It would be called 3001.pov and has the same information in it as the 'else' portion of the current dat files (although without the leading 0's, it would (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| In lugnet.cad.ray, Tore Eriksson wrote: <snip> (...) alternatives. In that case I think Don is right, just ignore the warnings and keep doing what you like. I doubt Lars will stop supporting his own LDraw meta extensions altogether. (...) The thing (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| (...) I think I've got a solution for you and Dave. Stop worrying about the messages. ;) No, really. The current version of L3P still does what you want, right? And I think we can safely predict that the next non-beta version of L3P is highly (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| (...) But does such an export include the POV-enhanced parts in proper matrix alignment, or does the user have to figure out how to orient the part to match the output file? If the latter, then it's equivalent to not supporting the POV-Ray elements (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| --snip-- (...) LGEO was updated fairly recently (in the last two years anyway) so it's definitely being updated sometimes. The newer LDView releases also make POVray export very easy and you can add parts you've made yourself simply by editing a (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| (...) This hits on the main issue, as far as I'm concerned. There are certain elements that simply can't be rendered well within the constraints of the official, accepted LDraw code language. My interest, of course, is in clone elements. I grant (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray, FTX)
| | | | | Re: L3P Warnings
|
| (...) I guess there we have the really big problem. We all have our own LDraw universes, and we all use LDraw for so very different purposes, different tools of choise, different approaches, different thinking, different ways to solve problems, (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| (...) I'm not conversant with LGEO or the like; what would the filename format be for these alternate parts? That is, if a 2x4 brick is 3001.dat, what's the equivalent name of the LGEO version? I ask because I like sticking with the DAT suffix, and (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
|
|
