| | Re: New LDConfig.ldr color file
|
|
(...) As far as I remember LDView does a more than decent job converting to PovRay as well as viewer so there is actually no need for L3P or L3Lab - not counting in that accordingly the L3P page (URL) supports the LDConfig.ldr file: "Colors from (...) (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: New LDConfig.ldr color file
|
|
(...) Well, actually there are two forbidden zones; the small at colors 29 through 31 and the large at 48 to 255. Color numbers within those ranges generate errors if used in L3P and L3Lab. In original LDraw and other really old programs, colors (...) (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: New LDConfig.ldr color file
|
|
(...) This can be done with the caveat that we start with something like say 2001 or 3001 in order to preserve the original LEGO numbering starting from 1 to 300. for 2001 the TLG color number would be "#7D1". Correct? w. (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: New LDConfig.ldr color file
|
|
(...) Could you be a bit more precise. What is the "Forbidden zone"? w. (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: New LDConfig.ldr color file
|
|
(...) renamed to "ldcfgalt.ldr" (...) Hmmm this would be best solved with an additional command in the file - say CATEGORY or CLASTER or whatever. Anyway, modifications to the synthax can only be applied by the LSC. (...) Good point. I'll modify the (...) (15 years ago, 29-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: New LDConfig.ldr color file
|
|
(...) for MLCAD use: (URL) (15 years ago, 28-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: New LDConfig.ldr color file
|
|
(...) <snip a lot of info> Seems like quite an undertaking. (...) My vote would go to keeping the old ldraw colors, like said else were most monitors aren't calibrated. (...) I don't know about other software but my LD4DStudio uses the config file (...) (15 years ago, 28-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: New LDConfig.ldr color file
|
|
(...) All new color codes except 313 Maersk Blue generate errors in L3Lab and L3P because the numbers just had to be picked from the forbidden zone... :( :( :( /Tore (15 years ago, 28-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: New LDConfig.ldr color file
|
|
(...) I don't really know what I'm talking about here, but I think there might be a big difference between the representation of RGB values in a dye based color system for bricks, another one for printing on paper, and a color system for computer (...) (15 years ago, 28-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: New LDConfig.ldr color file
|
|
(...) SNIP (...) So it'd be goodbye for Stone Gray? :-( Well, I can live with that.. (...) Nice! :-) SNIP (...) Hmm... looking at the new colours I'd be otherwise fine sans the new Black... looks too bluish for me. (...) Well that's going to be (...) (15 years ago, 28-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | New LDConfig.ldr color file
|
|
Hi folks, working on and off for almost a year with Scott Wardlaw, Alex Taylor and with the help from Joshua Delahunty we put together a new LDConfig file which hopefully fills in where the old version failed: (URL) file has the following (...) (15 years ago, 28-Jul-09, to lugnet.cad, lugnet.cad.dev.org.ldraw, lugnet.announce) !
|
|
| | Re: L3P -check Messages and hold votes
|
|
(...) Partly correct. I used an open source version of pascal to compile this program. Since it's not win specific, it's probably not as optimized to the win platform as Delphi is. -Orion (15 years ago, 20-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: L3P -check Messages and hold votes
|
|
(...) This is for Mac OS and windows OS at the same time. I think LDDP is only for WinOS. (15 years ago, 18-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: L3P -check Messages and hold votes
|
|
(...) I wonder why this windows execute is soooo large (12,6 MB!) and LDDP is only 1,9 MB?. cu mikeheide (15 years ago, 17-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: L3P -check Messages and hold votes
|
|
(...) Current version of DATHeader checks this. (...) Please see the document what DATHeader is testing for at (URL) the POV code test I think it is a complete list of things that got a hold vote or at least not certified on the PT during the last (...) (15 years ago, 17-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: L3P -check Messages and hold votes
|
|
(...) That's only true if the polygons are the same color. If they're different colors, it's an error. I've seen official parts with overlapping polygons that are different colors. --Travis (15 years ago, 16-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: L3P -check Messages and hold votes
|
|
(...) I'll look into this. The !LICENCE check is case sensitive so unless you have exactly what's in the spec, it will complain. (...) The Lib Spec says that 3 decimal places is enough in most cases (4 for scalable primitives). This would be a (...) (15 years ago, 16-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: L3P -check Messages and hold votes
|
|
(...) It complains with invalid !license on files that seem ok to me. (...) What do you mean? (...) I think it could be done. But is it really necessary? Thresholds would need to be defined too... Philo (15 years ago, 16-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: L3P -check Messages and hold votes
|
|
(...) Try out LDraw Validator: (URL) zip file contains both a Windows and OS X binary. I'll post the source once the program is complete. What it checks: - Compliance with header spec (mostly, see below) - Compliance with !CATEGORY and !KEYWORDS (...) (15 years ago, 15-Jul-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: L3P -check Messages and hold votes
|
|
(...) I suggest to use LDDP or Datheader instead. Both of them include the correct code to check for non-coplanar quads and are more convenient to use. Planarcheck should only be used by parts authors to automatically split non-flat quads. (...) (...) (15 years ago, 12-Jul-09, to lugnet.cad.dev.org.ldraw)
|