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.

Hello, i just built the panama canal (digitally), now the onlx thing that is missing is the sticker:
https://www.bricklink.com/v2/catalog/cat...=0#T=C&C=0
data from the set:
-flat sticker on a white 2x4 tile
-rounded corners
-about 1.8x3.8
-the cut seems to be inside the blue rim
can someone do that from that one picture (didnt find other ones), or does anyone have the set/part/sticker sheet?

Thanks in advance, René

The following change is effective immediately:

Shortcuts of parts that are produced and packaged as one assembly are allowed in the library. In addition, all sticker shortcut for a given sticker sheet and set are allowed.

For assemblies, the position/rotation of the parts in the shortcut file must exactly match the uncoloured assembly shortcut. If there is no uncoloured assembly, one must be authored and certified before any additional shortcuts of that type are certified. The file name for the additional assemblies must be <base file name>pCC©/XXXX (per the pattern file spec). All other rules for patterned parts apply.

For sticker shortcuts, the flat sticker rule is rescinded. All other rules apply.

For both types: until a new approval process is established, these parts are eligible for Fast Track by Fast Track authorized users.

The specs will be updated shortly with these rule changes.

I hope this is an appropriate place for my question.

I'm using the Import LDraw Blender plugin to render a model I built in StudIo. The problem is that part No. 80015 seems to have distorted geometry. I found found the .dat file in the unofficial parts library, however after adding to my locals files this is the result.

Please advise, I hope I'm just missing something obvious.

   

I am finding the behaviour for part usage countdown a bit strange.

If I build an official model where I have several submodels and I isolate one of the models it suddenly forgets that the parts are used in one of the other submodels.

In my opinion the countdown should be on global level in the file. Not per submodel.

Just ask if it didn't make sense