AY-6593_Xgen "Connect" action on multiple Alembic curve caches fails

[ynbot]

Please describe the issue you have acountered?

When using multiple palettes/splines in an XGEN description each of the entries, when applying a cached alembic should receive an input alembic cache file that contains only the curves for that palette. Currently the XGEN Connect action in Inventory connects all the palettes to a single Alembic entry (single pointcache) but with multiple palettes we need each entry to be connected to an Alembic of its own.

Note: It may be that there is a way for XGEN to work with one big alembic and it knowing which curves belong to which palette within it. But I couldn't find it.

Sidenote: What is unfortunate is that for the Connect XGEN action to work is that you need to load the curves into the scene and then "connect" but the actual "connect" that it does by no means uses the curves in the scene. Instead it just takes the Alembic filepath of that pointcache and sets that as filepath attribute on the XGEN palettes. Which means that what the XGEN is connected to is not tracked in the manager as a container, if you update the pointcache in the scene it does not live update the XGEN attributes hence basically on any pointcache update you will need to do the Connect XGEN again. Which is cumbersome (and also for the case of multiple palettes wouldn't even work).
[11:20 AM]
Also, because each needs an Alembic of its own we now suddenly need to make many pointcaches from the source workfile for each palette. Which is manageable with the scripts I provided to batch create those but it's not necessarily artist friendly in production to have to select and create those each time in animation scenes, etc.

How to replicate the issue?

No response

Additional context:

link to discussion on Discord
(might be a private channel)

This issue was automatically created from Clickup ticket AY-6593