To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cadOpen lugnet.cad in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / *46406 (-5)
  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)


Next Page:  5 more | 10 more | 20 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR