LDraw.org 2020-03 Parts Update Now Available

[Chris Dee]

The 2020-03 LDraw Parts Update has been now been released. This adds 1315 new files to the core library, including 829 new parts and 66 new primitives.

Thanks are due to all the part authors who created or corrected parts for this release. The small, but dedicated, band of reviewers also play an important role in keeping files moving through the Parts Tracker and deserve just as much credit. 

You can preview the new parts in 2020-03 here, and download the zip-file update or Windows install package here. Alternatively you can use the LDView menu option File | Check for Library Updates... to install the update.

[Philippe Hurbain]

The 2020-03 LDraw Parts Update has been now been released. This adds 1315 new files to the core library, including 829 new parts and 66 new primitives.

Thanks are due to all the part authors who created or corrected parts for this release. The small, but dedicated, band of reviewers also play an important role in keeping files moving through the Parts Tracker and deserve just as much credit. 

You can preview the new parts in 2020-03 here, and download the zip-file update or Windows install package here. Alternatively you can use the LDView menu option File | Check for Library Updates... to install the update.

Yeah ! Thanks a lot Chris!!!

[Max Martin Richter]

Thank you! Just a kind of a delayed Christmas present. ;-)

[Magnus Forsberg]

Great!
Now I have to rearrange my libray again.

[Steffen]

thank you very much, Chris!
as usual, this Christmas present is greatly appreciated.

I have 2 suggestions for corrections:

(a)
the links on page https://www.ldraw.org/parts/latest-parts.html
point to http files (for example http://www.ldraw.org/library/updates/lcad2003.zip ) instead of https
( https://www.ldraw.org/library/updates/lcad2003.zip )
This makes some modern browsers reject those links (they do not allow a http/https mix), for example the most recent Chrome on Windows 87.0.4280.88.
I suggest that all those download links are changed to https please.

(b)
I found some files inside complete.zip which have inconsistent line endings.
They usually (and correctly) are CR+LF, but there is a handful of them which inmidst of the file have a simple "LF" instead of "CR+LF".
It looks like this error was introduced by some script, because the error usually is present at the first comment line.
The problematic files are:

Code:

parts\104.dat
parts\2400.dat
parts\2619.dat
parts\30209.dat
parts\30536.dat
parts\3068bp61.dat
parts\32200.dat
parts\32201.dat
parts\32202.dat
parts\32235.dat
parts\3596cw1.dat
parts\3837.dat
parts\3847.dat
parts\44511.dat
parts\4592.dat
parts\4858.dat
parts\4858p1k.dat
parts\5306.dat
parts\6028.dat
parts\6055.dat
parts\6092.dat
parts\6265.dat
parts\680.dat
parts\681.dat
parts\682.dat
parts\776p12.dat
parts\777p12.dat
parts\883.dat
parts\973p3c.dat

parts\s\2335ps4a.dat
parts\s\2335ps4b.dat
parts\s\2473s01.dat
parts\s\2586ph2b.dat
parts\s\2867s05.dat
parts\s\3008p03b.dat
parts\s\3044bs01.dat
parts\s\3068p11a.dat
parts\s\32109-1.dat
parts\s\3622s01.dat
parts\s\3754s01.dat
parts\s\3939p91a.dat
parts\s\4864s01.dat
parts\s\6582a.dat
parts\s\71472s01.dat
parts\s\973p04a.dat
parts\s\973p05a.dat
parts\s\973pt2a.dat
parts\s\973sdfa.dat
parts\s\letaa.dat
parts\s\letab.dat
parts\s\letba.dat
parts\s\letbb.dat
parts\s\letca.dat
parts\s\letcb.dat
parts\s\letra.dat
parts\s\letrb.dat
parts\s\letxa.dat
parts\s\letxb.dat
parts\s\s1b.dat

These need normalization to CR+LF.

I have attached the corrected files to this post as .ZIP file

[Orion Pobursky]

Issue (a) is now fixed

[Steffen]

thanks

[Gerald Lasser]

That's really a big release, so many files! What an effort

Will post the summary picture!

[Chris Dee]

Regarding (b), are you saying that this is an issue with the complete.zip after the 2020-03 update and not in the version before that? I can't find any of those files that were changed or introduced in this update. All those I checked were last updated in the 2008-01 update - which was the complete library re-issue for CCAL licensing.

In any case, the current update process checks all new files for DOS-style line endings.

[Ulrich Röder]

But this time it is "really over the peak" ..... great!

Thanks Chris, the authors and the reviewer team!

[Takeshi Takahashi]

Thanks everyone, what a large number of new parts (almost a double of usual release) !!

[Vincent Messenet]

The 2020-03 LDraw Parts Update has been now been released. This adds 1315 new files to the core library, including 829 new parts and 66 new primitives.

Thanks are due to all the part authors who created or corrected parts for this release. The small, but dedicated, band of reviewers also play an important role in keeping files moving through the Parts Tracker and deserve just as much credit. 

You can preview the new parts in 2020-03 here, and download the zip-file update or Windows install package here. Alternatively you can use the LDView menu option File | Check for Library Updates... to install the update.

Congratulations to all parts authors, reviewers and admin for this collective achievement!

[Chris Dee]

Thanks everyone, what a large number of new parts (almost a double of usual release) !!

Yes, I had hoped to issue an update in early November, but other things intervened.

[Gerald Lasser]

Summary Picture

....difficult to select with this huge choice!
   

[Johann Eisner]

I agree with the previous speakers .... Thanks to everyone involved.

????????

[Philippe Hurbain]

Summary Picture

....difficult to select with this huge choice!

Great image (but file name looks weird?)

[Jaco van der Molen]

The 2020-03 LDraw Parts Update has been now been released. This adds 1315 new files to the core library, including 829 new parts and 66 new primitives.

Thanks are due to all the part authors who created or corrected parts for this release. The small, but dedicated, band of reviewers also play an important role in keeping files moving through the Parts Tracker and deserve just as much credit. 

You can preview the new parts in 2020-03 here, and download the zip-file update or Windows install package here. Alternatively you can use the LDView menu option File | Check for Library Updates... to install the update.

Thanks! Have a nice new year's eve everybody!

[Gerald Lasser]

Great image (but file name looks weird?)

I skipped the centuries

[Chris Dee]

Summary Picture

....difficult to select with this huge choice!

Thanks - now added to website.

[Steffen]

The error is present in the current latest complete.zip
https://www.ldraw.org/library/updates/complete.zip

To heal the error, the files inside the ZIP file above should be fasttracked through the PT I think.

[Steffen]

example: check file 104.dat :

   

[Chris Dee]

Steffenexample: check file 104.dat :



I can see, and don't doubt, your observations. I asked you to confirm whether or not this is an artifact of the 2020-03 update. I doubt that it is, and suspect these files have had incorrect line endings since 2008-01.

I can fix all the files on the server rand re-build the complete.zip (without any need for pushing these through the Parts Tracker). But first I want to eliminate the possibuility that something strange happened with the 2020-03 build.

[Lasse Deleuran]

I will join the choir and say amazing work to everyone involved. I have tried to contribute this time, so I have a good idea of just how massive this piece of work is!

I have two questions regarding the content of some of the primitives:

1) How come "7-16ring1.dat" has been added with the same content as "7-16rin1.dat" instead of making one of these an alias to the other?

2) What is the point of the seemingly all new fast draw primitives in the /p/ directory which are aliases of quick-draw primitives in the /p/8/ directory? See "stu2-logo.dat" for an example of this.

[Travis Cobbs]

Steffenexample: check file 104.dat :



I can see, and don't doubt, your observations. I asked you to confirm whether or not this is an artifact of the 2020-03 update. I doubt that it is, and suspect these files have had incorrect line endings since 2008-01.

I can fix all the files on the server rand re-build the complete.zip (without any need for pushing these through the Parts Tracker). But first I want to eliminate the possibuility that something strange happened with the 2020-03 build.

I can confirm that 104.dat is missing the CR on the last line at least as far back as the 2013-01 complete.zip. (I don't have earlier copies of complete.zip.)

[Magnus Forsberg]

I can fix all the files on the server rand re-build the complete.zip (without any need for pushing these through the Parts Tracker). But first I want to eliminate the possibuility that something strange happened with the 2020-03 build.

How many of these files are already corrected and present as updated files in the unofficial library?
If I check 2400.dat in the complete.zip it has a bad file ending, but the corrected/updated version is OK.

[Willy Tschager]

The following files need renaming:

94725.dat - Figure Friends Accessories Bow with Heart

to

Figure Friends Hair Decoration, Bow with Heart with Pin

[Magnus Forsberg]

I have two questions regarding the content of some of the primitives:

1)
Thats a mistake. We have abandoned the 8.3 filenames.
New ring primitives should use the whole word "ring" in their name. But we chose to not rename old ri-, rin-primitives.
Anyone uploading new ring primitives need to check if there already is an old file using ri or rin.

2)
To fool hardcoded requirements in MLCad.
Any primitive beginning with the word "stud", like studXXX.dat needs to have a corresponding stu2XXX.dat in the same p-folder.
But since we have the lo-res library now, p/8, we now need to make any stu2XXX.dat file a Move to - p/8 folder.

[Chris Dee]

The following files need renaming:

94725.dat - Figure Friends Accessories Bow with Heart

to

Figure Friends Hair Decoration, Bow with Heart with Pin

Updated and fast-tracked. This could have been avoided if you had mentioned it when you Certify voted :-)

[Lasse Deleuran]

1)
Thats a mistake. We have abandoned the 8.3 filenames.
New ring primitives should use the whole word "ring" in their name. But we chose to not rename old ri-, rin-primitives.
Anyone uploading new ring primitives need to check if there already is an old file using ri or rin.

2)
To fool hardcoded requirements in MLCad.
Any primitive beginning with the word "stud", like studXXX.dat needs to have a corresponding stu2XXX.dat in the same p-folder.
But since we have the lo-res library now, p/8, we now need to make any stu2XXX.dat file a Move to - p/8 folder.

Thanks. That MLCad requirement is pretty wild. But I'm glad that you are still accounting for there!

[Willy Tschager]

Updated and fast-tracked. This could have been avoided if you had mentioned it when you Certify voted :-)

I already blamed myself the whole day for not doing it - it wasn't necessary that you even turned the knife :-)

[Chris Dee]

I already blamed myself the whole day for not doing it - it wasn't necessary that you even turned the knife :-)

Sorry!

[Willy Tschager]

There are now two parts with different name but (almost) identical description:

3626cpm9.dat - Minifig Head with LOTR Thick Grey Eyebrows and Smile Pattern
3626cpm1.dat - Minifig Head with LOTR Thick Gray Eyebrows and Smile Pattern


Well, there is a general "Gray" - "Grey" inconsistency:

https://www.ldraw.org/cgi-bin/ptscan.cgi...ope=header
https://www.ldraw.org/cgi-bin/ptscan.cgi...ope=header

w.

[Orion Pobursky]

There are now two parts with different name but (almost) identical description:

3626cpm9.dat - Minifig Head with LOTR Thick Grey Eyebrows and Smile Pattern
3626cpm1.dat - Minifig Head with LOTR Thick Gray Eyebrows and Smile Pattern


Well, there is a general "Gray" - "Grey" inconsistency:

https://www.ldraw.org/cgi-bin/ptscan.cgi...ope=header
https://www.ldraw.org/cgi-bin/ptscan.cgi...ope=header

w.

According to the interwebs, grey is the commonly used spelling in Aus English.

[Magnus Forsberg]

According to the interwebs, grey is the commonly used spelling in Aus English.

Grey is the only spelling we should use. I was surprised by the long list of official parts using Gray.
Is there a reason why these might have not been corrected?

[Orion Pobursky]

Grey is the only spelling we should use. I was surprised by the long list of official parts using Gray.
Is there a reason why these might have not been corrected?

For self-consistency reasons I agree. The reason they probably haven't been flagged is that both spellings are correct. Grey is more common in UK/Commonwealth and Gray is more common in the US but they can used interchangeably.

[Magnus Forsberg]

For self-consistency reasons I agree. The reason they probably haven't been flagged is that both spellings are correct. Grey is more common in UK/Commonwealth and Gray is more common in the US but they can used interchangeably.

I know there are 2 different spellings, but we have decided to use only one. I'm asking, did we decide not to correct these?

[Orion Pobursky]

I know there are 2 different spellings, but we have decided to use only one. I'm asking, did we decide not to correct these?

No. They were probably overlooked for the reasons I stated above.

[Chris Dee]

No. They were probably overlooked for the reasons I stated above.

We should use only 'Grey' - the Australian English spelling . These were overlooked by all reviewers, including me. I should add a check to the update build process and recycle those using 'Gray'.

[Willy Tschager]

3817bpc1.dat - Minifig Leg Right with Red Tied Sash Pattern

has to be renamed to:

3817bpc1.dat - Minifig Leg Left with Red Tied Sash Pattern

as 3817 is the left leg.
---------------------------------------------------------------------------
973pd99.dat - Minifig Torso Robe with Black Gathers and White Neck Pattern

should be renamed to:

973pd99.dat - Minifig Torso with Robe with Black Gathers and White Neck Pattern

to be in sync with the nomenclature for torsi.

w.

[Chris Dee]

3817bpc1.dat - Minifig Leg Right with Red Tied Sash Pattern

has to be renamed to:

3817bpc1.dat - Minifig Leg Left with Red Tied Sash Pattern

as 3817 is the left leg.
---------------------------------------------------------------------------
973pd99.dat - Minifig Torso Robe with Black Gathers and White Neck Pattern

should be renamed to:

973pd99.dat - Minifig Torso with Robe with Black Gathers and White Neck Pattern

to be in sync with the nomenclature for torsi.

w.

Updated and fast-tracked.

[Chris Dee]

We should use only 'Grey' - the Australian English spelling . These were overlooked by all reviewers, including me. I should add a check to the update build process and recycle those using 'Gray'.

All updated and fast-tracked. I also fixed the few occurrences of LtGrey and DkGrey.

[Willy Tschager]

All updated and fast-tracked. I also fixed the few occurrences of LtGrey and DkGrey.

w.

[Travis Cobbs]

While generating the PDF part catalog for this release, I discovered that part 35860.dat has a !CATEGORY of Minifir Accessory. I'm editing my local copy and regenerating the catalog to avoid having that category in the catalog.

[Jaco van der Molen]

While generating the PDF part catalog for this release, I discovered that part 35860.dat has a !CATEGORY of Minifir Accessory. I'm editing my local copy and regenerating the catalog to avoid having that category in the catalog.

Travis, do you post that PDF part catalog somewhere?

[Chris Dee]

While generating the PDF part catalog for this release, I discovered that part 35860.dat has a !CATEGORY of Minifir Accessory. I'm editing my local copy and regenerating the catalog to avoid having that category in the catalog.

Fixed and fast-tracked for inclusion in the next update.

[Willy Tschager]

Travis, do you post that PDF part catalog somewhere?

The catalog gets updated on my request and is part of the AIOI.

w.

[Travis Cobbs]

The catalog gets updated on my request and is part of the AIOI.

Right now, I only generate this for Willy to put into the AIOI. I use a custom bash shell script that I created myself that runs on my Mac. The script generates HTML, which I then import into a master document in LibreOffice, and then export from there to PDF.

Safari, Chrome, and Firefox all have serious issues with table pagination that prevents me from simply printing to PDF from a web browser. (I just verified that again today.)

As an aside, the 2020-03 PDF is 79 MB. My script actually has support for high-DPI (200%) scaling of all the images, but I don't use that. I'm not entirely sure that scaling still works, but the generated PDF would likely be about four times bigger with that enabled.

[Jaco van der Molen]

The catalog gets updated on my request and is part of the AIOI.

w.

Ah yes. Since I do not use the AIOI, could it be hosted somewhere to download?

[sunil808]

If I check 2400.dat in the complete.zip it has a bad file ending, but the corrected/updated version is OK.