These are some parts from Bionicle / Hero Factory, The first 3 are in the LDD and could be converted.

98597 Large Figure Foot, with 2 Toes
20480 Large Figure Weapon Sword, Skull Warrior
15367 Large Figure Foot, with Ball Socket 5 x 6 x 2

15358pat000 Large Figure Creature Cocoon Petal with Black Base Pattern

Interestingly enough, some of these parts are the kind that appear in Rebrickable as having an LDraw part, but are nowhere to be found. If they exist and are named something else, please let me know.

I'd like to make a formed sticker of 4620859d
https://www.ldraw.org/cgi-bin/ptdetail.c...20859d.dat
to put on a bucket 48245.
https://www.bricklink.com/v2/catalog/cat...7#T=C&C=47

As the side surface of bucket is not cylindrical,
the Pattern Folder web-app by Lasse cannot be used.
Are there any smart ways for creating this sticker,
or should I cut the pattern manually with tweaking the coordinates in LDPE?

Thanks,
Takeshi

[Edit] 2021-06-20
Thanks again for a lot of advice.
The part has been admin-certified and will be included in next release.

Hi there,

Just wanted to confirm if one can expect parts to be deleted from unofficial library from time to time. 

This definitely happened recently with the part 5306c01 that used to be in the library but is now gone. It wasn't moved to the official list, so I assume it was simply deleted.

I know that such kind of thing cannot happen with files in the official library, because they stay there forever for backwards compatibility. But looks like things work differently in the unofficial library, which makes it even less reliable.

Hello community,
Is it possible to export the render-pictures for all parts included in LDraw as single files? WITHOUT LEGO logo on the studs?

Is there a data set like this somewhere already available for download?  Rebrickable offers pictures from all parts, but only with the LEGO logo in the studs.


Help appreciated

Good evening all. I just joined LDraw.org this evening. I'm here to make a request for #37697, Hair Mid-Length and Wavy with Bangs.
I don't know if the part was already requested, even after searching the forums and not seeing anything come up for it.

Some months ago Matthew Fleming on Twitter posted instructions for a funny Donald Trump MOC (branded as the "President" model from the "Ego" company). I couldn't find the LDraw file for it, so I made it myself. I hope you like it.

Attached Files

  Trump.ldr (Size: 4.96 KB / Downloads: 6)

Hey all,

I'm looking to have these 2 parts made and added to the library.

47577 Minifig Hockey Body Armor Plain

https://www.bricklink.com/v2/catalog/cat...77#T=C&C=1

And

[color=#000000][font=Tahoma, Arial]92814 Minifigure, Headgear Cap, Graduation Mortarboard with Tassel[/font][/color]

https://www.bricklink.com/v2/catalog/cat...4#T=C&C=11

Hoping someone do this for me?
Thanks in advance.

Regards

Derek Pearce (The Brickspace)

Attached Files

  47577.png (Size: 74.89 KB / Downloads: 55)
  92814.png (Size: 65.06 KB / Downloads: 54)

Hello,

I noticed that some parts consist of one or more individual parts, e.g. "Hinge Control Stick and Base (Complete)", Design 4592c01. This part is also available in other versions where the stick has a different color. Or the upper and lower parts of mini figures, some of which are already in the library. My question now is, does it make sense or is it desirable or not to include these parts in the library?

Greeting

Manfred

Since we had only 5 confirmed nominees, no election was necessary. 

Therefore, the 2021/2022 LDraw.org Steering Committee [1] is:

Gerald Lasser
Philippe Hurbain
Max Martin Richter
Orion Pobursky
Willy Tschager

[1] Try not to confuse the LDraw.org Steering Committee (SteerCo) with the LDraw.org Standards Board (LSB). The Steering Committee sets the course for the LDraw Organization while the Standards Board deals with the LDraw File Format.

Congratulations to the reconfirmed and new members!

Willy Tschager
On behalf of the LDraw.org Steering Committee

Hi,
Creating part using subparts is a great fundamental thing in the LDraw library. However, I found that there might be a little room for improvement with respect to subpart naming.

The `snn` suffix custom incremental naming is a good starting point, but when I looked at parts and their patterned versions, I found there is quite some ambiguity. This makes reusing existing subparts sometimes difficult and even impossible (e.g. when a subpart includes a part of the patterned area).

My suggestion would be to include a best practice where subparts have naming according to their place and/or orientation of the shapes.

Note: for the basic bricks and tiles this might not be needed, since these are mostly built up with primitives anyway.

But take, for example, the door part 92262. It generally has two sides where stickers or patterning could be applied (the front and the back). So these subparts of the model should be separated to provide an easy way to make patterned versions of this part. However, in this case, a small part of the patterned area is included in the top surface of the door. There are multiple ways to correct this or create new subparts, so that's not the issue. The issue is creators of parts might forget about possible future patterning when they divide their part into subparts. This is a great chance for improvement.

Entering my suggestion for naming subparts of possibly patterned parts:

File name suffix - Description
`s01` - Subparts containing a main collection (e.g. mirrorable part)
`sfnn` - Subparts containing the front facing part of a model
`sbnn` - Subparts containing back facing parts
..etc (`u` for upward facing, `d` for downward facing, `l` and `r` for left and right facing)

Alternatively, 'though less meaningful, the practice could be to use`sNn`, where:
N =
1 for main subparts
2 for top facing
3 for bottom facing
4 for front facing
5 for back facing
6 for left facing
7 for right facing
8 for misc (e.g. handles or other unprintable details)

In this practice it is not needed to subpart all these orientations, only the significant ones for that part.

In the case of the door part above, only top, bottom, front and back subparts would be needed. Since top and bottom are always the same within a part variation and only the front and back might have patterned versions to swap in.

To be clear, this would be a best practice and not a restriction. But including it in documentation might encourage more modular subparting with patterns in mind.

What do you think?