Studio library inconsistencies


Studio library inconsistencies
#1
Thinking again about this post (from Philo) about Studio:

(2024-06-21, 8:24)Philippe Hurbain Wrote: Is it possible to create an MPD embedding ALL official and unofficial parts? My use case is to render (or create BIs)  a model with Studio without fiddling with all part incompatibilities, libraries not in sync causing missing subparts and so on...
The complete scenario would be to embed all parts, add a prefix to avoid any conflict with existing Studio parts, extract these parts from MPD with MPDwizard, and place them in Studio CustomParts folder. After that, the model _should_ import flawlessly in Studio.

There are so many of these inconsistencies that when you have a really big build (like the Notre Dame cathedral I just finished), it can take quite a long time to adapt an LDraw model to Studio.

Remind me again, what's to prevent me from simply copying my entire LDraw folder in place of the one that comes with Studio, so that it always has the full library every time?

Or would it truly be better to try and embed all parts in an MPD, as Philo suggests?
Reply
« Next Oldest | Next Newest »



Messages In This Thread
Studio library inconsistencies - by N. W. Perry - 2024-11-10, 23:58

Forum Jump:


Users browsing this thread: 1 Guest(s)