(2026-08-07, 2:16)Orion Pobursky Wrote: It's actually a little more complicated. There is no "library" that LDView loads on the server. The library software creates a self contained MPD file of the part that has all the subparts/primitives included. Since the library knows the subpart tree and if a part is official or unofficial it changes how that MPD is constructed. If the part is official, it only uses official data. If the part is unofficial, it prioritizes unofficial files (e.g. part fixes) over official files.
None of this helps you Tom.
What I would suggest is use Travis's suggestion to prioritize unofficial over official parts and every on new LDraw release:
- Overwrite library with complete.zip
- Delete all your downloaded unofficial parts and either use the ldrawunf.zip or have LDView re-download the unofficial parts for you.
Thank Orion. This does actually match my current workflow, and it has been working well for years, since it is uncommon that an updated subpart is strictly required to render a decent part image.
What I find most interesting about your description of how the website generates part images is that it does pretty much what I suggested - prioritizing unofficial subparts over official subparts. I think it is actually more nuanced than my suggestion, since only unofficial parts prefer unofficial subparts, and official parts prefer official subparts.
Unless each app can be updated to reflect this subpart inheritance logic, which is unlikely since some of the apps are basically abandonware, then we should probably live with the limitations until a branched source control system is implemented.
---tom