SetTime Operation very expensive.

[michael-burk]

Hi, thanks for this great project!
My issue is, that the SetTime Operation seems over the top expensive.
I just want to playback and animation with 20 objects. When I record all the matrices for every frame and play them back customly this is much much more efficient.

[torinos-yt]

Currently, I think SetTime is the most expensive part, since the call to SetTime evaluates and interpolates all mesh and transforms in the alembic archive.

However, if the mesh in the archive does not contain vertex animations, then the per-vertex processing should be skipped. Your alembic could have 20 Transform animation objects merged into one object that does vertex animation on export. Or VL.Alembic may not be able to handle your alembic well enough.

If you share an .abc that can reproduce the situation, i may be able to investigate (although it may take some time as it is difficult to get enough time on this project right now).

[michael-burk]

Hi and thanks for your answer.
In our case we have 20 objects, just animated over scale, rotation and translation - so no vertex animation is necessary.
We can't really combine all of the objects, to not loose individual material properties.
Is there a way to skip the vertex processing in a case like that?