Alembic imports only two frames of animations when vertex color is checked while abc exporting
Closed, ArchivedPublic

Description

System Information
CentOS, Nvidia GTX Titan

Blender Version
Broken: 2.78c official

Short description of error
Blender imports only two frames of alembic animation when that alembic file was exported with vertex colors included.

Exact steps for others to reproduce the error

  1. Open attached file
  2. Select animated object and hit export abc
  3. Check "Selected objects only", end frame = 30, "vertex colors" = true -> export
  4. Import that abc file and get only two frames of animation
  5. Uncheck "vertex colors", repeat last steps and get all 30 frames of animation

This issue became very crucial to me, as i wanted to take generated from Houdini alembic and add animated vertex colors for using it as a mask in further shading outside of Blender.

Details

Type
Bug

I tested with 2.78c and latest blender from git, I cannot reproduce the error you mention.
I have attached my alembic output from the blend file you posted just in case it's different from your output.
(If possible - add your .abc file as well, the one you export from your blender, that way we can test with
the exact same data), and debug more if needed.

I've just tested it on my Debian home machine and got the same result as before on 2.78c. Are you sure you checked vertex colors in the abc export dialog? And what OS do you have?
Here're two files. _vc - is for vertex colors. You can notice they have a huge difference in sizes. And i don't think it will be helpful.
By the way, your file is different from mine in sizes for some reason.

I'm on 'Manjaro (arch based distro)'.

I double checked now - you are correct, I can confirm it now:
I tested with Blender on steam (2.78c - Date: 2017-02-24 14:33, hash: e92f2352830).
This creates the bug you mention.

I've tested with latest blender compiled from the source on git tonight, I do not get this bug there.
But as you say - it happens in blender 2.78c.

Sorry about the initial confusion.

Yes, just tested on a nightly build and the bug is gone. Hope it'll keep it that way in master. Thanks!

Closing this ticket since it appears the bug is solved.