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 / 5526
5525  |  5527
Subject: 
Re: L3P v1.3 20010120
Newsgroups: 
lugnet.cad, lugnet.cad.dev
Date: 
Fri, 23 Feb 2001 01:33:12 GMT
Viewed: 
4880 times
  
Sproaticus wrote...
> Lars,
> 
> Awesome.  I tip my hat to you and Lutz.  :-,
> 
> I don't mean to complain, in fact I am currently trying to figure out a
> solution anyways, but I thought I'd raise these issues and see if anyone
> else has figured it out already.  Basically, some LGEO pieces are not
> directly compatable with the LDraw parts library and need some tweaking to
> come across properly after L3P-ing.
> 
> The inconsistencies I have found so far:
> 
> <part:3149> hinge 2x5 base in LDraw becomes <part:3145> tipper end after
> l3p+lgeo
> 
> <part:3942> cone 2x2 becomes <part:3943> cone 4x4 afterwards, as well.
> Renaming lg_3942.inc to lg_3943.inc doesn't work btw

Are you sure you have got ALL updates installed properly?
My L2P_ELMT.TAB is from 31-12-99 and the latest part is
lg_3873.inc from 23-09-99.

BTW, you can use the -d option to L3P to see the contents of LGEO's
*.TAB files: "l3p -d -lgeo somefile.dat | more"

> <part:4588> brick 1x1 round with fins doesn't exist in clear in lgeo, so
> there's some parsing problems with the POV file...weird

Yes, Lutz forgot the lg_4588_clear in that file...

> <part:6536> technic axle joiner perpendicular ends up rotated 90 degrees on
> the part's y axis after l3p+lgeo
> 
> It's fairly easy to fix these by hand in the POV file, but I'm not so sure
> how to fix the overall situation.  Changing either the LGEO library or the
> LDraw parts library would most certainly break existing models, and
> requiring L3P to handle these on a piece-by-piece basis would get to become
> a headache for Lars.  Unfortunately, the latter is the best solution I can
> think of so far.

L3P already has one exception: it adds a missing texture
"texture {lg_black}" to pattern lp_0008.inc used in lg_3626p01,
the Minifig Head with Standard Grin Pattern :-)
But, that's not the way to go...

> Actually, another possibility is for L3P to incorporate some kind of
> external lookup table, in a file which can be maintained separately from the
> L3P binary.  Perhaps a simple mapping from LDraw to LGEO with part number
> changes and translation matrix -- any parts not mentioned in the table would
> just go through as they do now, which would keep the table down to a
> managable size.

No, Lutz Uhlmann should be alerted and fix his files. Otherwise also L2P
would suffer from the same mistakes...

I also have a list of errors:
lg_0711.inc: "#declare lg_0709_clear" should be "#declare lg_0711_clear"
lg_6081.inc lacks lg_6081_clear
wrong offset in z  lg_6832.inc  Windscreen  4 x  4 x  1
lp_0008.inc: missing "texture {lg_black}"
lg_cyan, lg_tan, lg_orange, lg_clear_brown, lg_clear_neon_orange are
missing in L2P_COLR.TAB

Lutz should also consider making a new version of L2P_ELMT.TAB,
preferably in text rather than binary.
The current format is inadequate for a conversion table between
DAT filenames and LGEO filenames: He only uses an integer for the
DAT file number (again, try: "l3p -d -lgeo somefile.dat"), which cannot
handle all our letter suffixes properly.
But I've already suggested that to him long ago...

> Anyway, I love the changes you've made to L3P Lars; incorporating Lutz's
> LGEO parts has really spiffed up my microfig collection.  :-,

Thanks.
/Lars



Message has 1 Reply:
  Re: L3P v1.3 20010120
 
(...) Huh. I downloaded the complete set, but my L2P_ELMT.TAB is from 25-1-1999. The other timestamp is off too. I figured this could be an old LGEO install, but I tried again on a fresh machine and I still have the older files. Exactly which file (...) (26 years ago, 23-Feb-01, to lugnet.cad, lugnet.cad.dev)

Message is in Reply To:
  Re: L3P v1.3 20010120
 
Lars, Awesome. I tip my hat to you and Lutz. :-, I don't mean to complain, in fact I am currently trying to figure out a solution anyways, but I thought I'd raise these issues and see if anyone else has figured it out already. Basically, some LGEO (...) (26 years ago, 16-Feb-01, to lugnet.cad, lugnet.cad.dev)

11 Messages in This Thread:





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

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

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