(continued) Just for completeness: CR2 files ought to be less controversial than independent morph target files, because a CR2 contains morphs as "target geometry", stored as DELTAS in the CR2, that rely on the original OBJ geometry. Whereas when a morph target is saved by itself, the result is an OBJ file that can be read in any other 3D modeling package - so a morph target file should always be encoded versus the original OBJ file. But even with a CR2 file, to be safe you should either: * remove all morphs that aren't yours [requiring the customer to transfer any of the original morphs that they need, using MorphManager], * or encode the CR2 file versus the original CR2 file, * or get the original vendor's written permission. -- "Toolmaker" Steve S.