I have a problem with LPub3D rendering LDView with Enable Highlight Steps.


Parts with tan colour now appear transparent instead of just highlighting the edge colour.
https://photos.app.goo.gl/JfhVyvE7CVQzUPqE7

The root cause seems to be in LDConfig.ldr with this change:

0 !LDRAW_ORG Configuration UPDATE 2025-09-18
0 // Last update: Added 11015 Trans_White and 11019 Trans_Tan


LPub3D uses the prefix 110 to show the highlighted parts with a defined edge colour:

# File: LEGOFadeStepColorParts.lst  Generated on: 11-07-2025 19:53:40

# This space-delimited list captures the LDraw static color parts (and their subfiles) to support
# step fade and step highlight. Parts on this list are identified in the LDraw library and copied to
# their respective custom directory. Copied files are modified as described in the following
# lines. If fade step is enabled, color codes are replaced with a custom code using the standard
# color code prefixed with [100].

# If using a single fade step color, color codes are replaced with main material color
# code 16 using the fade color set in Preferences. If part highlight is enabled, edge
# color values are replaced with the color value set in Preferences. If part highlight is
# enabled, color codes are replaced with a custom code using the standard color code
# prefixed with [110].

# When fade step is enabled, custom generated files are appended with '-fade',
# for example, ...\custom\parts\99499-fade.dat                 

# When highlight step is enabled, custom generated files are appended with '-highlight',
# for example, ...\custom\parts\99499-highlight.dat                 


So LDView now finds the new colour 11019 in LDConfig.ldr to be Trans_Tan, instead of the local definition of LPub3D in the temporary file 42143 - 1.1.1.1-highlight.ldr:

0 !COLOUR LPub3D_Orange CODE 11025 VALUE #D67923 EDGE #C000FF00 ALPHA 255
0 !COLOUR LPub3D_Dark_Azure CODE 110321 VALUE #469BC3 EDGE #C000FF00 ALPHA 255
0 !COLOUR LPub3D_Yellow CODE 11014 VALUE #FAC80A EDGE #C000FF00 ALPHA 255
0 !COLOUR LPub3D_Tan CODE 11019 VALUE #D7BA8C EDGE #C000FF00 ALPHA 255
0 !COLOUR LPub3D_Light_Bluish_Grey CODE 11071 VALUE #969696 EDGE #C000FF00 ALPHA 255
0 !SILHOUETTE 1 #C000FF00
1 11071 0 0 0 -1 0 0 0 -1 0 0 0 1 64179.dat
1 11019 0 0 50 0 0 1 0 1 0 -1 0 0 3749.dat
1 11014 0 0 40 1 0 0 0 1 0 0 0 1 69762.dat
1 11014 0 0 -40 1 0 0 0 -1 0 0 0 -1 69762.dat
1 11019 0 0 -70 0 0 -1 0 1 0 1 0 0 99008.dat
1 110321 0 0 -80 1 0 0 0 -1 0 0 0 -1 69779.dat
1 11014 0 0 0 0 0 -1 0 1 0 1 0 0 42143 - 1.1.1.1.1-highlight.ldr
1 11014 -40 0 0 1 0 0 0 1 0 0 0 1 4519.dat
1 11014 -70 0 0 0 0 1 0 1 0 -1 0 0 59443.dat
1 11014 40 0 0 -1 0 0 0 1 0 0 0 -1 4519.dat
1 11014 70 0 0 0 0 -1 0 1 0 1 0 0 59443.dat
1 11025 40 0 -60 0 0 -1 1 0 0 0 -1 0 65304.dat
1 11025 -40 0 -60 0 0 -1 1 0 0 0 -1 0 65304.dat
0 !SILHOUETTE

How to solve this conflict?
Why has the colour 11019 been included in LDConfig.ldr ?
If I remove it there, the problem is solved.

When a part number is updated, a move to file is created for the old number. Why does the new part use the subfiles from the old part number?

e.g. https://library.ldraw.org/parts/49972

What is the position in regard to matching the colours of the BI textures vs the colours that say Bricklink say the colours are?

For example making part 3069pb1341
https://www.bricklink.com/v2/catalog/cat...#T=C&C=152

A) is the part in studio which uses the texture from BI

B) My go to match those colours

C) The colours if you go by the parts description in the Bricklink store.

So do we just ignore the actual texture colours and go with the store decription?

I'm considering implementing the following automatic upon submit edits:
- Remove all lines that consist of a single "0" and replace with a blank line
- Remove all lines that are "0 //" (i.e. a blank comment) and replace with a blank line
- If the last line is a single "0", remove completely
- Capitalize the first word for all keywords.

Thoughts?

Thread for Friends 2025 sets

Minifigure, Head Beard with Dark Brown Eyebrows, Angular Beard, Smile and White Pupils Pattern
I just cannot find this piece anywhere for the life of me though I've seen a photo of its digital rendering on the official Lego website. I've looked all over trying to find this specific print and even made my own recreation of it but it just looks off. This would be DEARLY appreciated. Thank you.

Hi, I’m looking for part 45499 which is Clikits042 ring narrow band with hole child size? I’m also looking for part 76794 Plastic Cape with Silver Spider Web Pattern, thanks    
  IMG_4041.png (Size: 324.54 KB / Downloads: 67)

Can we get a sort by date option for the Parts List, please. The Parts by week doesn't have enough filtering options.

As mentioned in this old 2014 thread, the real life part and the part in BI have a side stud protruding over the regular 1x1 brick dimensions which was never implemented. It probably should be though since it would be easy to make a model that is unbuildable in reality due to this.

https://forums.ldraw.org/thread-12698.ht...light=4070

There are also a few other differences too in more modern revisions like how the internals are arranged and the internal circular hole depth. It also has those triangular parts which are likely to help hold a bottom stud a bit more securely.

On the right is the BI part and on the left is the ldraw one.  I've attached the latest version of the BI part.

Attached Files

  4070.dat (Size: 25.28 KB / Downloads: 3)

Hello,
with the 2025-08 release something no longer works with the empty.dat file in MLCad (3.20 or 3.50).

Parts that use it are not uploaded correctly.

I did some tests on my PC and found this solution that seems to work without having to update software or change anything else.

Instead of the line:
0 MLCAD HIDE 5 24 0 0 0 0.0001 0 0 0.0001 -0.0001 0 0 0 0
I use:
2 16 0 0 0 0 0 0

if I open the file thus modified with LDPE1.8.96 obviously I have an error: identical vertices. But otherwise I have no problems.
Nothing is displayed, not even an isolated vertex, but the software continues to work.


if I open a part that uses empty.dat with the same software in the same way I have no problems.
I can't verify that any vertex is added, because now the software adds it automatically.

Similarly, if I use LDCad 1.6d there are no problems: no isolated vertex is shown and all parts are loaded.

- I don't know what happens if you export the part to use it in POV or Blender.
- I don't know what happens on other PC.

Massimo