Problem summary The AlembicIn node ignores transformation of locator shapes exported from Maya.
Objects in Maya are composed of two elements, their transform and their shape. To view them both in Maya, enable the Outliner menu option: Display -> “DAG Objects” and “Shapes”.
In the case of a locator, Maya creates a 'locator1' parent and 'locatorShape1' child. The 'locator1' object has transformation attributes. Also, the 'locatorShape1' object has Local Position and Local Scale attributes.
When exported as an alembic, both transformations are included as an ".xform" CompoundProperty as seen in abcecho:
However, when loading the alembic in Katana with the AlembicIn node, the 'locator1/locatorShape1' scene graph location is missing the xform attribute.
Customer reported version katana.3.0v9
Customer reported platform centos7
Steps to reproduce
Create a locator alembic in Maya (or download locator.abc): 1) Start Maya, then select Create>Locator at the top menu bar. 2) Enable the Outliner menu option: Display -> “DAG Objects” and “Shapes”. 3) In the Channel Box tab, set the Translate X attribute to "1" on the 'locator1' object. 4) In the Channel Box tab, set the Local Position X attribute to "2" on the 'locatorShape1' object. 5) Export 'locator1/locatorShape1' objects as an alembic by selecting 'locator1' in the Outliner then select Cache>Alembic Cache>Export Selection to Alembic...
6) Start Katana, create an AlembicIn node and set the abcAsset parameter to the alembic generated above. Notice: the 'locator1/locatorShape1' scene graph location is missing the xform attribute
Expected behavior The 'locator1/locatorShape1' scene graph location contains the xform attribute.
Actual behavior The 'locator1/locatorShape1' scene graph location is missing the xform attribute
Workaround No known workaround.
Reproduced by support This bug has been reproduced in: Katana 3.2v1 - CentOS 7, Windows 10 Katana 3.1v5 - CentOS 7, Windows 10 Katana 3.1v1 - CentOS 7, Windows 10 Katana 3.0v9 - CentOS 7, Windows 10 Katana 3.0v1 - CentOS 7, Windows 10 Katana 2.5v1 - CentOS 7, Windows 10 Katana 1.6v3 - CentOS 7
Earliest version tested Katana 1.6v3 - This issue appears to be in all versions of the product