Concatenate pointcache hierarchies about pyblish-magenta HOT 4 OPEN

I think it would be possible to do an alembic cache where you define the root nodes and as such it would skip its parent hierarchy. I do think it's important then to enable the worldSpace setting so that if any of the parent groups were moved that movement is preserved.

In that scenario I would also recommend not taking the "output_GRP" but the "ben_GRP" underneath. Purely because otherwise what's imported will be named "output_GRP" and might be confusing. At the same time if namespaces are there of the item (e.g. ben01_:) then it shouldn't be too much of a problem.

I'm only in doubt whether the taking the closest root node should become the default behavior for the extractor or pointcache family, since it really alters how it behaves.

That would also mean it's up to the artist to define the "top" group they want to extract with their children as opposed to the "shapes" they want to collect including its parent hierarchy. So what you put in the objectSet for Magenta to recognize would be somewhat altered.

@mottosso what do you think?

from pyblish-magenta.

I would include the contents of output_GRP (that is, not the group itself), which I'd expect to be just meshes. If there's a group in there, so be it, it'd be up to the artist/td to decide whether it belongs or not.

from pyblish-magenta.

Sure. What about defaut behavior?

• Exclude the parent nodes? (Maybe pointcache family would then override the defaults?)
• Or keep the defaults (like alembic also has as default) as is right now where parents are included?

from pyblish-magenta.

I would expect a family of pointcache to only apply to instances containing a directory called output_GRP and only pointcache the contents, regardless of what it is.

from pyblish-magenta.