It looks like I was too hasty in adding Olive Green and assuming that it was the The LEGO Group's Color 326 Spring Yellowish Green. Now that Bricklink is selling Yellowish Green; it is obvious that Yellowish Green matches TLG's Spring Yellowish Green. Olive Green seems to match as close to Spring Yellowish Green as it does Faded Green, so it will be matched with LEGO ID 210 Faded Green.

I plan on changing our LDraw Color ID of Olive_Green from 326 to 210, and adding the new color Yellowish_Green with Color ID 326.

Please let me know if anyone has any major objections to this, but this post is mostly to inform anyone working on these parts:
973pb990
3626cpb669
98166pb02
DARaptor2
DATRex3
DAPtera3
98086pb02
bb539c02

that Olive_Green will soon be code 210 instead of code 326.

I won't be so hasty in the future to release a new LDconfig at the beginning of the year...I'll wait until enough of the new colors are out in the wild that making matching decisions will be more straight forward.

Thanks,
Scott

EDIT: Added an [attention part authors] to help those who should read this to read this. TG

Chris,

what are the filepaths for Alias and Physical_Color under:

http://www.ldraw.org/library/official/<filepath> ?

Thx, w.

I response to complaints about my (inadvertent) use of alias parts, I wrote a PHP script that updates a model file to not use them. This could easily be extended to also handle MovedTo and Physical Colour parts. Is there any interest in this being hosted on the LDraw.org servers?

Attached Files

  update.php (Size: 2.29 KB / Downloads: 0)

http://www.buildwithchrome.com/static/map

Very cool idea.

I made this set in 2008, I discovered MLCAD, afterwards I bought truth.

Attached Files

  10179.ldr (Size: 352.39 KB / Downloads: 10)

Hey,

Here is the new, (hopefully) bug-free LPC 1.3.8


Please uninstall older versions of this software before installing a new version.
Your configuration won't be deleted if you have already version greater than 1.3.1 installed on your machine.

Change log:

New features:

• The background image is stored in the LPC-file. It will be synchronised with your local image file. The image will be exported to the same directory of the LPC file, if the original image (with an identical path and filename) is not located on your harddisk. This will be done only once and as a result, the LPC file will refer to the exported image.
  
• LPC is since version 1.3.6 full backwards and forwards compatible. That means, that you'll be able to open files from 1.3.7+ with version 1.3.6, too.
  
• Minor improvements for LDraw subpart handling
  

• The background image is not shown after loading a file
  
• The DAT-export creates wrong matrices for subfiles.
  
• "Delete"/​"Cut" does not delete the metadata of subfiles and groups (leads to a crash on export and metadata edit).
  
• "Ungroup" does not delete the metadata of subfiles and groups (leads to a crash on export and metadata edit).
  
• Undo/​redo could cause indirectly a crash+bad data when using groups/​primitives.
  
• The "Unsaved Changes" warning still appears after the file was saved.
  
• There is a memory leak in the LPC file loader.
  
• There are issues on the first start of the application in the "Advanced Options" menu.
  
• LPC stops at reading a *.lpc file. As a result, the vertices are displayed only.
  

I recently updated 577.dat to correct a handful of issues with it.
To support the length and hole depth corrections, the shortcuts used by the minifig generator were also updated.
There is some discussion at 577c01.dat & 577c02.dat regarding these.

I don't think a 10-year old part should be made obsolete, especially in this case.

I expect the users of the shortcuts are accustomed to having the light.dat in them, and that positioning them to get the desired effect would be difficult if they weren't there.

I do think that the new c03/c04 descriptions are better to suit the chrome hilt, but possibly adding 'Lit' to these should suffice rather than making them obsolete, grandfathering the use of light.dat here.

Please weigh in if you care if the current shortcuts should be made Obsolete or not.

Hello to all! I've been using LDraw for seven years and have designed both LEGO and "non-LEGO" parts alike. My portfolio can be seen here. To note, some parts are my own custom design and therefore not true LEGO, though I made the effort to fit them within the LEGO spirit and theme. I hope you like!

I am interested in connecting personally with those who share my interest in design as well as POV-Ray; my LinkedIn profile is here.

I Have a problem regarding LEOCAD.

I'm designing my robot in MLCAD and when I try to open it in LEOCAD some parts are missing.
I tried to update the pieces list of LEOCAD but with no success.

Any suggestions please?
Thanks in Advance,

Hello,
there is a problem of connection with the part 2859.
See attached picture

No problem with the part 2861 (point left)

Thank.

Attached Files

  Track.ldr (Size: 7.34 KB / Downloads: 2)