…needs to exist in an uncoloured version, e.g. for set 21033. Easy enough to make, but what's the right procedure/numbering/naming for it? (And is it still a shortcut, or is now just a part since there's no hard-colored portion?)


  93094a.dat (Size: 681 bytes / Downloads: 3)

Hi all, I just joined and just started using LDraw, so sorry in advance if I'm being stupid !

I'd like to revive my old Legos sets for my son, but there are heaps of missing parts... However I have a 3D printer and I'd like to print them.

I did a bunch of tests and it's quite promising with LDraw library. However I stumbled upon one issue : the basic thin parts from LDraw lib are not as deep as real legos !

Taking for instance part 3023, 1 x 2 plate, when measuring the internal depth from the bottom to the internel ceiling, I get more than 2mm on an actual part, and 1.6mm from LDraw lib.

Is that normal, like for rendering purpose or something ?

Thank you for your help.

Is this a variation we care about?

https://rebrickable.com/parts/95120/hing...ng-ridges/

Hello,
I wanted to draw a train track in LDCad, but I could not find part 53404 / 53406 in Ldraw. Here on the forum I read a thread from years ago with the clue to look at http://www.brickshelf.com/cgi-bin/gallery.cgi?f=203196 . There I found my part and implemented it succesfully (I guess). My question is why is this part never included in Ldraw official or unofficial parts?
Thank you.

hi guys, I'm new in this forum but I use draw by 1 month...  initially build the models with lego digital designe and then I import them in blender thanks to ldraw ... I have only recently noticed that the parts: 18973, 27507 and many others are not displayed in blender ... practically the dat extension files present in the library there are not in the window at the top right: Collection / scene collection .. only the file name extension ldr appears to me.
Have any of you encountered the same problem?
thanks
 David

Hello,

I have a parts request for this part, as I cannot seem to find it at all in the Ldraw library.



The complete assembly consists of these two parts:
https://www.bricklink.com/v2/catalog/cat...ane%5D#T=C
https://www.bricklink.com/v2/catalog/cat...ane%5D#T=C

It is used in just a few sets, for example 4555 Cargo Station (1995).

Hello,

Is there any plans on finishing this part?
https://www.bricklink.com/catalogItemIn....70962&in=S

I see there's a couple parts and subparts in the unofficial parts tracker that mentions 70962. The last comment from Dec -19 in this entry https://www.ldraw.org/cgi-bin/ptdetail.c...s/u656.dat notes that 70961 exists but 70962 is missing.

Does anybody know if 70962 will be created?

Hello All,

I am planning on using the LDraw parts for a virtual reality building system, but I am unsure if this is a good idea because of the potential copywrite infringement on the LEGO Group. 

I want to decide early in the development process if I should use LDraw or model my own knockoff parts and possibly use the same part names for instruction manual/LDraw .ldr file export purposes. 

The library wouldn't be all-encompassing in either case, and I would make sure not to use any trademark material, but as far as I am aware the LEGO Group has failed in multiple lawsuits to secure intellectual ownership of most of their part designs (excluding some parts such as minifigs, Bionicle, etc.) after their patents expired. 

I know that LDraw is available for commercial use, but am I looking at a lawsuit if I use the parts in this way?

I have already developed a prototype if anyone is interested, currently developing for the Oculus Quest VR Headset using the Unity Engine.

Prototype:

I love Rebrickable's PBG export. However, it has the drawback that minifig torsos and legs are listed as assemblies so unless they're generic enough to use the appropriate shortcut they'll always appear as unfound parts in the parts bin. I recently had a forum thread with the dev team about this and was basically told that this will never change since it's too much for them to track arms, hands, torsos, hips, and legs separately. I don't disagree with this decision from their point of view.

I proposed the following solution:
Associate the LDraw part number for the appropriate torso with the assembly. Add in the arms in the same color as the torso and the hands in yellow. This will at least get the correct torso pattern to show up in the parts bin and the if the arm or hand color is different, that's easily changeable by the user. They have yet to get back to me on this suggestion.

Then I got to thinking, we could use the Rebrickable API to provide our own PBG export. Either roll our own cross reference database or, since Bricklink does catalog the torsos, arms, and hands separately and Rebrickable provides the Bricklink number, pull this data from Bricklink via their API. We could also have an option to include the unpatterned version of a part if the patterned version doesn't exist and reference the appropriate flex part template for flexible parts.

Thoughts?

For reference:
https://rebrickable.com/parts/11055/flag...ick-clips/

Is this a variation we care about or should I tell Rebrickable to use 2335?

Note: Bricklink doesn't differentiate.