I'm working on the new TIE Interceptor and 35154ps1 renders odd. The PT webGL renderer and LDView are unaffected.

   

After the release this Monday (5/27) I'm going pause new feature addition to the PT to embark on some housekeeping. Specifically:
- Update the server to the latest version of our Linux distro
- With that, write scripts to automate this process.
- Do a complete code review and streamline/refactor files

Additionally:
- Update and reformat the Official Library Spec and Number Spec.

This will probably take the better part of a month and may involve some extended outages. 

Bug fixes will continue to be addressed as they occur.

Hello,

I have seen two complete minifig upper parts on the Parts Tracker.
They are the parts 76382pdg1 and 76382pdg7.
I would add c01 to the numbering, as it is possible that there may be the same part with hands in a different color at some point. The character sequence dg1, dg7 stands for the printing and c01 stands for the design.
As an example, see also on Bricklink the parts 973px61c01 and 973px61c02. These parts are identical except for the color of the arms.

Greetings

Manfred

u9284.dat already exists
https://library.ldraw.org/official/15951

would it be possible to create the two other common sizes?
-AAA (thin)
-C (big)
https://en.wikipedia.org/wiki/List_of_battery_sizes
do we also need the 9V-Block?

unfortunately most battery boxes miss the interior (but that is another thing)

Stud.io's native *.io file already contains thumbnail picture of the model in editor, yet it does not show/use it as a thumbnail in Windows Explorer, but instead it uses Studio default icon for all the model files.
This results in that when we have many mocs in a folder, we can only distinguish them by name.
So，can someone develop a plugin to achieve this functionality?

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