Alembic in vrayProxyLoader - Using "starting object" parameter gives weird transform

[jbvfx]

Hi

I have a problem with a transform offset when using the starting object parameter on the vrayProxy node with an alembic input file.

If I don't set the starting path, everyting is fine, but if I set it to the root of one of my objects, it gets a weird offset.

In the attached image I have loaded the alembic file twice. One without a starting object path (in green) and one with the start object path to the root of sphere object (in red).

I have attached the alembic file aswell as the Maya scene.

https://drive.google.com/drive/folde...N6-zwnk5yumbi6

--
Jacob

[hermit.crab]

Thanks for the provided files. Something seems to be odd with the specific objects' transformations (also transferred to the .abc), which results in their offset after setting a 'starting object path' in the VRay Proxy. Freezing the objects' and groups' transformations (Modify>Freeze Transformations) prior to exporting as alembic seems to eliminate the issue.

[jbvfx]

Thanks for your reply.

This example was just to show an issue we're having with alembics exported from animation. As I can't upload the actual assets, I created this simple example to show the issue.
We can't freeze the transforms, as we have animation on them.

It seems like the concatenated transforms are not calculated correctly, when using the "starting object path" parameter.

[hermit.crab]

Thank you for the feedback, I understand. The issue seems to stem from the transformations of the groups themselves. I'll log it (Bug-tracker id: VMAYA-9172) for further analysis.