The 2013-02 LDraw Parts Update has been now been released. This update includes 869 new files in the core library, including 570 new parts and 61 new primitives.
The optional installation library of Alias parts has been dispensed with - all aliases are now in the main library, but identified with a "=" prefix to their description, and all previously released alias parts have had their descriptions updated in this release.
Of note is the inclusion of a new /p/8 sub-folder to hold low-res versions of stud (and potentially other) primitives. This should be the preferred location for tools to find low-res primitives, but to satisfy the needs of MLCad, we will continue to maintain stu2* versions of the stud* primitives in the /p folder. Thanks to everyone who contributed to the discussion on how best to implement this.
A major component of the update is most of the Mindstorms EV3 parts, for which massive thanks are due to Philippe Hurbain (Philo) for their creation and to our enthusiastic reviewers for checking them so soon after this product release. Thanks are also due to the other part authors who created or corrected parts for this release and to the reviewers who have also played an important role in making this release happen.
You can preview the new parts in 2013-02 and download the update by going to the Latest Parts page.
Once again, no new "Physical colour" parts are included in this update as we develop plans to move these to a separate section of the LDraw file structure, to more closely fit with the "DesignID" vs. "ItemID" concept.
I noticed the offical file 3079bps9 is using "blue" for the instruments. The part was used in blue and yellow. The yellow parts don't have blue elements. I changed all references in the instruments to match color code 16.
For me the part now looks like the real world part. Please consider changing the offical file according to the my attachment.
I'm experimenting with a mobile-friendly template. Right now it'll look quite different from the default color scheme but this will change as I play around some more.
More than a year ago I jumped into a MOC project (my second one, please be lenient) which was initiated by a planned village festival with the motto Bear, including a small Lego exhibition. Spontaneously I decided to go for a MOC based on a memento from a earlier U.S. trip, a Ironwood carving "Mother and Baby Bear".
Some of you helped to tackle the project and bring it forward
(1) Laser scan (STL mesh) done by a third party
(2) LSculpt from Bram Lambrecht (converts a triangle mesh into a skin of 1x1 plates)
(3) Splitting up Mother/Baby, remodeling the cutting region and artefacts with MLCad
(4) Coloring all visible bricks with MLCad, throwing away all needless inner parts
(generated by LSculpt, reducing the total number of bricks to one third !)
(5) Organizing skin plates to "layers" with MLCad
(6) With MLCad for each layer: Replacing skin markers by bricks/plates
(in addition constructing a inner structure to stabilize the model)
(7) Visualizing building results stepwise with LDView (MLCad didn't the job well)
Producing partlists and snapshots with LDView
(8) Generating building instructions with LPub
(not too perfect, working doc to build the Bear Group in reality)
(9) Building the Bear Group in reality by my wife Laura
The virtual cobbling together of 25,825 Lego bricks not succeed without errors,
so I had to do some corrections following Laura's advises :-)
This is not directly a part request- more a request for a clarification of this issue:
I find 3741 Plant Flower Stem as 3741A.DAT, but no 3741B.DAT or so in the library. There is also no other version existing in real life. And there is 3741.DAT which seems to be obsolete (it also in the part name). But why is this obsolete part still existing?
And in all models where I used 3741.DAT this remains this version. But I think when there is only one real life version this should be used.
Short: Shouldn't the obsolete shape replaced with the actual one?. This would mean deleting 3741.DAT and renaming 3741A.DAT to 3741.DAT.
Why has this not happend? Is there a good reason?
When modeling official sets, should then always the 3741A.DAT be used?