@Atomic (atomic) please attach example files to the task description, so that people interested in solving this don't have to read through each individual comment to see which file(s) they should be using.
Also see e12c31100. Guessing for default values is a tricky thing, especially since Alembic doesn't seem to have a standardised property for the curve resolution (I'm gladly proven wrong on this one). Having resolu=12 is fine for a simple case like T53839, but brings down Blender to a crawl when importing animated hair from another package.
Wed, Mar 21
This is fixed in 09c88fed1f58df642c7a13fc5a32057b7160f85c
Fri, Mar 16
I guess this isn't the right place, but can I ask for a relative file paths option on Alembic import?
This should be fixed now (rBe5327afcb73f), thanks for the report!
Thu, Mar 15
Tue, Mar 6
Feb 20 2018
Here's what I've got so far...it builds successfully and exports valid Alembic files, but abcls doesn't find the mayaColorSet=1 flag so I'm still doing something wrong.
Alembic::AbcCoreAbstract::MetaData md; md.set("mayaColorSet", "1"); OC4fGeomParam param(prop, name, true, kFacevaryingScope, 1, 0, md);
Feb 19 2018
OK, progress--I can build Blender from source with Alembic enabled. Next step, @Dario Seyb (daseyb) says for Unity he used the following to add the Maya color set flag:
AbcGeom::MetaData md; m.set("mayaColorSet", "true"); m_colorSet = AbcGeom::OC4fGeomParam(m_scheme.getArbGeomParams(), “Cd”, true, AbcGeom::GeometryScope::kFacevaryingScope, 1, m_tsi, md);
Could you help me adapt this for Blender in abc_customdata.cc? I'm getting more certain that this is the fix to make Blender vertex colors readable in Houdini and Maya.
Feb 18 2018
Feb 17 2018
If I wanted to recompile Blender's Alembic export module with the mayaColorSet=1 flag added, where in the source should I look?
Feb 13 2018
Feb 4 2018
Ok, thanks :)
@Juan Gea (juang3d) no one is working on that currently, otherwise there would be some activity here.
Jan 30 2018
How is this going?
Well hm, afaiks this is a matter of setting the curve resolution.
In 278c curve resolution wasnt really considered at all thus defaulting to U=12
Jan 28 2018
Please update the description of the issue so that it's complete, example files and all. That saves people (like me) from having to read through all the comments and from figuring out which files are relevant.
Jan 26 2018
OK, can confirm both issues
- when importing meshes, then particles --> both are visible, but meshes dont animate anymore
- when importing particles, then meshes --> only particles are visible
It seems that I uploaded a mesh file by mistake.
@hidenori saito (hisai): maybe I am missing the obvious, but the provided zip only contains the foam/particles (HY_Foam01_00000.abc - HY_Foam01_00031.abc)? Where is the mesh part?
Closing this, since it's an upstream Alembic limitation that I can't solve.
Jan 24 2018
It seems that the bdc file will be output to a separate folder after putting this check in the screen shot.
How about thinking it is irrelevant to this case?
note though that I do get messages like this:
Particles (HY_Foam01_00000.abc - HY_Foam01_00031.abc) seem to be imported correctly - and are animating on my side?
Are you sure you have checked Is Sequence in the Import Alembic options?
Uploaded file simulated with realflow10
could you share the .abc files here please?
Jan 22 2018
looks like indexed is the way to go (and not directly as an ArrayProperty)?
Jan 21 2018
I re-conducted the import test on Windows 7 downloading the new file I posted.
This does produce working results. However, the result in 2.79 are wrong while the results in 2.78c are correct.
It does look like the original attached file was corrupted on upload somehow? I am re-uploading the same exact file, which does work on both Houdini 16.5.332 and Blender 2.79. I have removed the bad file from the first post.
Jan 19 2018
hm, true, file seems to be currupt, no? abcecho and abcls even crash...
Well, here is what Houdini 16.5 says to the attached .abc file.
I can't load this file neither on linux nor windows, it's also suspiciously small you sure it's not just a corrupt file?
OK, this is from maya (also writes them indexed)
Jan 16 2018
We weren't using the provided index at all. As it turns out that index often just contains the indexed number, i.e. index[i] = i, so in those cases ignoring it was fine. I've implemented a lookup via that index now, and that fixed this issue.
Jan 15 2018
Here's how vertex colours are represented in each of the Alembic exports. Can anyone tell me why Houdini and Maya can see each other's vertex colours, but Blender's aren't visible in Houdini or Maya? Looking at the logs here, is it just as simple as adding a mayaColorSet=1 flag to the Blender compound property on export?
Jan 8 2018
I'm also getting Alembic: color index out of bounds reading face colors for object /Stage/Symbol/paint_1_1/Frames/FrameMesh, property Cd on import.
@Sybren A. Stüvel (sybren) : could you have a look?
I think so, the application is called AnimVR.