@Sybren A. Stüvel (sybren): any chance to have a look at this? [still wont consider this High prio -- but I know at least two other studios suffering from this as well, and having to go .mdd/.pc2 instead...]
(how did this work for Spring btw.?)
Looks like these are the same issues as in T63534, I will merge this report into the existing one...
It is still rendering, but I assume this is the same as T63534
Thu, Jul 11
T56408 might be related...
I already have a fix waiting for 2.81 in D5191, which I'll commit when the repository is open for new features again (it's now locked in preparation of the 2.80 release). If that fix is in and doesn't help, then I'd really appreciate some files to test with :)
Wed, Jul 10
@Renesmee (Renesmee) , @Sybren A. Stüvel (sybren): I assume this would report a different bounding boxes with the alembic/bin/abcechobounds utility (depending on the CPU)?
Using abcechobounds would save us from using other tools...
Please provide us with exact steps to reproduce the issue. We don't have Clarisse, and I don't know what "combiner" is.
Don't add this to 2.80, no risky changes like this right before the RC.
I've fixed exporting loop normals as well; now things load properly in Gaffer as well as Blender, so I'm confident this is a proper bug fix (or two).
- Added comment about smoothing in SubD loading
- Alembic export: fix exporting of loop normals
Tue, Jul 9
Fri, Jul 5
From quick look this seems OK…
@Micah (Micah) can you make a simple test case for me, with a Blend file, the ABC as exported from Blender, and the ABC re-exported from Cinema 4D? Then I have an example of what the data in the Alembic file should be, and can work to make Blender export that too.
Wed, Jul 3
Wed, Jun 26
I have had the exact same problem these guys ave had. The only way to fix this that I know of is to import the file into cinema 4D, then export again. This will fix the normals. The issue is, it makes the file size bigger. This is extremely inconvenient.
Tue, Jun 18
Jun 14 2019
Please create a new report.
I have encountered an issue similar to this in the FLIP Fluids addon using Blender 2.80 (hash 5e626e766459, June 13th 2019). The FLIP Fluids addon updates fluid mesh geometry in the frame_change_pre handler.
Jun 11 2019
Looks like the (camera) origin is actually correctly scaling with the setting, drawing the camera however fails [stays in original position].
For meshes, this is similar: the selection outline will not scale with the setting the actual polysoup will...
Guess this is CoW-related?
(also getting assert BLI_assert failed: /blender/source/blender/blenkernel/intern/cachefile.c:103, BKE_cachefile_reader_free(), at 'cache_file->id.tag & LIB_TAG_COPIED_ON_WRITE' exiting blender after importing...)
May 19 2019
@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.
May 17 2019
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:
May 2 2019
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?