'Small' keys missing in an import Alembic scene

Hi,
we are working with pretty large scenes in Maya and we have in particular a cardBoard (a simple moving plane) with an animated scale, relatively small values (between 0.100 and 0.200).

When we export the cardBoard via alembic and try to import it in Fusion all small keys are missing, e.g. every keys vith values in the range [0.105, 0.106].

We explored the abc file and the info are there (reimporting the abc in Maya works fine), and by putting manually the original values everything works as expected.

Is it a known bug?
Is there a way via Lua/Python to increase the 'tolerance'?

Guido Pollini

No sure if it's works the same for Maya, but I've had to bake my animations first in c4D and in modo, then export the .abc. Rather than having the alembic export bake the keyframes.

Also, be sure to import the .abc file through Fusion with file/import/alembic scene.

Hi Ryan, thanks for the answer:)

I did try to bake everything but nothing changed; apparently if a key value is very small the importAlembicScene algorithm discard the following keys until it finds a future key which has a 'solid' value.
It doesn't matter where we are on the timeline... Key holes appear:)

Eventually this won't be a serious issue; I couldn't find a Lua/Python command to perform a script 'import alembic scene' (am I missing something?) so we reverted to a 'textual' alembic import via an external Python interpreter. By doing this way Fusion doesn't complain because it has of course no trouble in managing very small values.

It really seems to be a 'bug' of the importer.

Gui