I'd like to add 2 new type qualifiers to the !LDRAW_ORG meta:

Pattern and Assembly

- Since the pCC©/pNNNN suffix is used for both dual mold and printed parts, Pattern will be used to denote a printed part. There might also be a use for a dual mold qualifier.
- Assembly with be used to denote a shortcut that LEGO normally produces and distributes as one unit. Think torso with hands and arms, the 1x1 lever, or electric motors. This will not apply to further shortcuts that combine more parts, like the electric motor and cable shortcuts.

Hi,

While working on a model with submodels I like to add a keyword to some submodels.
Would it be possible in LDCad to search for this keyword in the part bin "All models"?
This does not seem to work.

In the Part bin display filter I checked to look in Keywords and choose OR at the Match kind 

Tnx.

Jaco

Kind of a random and trivial inquiry, but one I keep going back and forth on…

In model files, do you prefer that an MPD filename (the 0 FILE meta) always match the—well, the file name, i.e. the 0 Name meta?

LDCad, for example, offers the option to sync these two metas by default, and it's also required by the OMR spec. But apart from that, are there reasons why these two entries should or should not always match?

Couple of points I can think of:

• The 0 FILE meta accepts a filename as a parameter. If this filename is always the same as the 0 NAME meta, why would it need to appear again as a parameter for 0 FILE?
  
• I've always understood 0 NAME to be the filename as it's saved in my system. At least, that's how it is for parts, including whether it's saved in the s/ or 48/ directories.  But for the main subfile of an MPD, it's expected that the filename be "main.ldr", which is not how the parent file is saved. (I know they're different, but the parent file is really nothing but an empty wrapper, and it doesn't have its own header other than that of the main subfile.)
  

Hi,

I would love the file for "Rabbits" head from Winnie the Pooh

https://www.bricklink.com/v2/catalog/cat...conly%22:0}

Thank you

There is a certain shade of grey used in many of the models in the Star Wars cinematic universe (i.e. the movies). I'm talking about Han Solo's Millennium Falcon, the various Imperial fighter craft and capital ships, and the Death Star trenches. 

In my opinion, the LDraw color 71 is just a bit too dark for this specific shade of grey. However, when I try using color 151 for this shade of grey, the result looks too close to white, especially for the TIE fighters (since the grey is contrasted with black). 

Per the official color specifications for LDraw, color 71 is #969696, and color 151 is #C8C8C8. Therefore, the custom shade of grey I think I should be using would be #AFAFAF. (Since both of the afore-mentioned "official" shades of grey use the same Edge Color, I do not need to create a new such shade.) 

Now that I have the RGB hexadecimal value to use for the desired shade of grey, how do I use this info in my LDraw models, please? 

Thanks! 
Franklin

Hi Roland,

I have started tinkering with some shadow files for some parts I needed it for and have some questions. 

First of all is it ok that I just add PRs to the github repo?

And second. For this example. Does it matter what orientation the lines are in for the window/door?

Attached Files

Thumbnail(s)
   

If you would like an invite to the LDraw.org Discord, please PM Orion.

Dear LSB,

please read:

https://forums.ldraw.org/thread-28231.html

and have your say.

w.

Hi folks,

I just updated the MLCad.ini file accordingly to the latest LDraw.org parts update 2024-03. The .ini file defines (among other things) the parts available in MLCad's, LEOCad's and Bricksmith's minifigure generator.

Download the file from my website: http://www.holly-wood.it/mlcad/mlcad_ini-en.html

Bye, w.

With the assembly/stick shortcut policy change I'd like to proposed 2 new categories:
Sticker Shortcut
Minifig Top(?) 

I need help with the torso assembly category. I think it should start with Minifig. It should not be more than 2 words. I think Minifig Assembly might be too generic.

Once finalized, I'll add the new category to the applicable parts via automatic action.