odf posted at 7:05 PM Thu, 22 September 2022 - #4445076

Not a bad idea, but since this apparently affects other independent figures as well, maybe it should be a separately maintained and distributed script that comes with a mini database of figure hierarchies.

In general a database of figure metadata would be of great benefit. Part of the relative success of DAZ is due to their system approach to content: once you select the figure you get an overview of 'smart' content that can be used with it. Conversions are largely transparent and many parameters are set automatically. This greatly helps acceptance of their figures. The system is effectively under their control and of course this gives them great power as developers. One can debate the degree to which they use it to 'stimulate' sales, but that is another discussion.

Poser works fom clean slate all the time,  leading either to complex and fragile procedures that re-do the same work over and over again. You cannot tell the Fitting Room the garment is tailored for V4 and it does not recognise the target figure is LF, so each time it has to use complex and fragile wrapping procedures and 'easily going wrong' regrouping. To my knowledge EZSkin is an exception maintaining a database of conversions. It uses the name of the geometry file as a key. 

The acceptance of Antonia was hindered by the various branches,  which people noted because their content did not work correctly. I therefore think Antonia would be helped if there were, to begin with, a metadatabase including hierarchy and other data relevant for converting and applying content. When it works it could be used for other figures also.

But yes, this need not affect current developments and would be one of the frills.