Studio library inconsistencies


RE: Studio library inconsistencies
#4
(2024-11-11, 2:17)N. W. Perry Wrote: Does Studio prioritize custom parts over its main library, if the filename is duplicated?

No.  Stock files are prioritized.
You can test that by putting a random model in CustomParts and naming it 3001.dat: you’ll see a 2x4 brick.

And the copy in the Custom Parts palette will be categorized as a Brick.  That’s a good way to see if the part is now officially in Studio: it gets a category.  It’s also a problem because some parts (DUPLO) are in Studio’s database with no category (= category zero), and therefore don’t appear anywhere.

Also, the other solution of replacing Studio stock files is a bad idea because updates will corrupt the files (the update program, Patcher, uses binary diffs).

And, yes, Studio’s “ldraw” folder is a fine mess.  With duplicates in UnOfficial, and butchered LDraw files (latest seen is 10169: the original had been unnecessarily subfiled in 2019 and is now broken by the inclusion of the new patterned versions which use another subfiling).
That folder needs a good clean-up and update.
And the “database” (StudioPartDefinition2.txt) too.  And it also needs to be automatically updated when the catalogue is changed (parts re-IDed or renamed), but it’s not a priority.  The devs seem to prefer my nagging them every few days with a new correction to make 🤷‍♂️
Reply
« Next Oldest | Next Newest »



Messages In This Thread
RE: Studio library inconsistencies - by Sylvain Sauvage - 2024-11-11, 13:28

Forum Jump:


Users browsing this thread: 1 Guest(s)