Problem summary
If you export an Alembic that contains a Camera with values being provided by an Axis node (through the Camera's Axis input). When either re-importing the alembic file or using it in another program, these values are not applied to the alembic file.
This occurs for any alterations to values, including animations.
Customer reported version
Centos 7
Customer reported platform
Nuke 11.3v3
Steps to reproduce
1) Create an Axis node and set several animated keyframes (over any duration)
2) Create a Camera node and connect the Axis into the Camera nodes Axis input
3) Create a Scene node and connect the Camera output
4) Create a WriteGeo node and connect the Scene node into this
5) Render out as an alembic file (including all abc options)
6) ReadGeo the Alembic back in or import into a 3d package Result: Values are not carried through from the Axis to in the Alembic file
Workaround
There are two workarounds for this problem, till a permanent solution is created:
1) Attempt to do any alterations to values in the Camera node, this will bake the animation in the alembic as a camera
2) If you need to use an Axis node, expression link the Axis node values to the Camera node values. If the Camera node has set values that don't change, you can 'add expression' on the field and type 'curve' + 'camera's original set value' eg rotate x = 10.
Reproduced by support
This bug has been reproduced in: