I did a quick recap of all the Opal colours so far (a total of 8) and noticed a few issues with older existing Opals, but also a few other colours:

1. Our Opal_Trans_Green (ID 367) is using the wrong Base Colour; Trans_Green instead of Trans_Bright_Green. This is likely caused by the official name being just "Transparent Green with Opalescence" for some reason. Opal Trans-(Dark-)Green parts do exist, but those are purely unofficial at the moment. I intend to change the current one to match Trans_Bright_Green.
   
2. Should 363 Opal_Trans_Black be renamed to Opal_Trans_Brown? This Opal colour is based on the old 1999-2022 Trans-Brown and it's not entirely unlikely we will eventually see parts in "real" Opal-Trans-Black.
   
3. None of the 3 variants of Trans-Purple (52 Regular, 129 Glitter, 365 Opal) currently match. Those are all based on the same plastic colour, just with a different amount of the glitter additive, so should be very close for the real parts. Is this something that should stay this way?
   
4. For Trans_Clear (47) and Glitter_Trans_Clear (117) the same Mis-Match applies as with Trans_Purple.
   
5. Colour 294 Glow_In_Dark_Trans currently uses the same Alpha value as the other 2 Glow-in-the-Dark colours 21 and 329, despite being noticably more translucent on real parts. Should it's Alpha be lowered?
   
6. The colour 342 Conductive Black (only ever used for part 15411, the App-Bricks in Ultra Agents) would probably look more realistic if it got changed to a type of Glitter colour, likely with dark grey particles instead of silvery ones used for real Glitter colours.
   
7. Colour 77 Light_Pink seems to use a wrong Hex (#FECCCF). The Lego Colour this is based upon (223 Light Pink) uses #F17880 officially and looks much darker/saturated than the current one. This is an odd colour anyways, since it's one of the few in LDraw that never was released officially. It was supposed to replace 101 Medium Red (12 Salmon) in 2004, but got eventually cut.
   

I've started converting over the new 7905 leaf part into something that can go on the tracker.

Is there a better ring segment I can use for the back half of rounded portion of the leaf so it looks better in high res? I don't really get which one to use other than the half rings and you aren't supposed to rotate other ones other than by 90 degrees.

Attached Files

  7905.dat (Size: 24.04 KB / Downloads: 4)

As many of you probably noticed, we got 2 new colours in 2026 sets: Warm Pink and Blue Violet.

Both are now addedto LDConfig as:
430 Warm_Pink (Warm Pink)
431 Bright_Blue_Violet (Blue Violet)

The official name for Blue Violet was unfortunately already taken for a quite a while now, so I had to come up with a different name. Our "Blue_Violet" is Lego's "195 Royal Blue" - a retired, yet still not that rare of a colour (used primarily in Knights' Kingdom II around 2004-2006).

For the moment I opted not to rename the older colour to avoid confusion, but it still feels not optimal all things considered

I also noticed Bricklink recently changed their name for the old "Blue Violet" to "Royal Blue (Old Blue-Violet)". Maybe it's better to do something similar?

Any opinions on this?

This thread is just for Information and a monthly collection of new parts released.

And can serve as a source to author the part for the tracker!

Those parts are NOT corrected for orientation and origin

Do NOT answer to this thread.

-----------------------------

Hello,

Among the primitives, there is the primitive n-fchrd.dat. This primitive is well suited for creating a transition to, for example, an enclosing circle. Unfortunately, the starting point of the circle segment is always at 0°. Sometimes it would be useful if this starting point were at 22.5°, for example. The circle segment would then go from 22.5° to 67.5°. In the high-resolution version, it would be 7.5° or a multiple thereof.

Rotation that is not equal to a step size of 90° results in rounding errors that can lead to visual errors.

Furthermore, a similar primitive would be useful, forming a circle segment from, for example, 22.5° to -22.5°. The center point of the circle segment would then be at 0°.

My question is whether it would be possible to introduce such primitives.

Best regards,

Manfred

Hello,

I would like to create a new primitive (4-4ring179.dat).
To do this, I looked at the primitive 4-4ring18.dat. I noticed that the values of the individual points are, in my opinion, incorrect.
A quarter circle consists of four circle segments. The angle of each piece of the quarter circle is 22.5°.
The first line in the primitive file looks like this:

4 16 19 0 0 17.5541 0 7.2713 16.6302 0 6.8886 18 0 0

19 0 0 is the point at the bottom right of the first circular arc segment. For the second point counterclockwise, the following applies:

x = cos(22.5°) * 19 ~ 0.923879 * 19 ~ 17.55371111 -> 17.5537
y = sin(22.5°) * 19 ~ 0.382683 * 19 ~ 7.27098521 -> 7.2709

These values differ from the values in the file.
The deviation is very small, but it is there.


My question is: is the value in the file correct and I have made a mistake in my thinking? If so, what is it? 

Best regards,

Manfred

Hello, I have to deal with this part on Rebrickable, and I have a problem.

On BL and here, the part is called : [...]with Dark Tan Crescent Pattern, whereas its called [...]with Reddish Brown Crescent Print.

At first I thaught there was 2 different parts, one tan and one brown and that I encountered a mapping issue. But this part seems to have been used in one set only. and the picture on BL show a reddish brow cressent and not a dark tan one, like the LEGO element render.

https://rebrickable.com/parts/2654pr0003...ent-print/
https://www.bricklink.com/v2/catalog/cat...=2654pb015
https://library.ldraw.org/parts/24301

Is it because dark tan printed on black looks like reddish brown ? Or Is there an error somewhere ?

Hello

The part in question is variant of 98138 (Tile, Round 1 x 1) with TIE Fighter cockpit print. IIRC Trans-Clear.

I'd greatly appreciate if it could be added <3

https://www.bricklink.com/v2/catalog/cat...98138pb257

Hello!

Part 4592 currently features mismatch between dome and cylinder parts. 
   
As seen in attachment, this leads to holes in geometry. I'd greatly appreciate if it could be fixed. <3

Get this Release.

New in this release:
With this release it is possible to get colour values with a function call. This can be useful when using the OpenScad Customiser.

Important Notice:
Both the installation method and usage of this library has changed. Please read the updated installation and usage sections in the README.