AlembicMesh3D

Alembic is primarily a baked geometry/cache interchange format. Resolve 21 describes Alembic payloads as capable of carrying meshes, cameras, points, UVs, normals and baked animation, but that does not mean an arbitrary source scene transfers losslessly.

Fusion offers two import paths. A manually added AlembicMesh3D loads the .abc as a direct file-backed mesh/object path. Fusion > Import > Alembic Scene is the preferred path for a complex scene because the importer expands supported hierarchy and transforms into editable Fusion nodes.

Scene import has an important persistence boundary: imported transforms are read into Fusion controls/splines and saved with the comp, while mesh geometry continues to reload from the external Alembic file. Moving the comp without the .abc can therefore preserve transforms while losing the actual mesh.

Treat Alembic animation as sampled/baked data rather than the original Maya, Blender or Houdini rig. The importer detects sampling rates and should normally be kept at the export/source rate; changing the resampling rate is an intentional retime, not a harmless quality setting.

Resolve 21 explicitly notes interchange limits: lights, materials, curves, multiple UV sets and velocities are not reliably supported Alembic payload classes. Blackmagic recommends FBX for lights/cameras/material-oriented interchange and Alembic primarily for meshes.

AlembicMesh3D has two Node Editor inputs and both are optional because the file itself generates geometry. Orange SceneInput adds another classic scene3d branch. Green MaterialInput is documented specifically as a 2D bitmap texture for the imported Alembic surface.

The current captured Inspector exposes three direct-node-specific controls: Filename, Object Name and Wireframe. Import-dialog controls such as Hierarchy and Resampling Rate belong to the Alembic Scene import workflow and should not be taught as always-visible controls on the direct node.

Object Name identifies imported mesh context. With the direct-node path, a blank value means the Alembic contents are brought in as one mesh; with Alembic Scene import, Fusion populates the field for the corresponding imported mesh.

Wireframe is a geometry diagnostic. Resolve 21 documents a conditional anti-aliasing option when Wireframe is enabled and states that wireframe can be rendered to file when Renderer3D uses the OpenGL/Hardware path.

Visibility, Lighting, Matte, Blend Mode, Normals/Tangents and ObjectID are common classic-3D object controls. Material and Transform are common 3D tabs as well, so diagnose file/import problems separately from generic object/material controls.

AlembicMesh3D Output is scene3d, never a normal RGBA image. Merge it with cameras, lights or other objects via Merge3D or the optional SceneInput, then rasterize through Renderer3D before MediaOut or 2D effects.

The bundled screenshots verify the current Controls, Material, Transform and blend-mode UI. Exact exporter-specific hierarchy behavior, cache playback and the target Resolve build still deserve live testing with the real production .abc.