To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.rayOpen lugnet.cad.ray in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Ray-Tracing / 2970
2969  |  2971
Subject: 
Re: L3P Warnings
Newsgroups: 
lugnet.cad.ray
Date: 
Thu, 1 Jul 2010 19:31:24 GMT
Viewed: 
33729 times
  
In lugnet.cad.ray, Roland Melkert wrote:
   In lugnet.cad.ray, Dave Schuler wrote: snip
   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 using the official part names (3001) simply makes the most sense.

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 be pure povray script).

snip
  
   So perhaps you are hinting on maintainability or mixed single files (because even subfiles would work ok using a mirror tree, aslong they use the same scale and orientation (or are supplied with a transformation key).

Not sure I understand this part. Are you suggesting that the inlined POV-Ray code might be housed in a subfile? I could see that working, actually, though I’m not the person to generate the protocols to parse it.

I mean you could only put eg a p\stud.pov in the mirror tree and the converter tools would use the pov version for all studs in the scene when generating the povray version of the scene.

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 .dat files (but with a .inc extension instead of .dat). (Note that the last #declare in the file is expected to be the #declare for the file’s geometry.)
  • Check the “Search for POV replacements for LDraw parts” check box in the Native POV Geometry box of the POV Export Options dialog in LDView.
Note that I don’t remember off the top of my head what happens if you have that checked along with “Use XML mapping file”. I think the POV replacements only happen for files that don’t get found in the XML mapping.

--Travis



Message is in Reply To:
  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)

46 Messages in This Thread:













Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

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