(Yesterday, 23:58)Travis Cobbs Wrote: This seems to be an LPub3D problem, not an LDView problem. I'm guessing it was assumed that adding a 110 prefix to a standard color would never result in an overlap with some other standard color. Having said that, is there a reason that certain colors (like Trans_Black, Trans_White, and Trans_Tan) were given 5-digit color codes?
The current standard is to assign newly released colours their official Lego ID.
In the past these numbers were for the most part unknown, so different numbers were picked (example: LDraw 19 Tan = Lego's 5 "Brick Yellow"). Unfortunately this caused many official IDs being occupied by the wrong colour in LDraw (some of the Fabuland colours might become a problem in the coming years, when Lego reaches the 500 range).
To avoid accumulation of these problems, it was decided, that all newly added colours for which an official ID is either unknown, already blocked or likely does not exist (rubber, canvas, thosetransparent sticker colours) gets a 5-digit ID.
Further for some ranges the idea was
variant_colour_ID = base_colour_ID + x
where x is a 5 digit number specific to that use, like 20000 for Canvas, 30000 for Modulex.