It’s nice to see how this thread has evolved with the development, builders and testers. This is OpenSource 
Congratulations!
It’s in master now, isnt it?
I added the libs for all msvc flavors earlier today, the buildbots should already be configured to look for them, so with a bit of luck it’ll be in there next time they build
KWD - Great work, really great, thank You and everyone else which was contributed to this project. It helps Me ALOT with something.
Are LazyDodo’s libs and adjustment to buildbot working for you?
Yep, everything seems to be working now!
Hi KWD! A belated congrats on getting your work merged in master
About the exported camera with animated focal length (post 355) do you want me to report it on d.b.o?
Thanks 
About the exported camera with animated focal length (post 355) do you want me to report it on d.b.o?
Please, do so. I cannot reproduce the issue with a simple test file, so maybe you can (and have to for bug reports 
) provide a simple file that shows the issue.
I put some debug prints in the code and got this (fov animated from 25 to 80 from frame 1 to 25):
Writing frame: 1
Writing camera focal lens: 25
Writing frame: 2
Writing camera focal lens: 25.2102
Writing frame: 3
Writing camera focal lens: 25.8454
Writing frame: 4
Writing camera focal lens: 26.9086
Writing frame: 5
Writing camera focal lens: 28.3975
Writing frame: 6
Writing camera focal lens: 30.3025
Writing frame: 7
Writing camera focal lens: 32.6056
Writing frame: 8
Writing camera focal lens: 35.2794
Writing frame: 9
Writing camera focal lens: 38.2854
Writing frame: 10
Writing camera focal lens: 41.5745
Writing frame: 11
Writing camera focal lens: 45.0869
Writing frame: 12
Writing camera focal lens: 48.7539
Writing frame: 13
Writing camera focal lens: 52.5
Writing frame: 14
Writing camera focal lens: 56.2461
Writing frame: 15
Writing camera focal lens: 59.9131
Writing frame: 16
Writing camera focal lens: 63.4255
Writing frame: 17
Writing camera focal lens: 66.7146
Writing frame: 18
Writing camera focal lens: 69.7206
Writing frame: 19
Writing camera focal lens: 72.3944
Writing frame: 20
Writing camera focal lens: 74.6975
Writing frame: 21
Writing camera focal lens: 76.6025
Writing frame: 22
Writing camera focal lens: 78.0914
Writing frame: 23
Writing camera focal lens: 79.1546
Writing frame: 24
Writing camera focal lens: 79.7898
Writing frame: 25
Writing camera focal lens: 80
Importing the file back does not show apparent issues.
Just some heads up, I have pretty much finished implementing the FCurve cache modifier I talked about a couple of weeks ago, to support arbitrary property animation (main goal being camera field of view):
This is not in master yet (and has to wait for after the release, since we are in bug fixing period), so if people want to try it out, you can check out the abc_fcurve branch from my github repo.
Great work on Fcurves!
Just to report that currently both CURVES and 2 vert primitives (curve>poly convert) fail to export to external applications.
NEVERMIND NEED TO UNCHECK SEQUENCE - SORRY
Hi,
Something is wrong loading a single ABC file sequence. My simulation last 420 frames, and when loading now after merging to master it last about 20 frames, I mean not only 20 frames are loaded but whole 420 is compressed to about 20. What is wrong?
I can’t upload this is 68GB one single ABC file.
Kamil.
Thank you for working on this. I tested it and it seems to work as expected - it is so nice that everything is setup automagically
I don’t have any apps (besides Blender) that can actually save an Alembic file, so can’t test camera I/O as I want to. Also hit a few bugs, which is totally fine at this point, such as Blender crashing when trying to add the fcurve modifier manually, and one I can’t replicate where playback of an imported file (anim camera + suzanne) ran at half speed (10-11 fps) until I closed Blender and tried again.
Anyway, thanks again Kevin!
Hey Kévin, just wanted to say big THANK YOU! for implementing this.
This is crucial for embedding Blender into mixed pipelines.
Tried it today for the first time. We’re on a Max+Vray and Houdini pipeline here, where I’m the lone guy using Blender as a Swiss Knife App.
Anyway, successfully managed to import the camera from Max, and been exporting assets from Blender to Houdini using Alembic.
Big thanks on the hard work! Much appreciated.
same.
Big thanks on the hard work! Much appreciated.
Awesome. Great work. Thank you.
I’m just compiled blender master with alembic.
And lok’s like it works! Thank you!
This is one of greatest features of this year!
Thank you!
Great job!!
Testing a workflow Blender-Alembic-Unreal (4.13).
- Mesh and animation are ok, but scaled down (1/100), x inverted and roteted (y-z). (No scale rotation problem on importing on Max/Maya)
- Materials names and assingments (per face) are fine on Unreal import!! This doesn’t work on Maya-Max. Probably due to Alembic 1.6 in Blender and Unreal.
- Normals are problematic on Unreal import, maybe related to non triangulated faces on Blender-Alembic.
As long as triangulate character is problematic (it leads to brake bland shapes), an triangulate faces option on Alembic export would be great.
I’ve encountered a bug with alembic that crashes Blender every time.
The Alembics are exported from 3ds Max 2016.
Case #1:
If the export has an Empty (in Max Point Helper), once you save a file and reOpen it - instant crash when you enable the layer where the Empty is.
Case #2:
Import alembic with some mesh. Add a cube. Save. ReOpen - instant crash when you enable the layer where the alembic meshes are.
This will not crash Blender though
Import alembic with some mesh. Save. ReOpen. As long as you did not add a Blender mesh to this, it does not crash on reOpen.
I can provide an alembic file, and a blend file that’s crashing it.
I’ll report this to the bug tracker later tonight.
Edit:
I was digging through this issue a bit more.
The problem seems if you parent something to the Alembic Object, enabling the layer visibility of the layer where either the alembics are or the object that is parented to alembic crashes Blender.