Sun, May 19
@Kévin Dietrich (kevindietrich) Glad you came back! Could you please update your patch D2388 for the current code, so we could review and make it to the master finally, cause it's very important for fluid rendering.
If there's something I can assist with, let me know. I'm not a coder anymore, but maybe a can help.
Fri, May 17
Also I am having problems with sequences again: https://developer.blender.org/T51820
I am not working on this anymore, although I could resume work. This approach was suggested to me by Campbell as a general way to import custom keyframes from alembic archives. The patch was uploaded for review a few years ago: D2324.
I think the approach is pretty nice, as it'll give us a way forward to animate other properties as well.
@Sybren A. Stüvel (sybren): yep, not for 2.80, but this is the way to go, right? [having a cache-fcurve-modifier]
Or is there another possibility [from the design point of view]?
@Philipp Oeser (lichtwerk) it looks interesting, but too big a feature to put into master for 2.80.
Just wanted to check the status on the import-of-animated-camera-focal-length issue:
Thu, May 2
Yes seems like we have the same problem with Alembic export. FBX or obj export works correctly but Alembic doesn't.
Apr 26 2019
I ve tested to render animation with mblur and hair on alembic cache and there is some problems too....not sure if it corelates to the above mentioned problems or its kind of new problem.
Apr 18 2019
Have the same problem, here is a side by side basic test
Apr 17 2019
Is there an alternative to that workflow? Because we use real world scales to be consistent with lighting and materials over live footages. How can we interchange hair between Alembics and still maintain real scales?
Apr 16 2019
Tried to do that but it still breaks the hair
Applying scale is not supported. This changes the mesh data, which is replaced with the data from Alembic. Try creating an Empty, set it as the parent of the imported Alembic object, and scale the Empty.
Hi Atomic and Sybren,
Unsure if applying scale is supported for sequence caches. @Sybren A. Stüvel (sybren) any input on this?
Apr 15 2019
I tried the Tree.abc file in Houdini 17.0 and it does not work. When I unpack the data, I can see that a 4 float vector is written, but that is wrong, it should be only a 3 float vector. Even when I promote (or wrangle) the data into an attribute @Cd, that the viewport expects, all the data is zero (i.e. black).
@Sybren A. Stüvel (sybren) ok, sorry not doing it before....should be done right now
@Libor Batek (lbatek) please put the description of the issue in this task, instead of hiding it in a ZIP file. Hiding it like this makes it invisible to the search engine, and makes it harder for developers to access as well.
Apr 12 2019
Confirmed on first sight
(Looks like 2.79 has a similiar issue even)
Mar 31 2019
Just edit the task description of the other task if you want to add your findings.
Mar 30 2019
Mar 28 2019
Yeah, Bastien. In my case, I found the solution with FBX export.
Note that FBX should also be able to export vertex color data?
Mar 27 2019
Havent actually checked it, and it feels like swapping mesh datablocks in a framechange handler is not the best solution, but would it help getting the evaluated object?
Hi guys. Just found this bug in Blender. And searching brings me here.
I tried to export vertex color from Blender to Maya. Alembic the only format I found to have "vertex color".
And it's doesn't work. Maya can't see the color.
So why can't I fetch the mesh data block, from the .abc animation, in a frame change?
Shouldn't the Mesh Sequence Cache modifier correctly present the current mesh data block, to the API, for the frame it is displaying?
Why does the frame change code fail?
Mar 21 2019
Mar 20 2019
Mar 19 2019
Any news on this? This is a big one in terms of alembic for studios considering using it in thier pipeline, I will be more than willing to supply production example files in email, this will be for alembics exported from houdini specifically.
Mar 18 2019
Mar 6 2019
@Thomas Volkmann (knekke) please do not re-open old reports, even if issue seems similar, it is quiet likely to be something different, so new report is *always* the way to go (you can easily link new one back to an older one if needed, of course). Plus, it makes things simpler to track down (a report that is fixed, then mark as not fixed, then fixed again… becomes confusing).
I have problems again with alembic sequences in 2.8. The sample files further up are crashing too...