Fri, Oct 11
Apart from importing via Alembic, there have been issues with smooth/flat object shading regarding NVIDIA cards. See T68681. It is plausible that an Alembic import can be successful, but a manifestation of T68681 disrupts the observation of a flat/smooth object setting.
Thu, Oct 10
I managed to run a few tests and it works!
Mon, Oct 7
Here is another test with a file containing 3 different case studies (a fractured objet, a liquid sim, and a rotating object), all of which have custom velocities:
You have to apply the patch and compile Blender to test the feature, it is not in the daily builds. Also your file does not have velocity information (the array size is 0). So without the patch and without custom velocities, Cycles is just using an interpolation between the previous, current, and next frames.
I have some blurriness, but it doesn't seem to look right. (see Images)
This is a particle system that I exported and then reimported to reverse the movement. And the plane is a dupliobject on the vertices of the ABC.
I would not expect to see a clear outline of the plane in the image with motion blur. Also, the position of the blur is set to Center. But this seems more like Start. And the shutter duration also has no effect.
For those who haven't noticed, I updated and fixed the patch D2388, please try it if you can!
This patch is nearing completion, with one remaining property to be added. Here are some examples:
- Attempt to update the code.
- Finally make motion blur work!
Wed, Oct 2
Thank you for the explanation, baking pivots in Maya resolves our problem.
thx for learing that up @Sybren A. Stüvel (sybren)
Blender simply uses the transformation matrix of each object, which is constructed from the Alembic file by the Alembic library itself (source). The Alembic file can contain various separate operations, or the final matrix. In the case of this Maya-generated file, it contains a sequence of operations. This is such a sequence:
Only thing I can think of is we are not hadling (more or less a stab in the dark...)
This is abcls for that file (still assume it has to do with the .ops part of the XForm?)
Attached is the case of a cube with the pivot manually set to the center of its top face. The file imports back to Maya with the pivot in the same location.
The objects are exported from Maya 2019.1, please let me know if there are specific test objects you'd like me to generate.
Not sure about this.
Fri, Sep 27
I'm closing the revision as it seems to be abandoned by the author.
Wed, Sep 25
Cool, thanks for the confirmation, closing then.
Tue, Sep 24
That is actually already in the tracker... T49234: Alembic not importing motion blur
Fri, Sep 20
Can we have setting so blender automaticly reads orient attributte? And rotates proxy/instance acordingly?
Thu, Sep 19
Wed, Sep 18
Tue, Sep 17
This is indeed not a bug, it's simply a property that's written to Alembic and that's not read by Blender. Alembic is quite bad in this respect, in that there is no well-documented open standard in which such properties are defined. I'd be very happy if you can prove me wrong on this one.
Sep 12 2019
Thank you, Philip
There is a good chance this has already been fixed, see
Sep 3 2019
Sep 2 2019
Time to archive this imho...
Here are the Alembic file and the texture for the swapping face parts.
Moreover, in the beginning, the rigger used moving UV's as a way to stay with the same plane and still swap between the faces texture grid, but it also didn't work in Blende...
We have the same problem:
As you can see, the rigger used "Write visibility" option to swap between face parts. In Blender - all planes are visible.
Aug 30 2019
Just tryed it, look like it work in 2.81, thanks for the Fix!
Aug 27 2019
I'm exporting from maya (2018) . I was sure the test file had normal export enabled. Here i tried here with another test alembic with normals and it also is importing as flat shaded, smooth shading has only effect on first frame, after disabling face on modifier.
Since rBe9c149d911c2, reading loop normals should be supported.
In your file, normals dont seem to be exported:
In a way this is similar to the lack of importing e.g. Focal Length (T54050: Camera focal length animation not importing), or Custom Properties (T50725: Alembic export doesn't take 'Custom Properties', as alembic non-standard data.).
Aug 23 2019
Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.