Docs Projects & files

Merging a project

File ▸ Import ▸ Celas Project (as group)… pulls another .cls into the one you have open, as a group you can pose alongside everything else.

Open is not the only way to bring a .cls into a session. File ▸ Import ▸ Celas Project (as group)… reads a second project and drops its whole layer tree into the one you already have open, as a new group: a way to reuse a background, a prop or a rig you built somewhere else without leaving your current file. The item sits in the Import submenu with the other import formats and is disabled the same way they are, until a project is open to import into.

Bringing one in

  1. Choose File ▸ Import ▸ Celas Project (as group)…
  2. Browse to the .cls file you want to bring in.
  3. The whole project appears as one new group, named after the file, sitting in your current layer stack ready to move, mask or animate like any other group.
A second project merged in as a named group in the Layers panel, sitting alongside the layers already in the scene.

What comes across

Everything the imported project's layer tree holds comes with it: shapes, groups, bones, meshes, keyframes, and every action recorded on an Action Bone (see Smart actions). Its symbol library merges into yours rather than staying separate.

Keeping ids from colliding

Both projects can have layers, actions and vertex welds numbered from 1. Merging renumbers everything from the incoming project into ranges that are free in the project you are working in, so nothing in your existing scene gets overwritten or reparented by accident.

What it isHow the clash is handled
Layer idsEvery incoming layer gets a new, free id
Action idsEvery incoming Action Bone action gets a new, free id
Vertex weld idsEvery incoming weld gets a new, free id
Symbol libraryA symbol whose name matches one already in your library is renamed with a (2) suffix, and every instance that pointed at it by name is repointed at the renamed copy
Because symbols are matched and repointed by name, giving your reusable pieces distinct names before you build a library out of several projects saves a round of (2), (3) renames later. See Symbols & variant layers.

What is dropped

The incoming project's own camera is not brought in: only the scene you are merging into keeps its camera. Everything else in the imported layer tree survives the merge; camera framing and any camera keyframes from the source project are what you lose.