To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 10337
10336  |  10338
Subject: 
L3P-Bug using LGEO
Newsgroups: 
lugnet.cad.dev
Date: 
Mon, 14 Nov 2005 15:33:58 GMT
Viewed: 
2351 times
  
hi lars,

looks like L3P doesn’t distinguish between part-files (.dat) and scene-files
(.ldr) when I use LGEO parts.

have a look at the following pic. when I render a .mpd (which containes the
subfile 926.ldr refering to the sets number) without LGEO I get a fine
result:



using LGEO-parts L3P substitutes the subfile 926.ldr with part
“32014 - Technic Angle Connector #6” ‘cos “lg 0926.inc” has an inbuild
move-to command (lg 0926 moved to lg 32014) to the Technic
Angle Connector #6:


you can download the related .mpd and .pov from:

http://www.holly-wood.it/tmp/l3p-bug.zip

I’m well aware that LGEO gets more and more outdated, but because of the
fantastic quality of the parts I’d like to stick to them as long as I can. it
would be great if L3P could distinguish between .dat and .ldr ... and use
anton raves parts for those not available in LGEO ;-)

bye, w.



Message has 3 Replies:
  Re: L3P-Bug using LGEO
 
I agree and disagree with this. I agree that it would be good (for now) if L3P only substituted LGEO parts for files with a .dat extension. Or, even better, if (a) the file being substituted has the UNOFFICIAL/LDRAWORG meta-statement and states it (...) (19 years ago, 14-Nov-05, to lugnet.cad.dev, FTX)
  Re: L3P-Bug using LGEO
 
(...) Getting back to the problem at hand, yes I do think this is a bug in L3P, the line specifically says include 926.ldr. Maybe L3P should include the extension as part of the inc file name unless it is .DAT? Of course that will break if the parts (...) (19 years ago, 15-Nov-05, to lugnet.cad.dev)
  Re: L3P-Bug using LGEO
 
(...) Yes, I would be great. But while it doesn't distinguish, we have to deal with it. I think the naming convention we had had before the .ldr extension, with officicial models named m926.dat and so on, solves this problem. So I suggest you name (...) (19 years ago, 15-Nov-05, to lugnet.cad.dev)

19 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