Limitation

• Transfer material depending on a definition in file mat_dict.json.

• This tool uses an alembic file apart to send objects. can not send controller or modifier at all. You can only send the final scene as a still model or animation with alembic cache.

• Why choose alembic, not FBX.When you have a name that is not a number/character Maya FBX not support that name which hard to reconnection any node

• This tool work on alembic import/export . Which makes this plug-in have limitation same alembic system.

• Not support for instance object.

• You can only submit materials and attributes in specific materials that are defined in the file mat_dict.json 

Warning

• Naming  Maya not allow to have repeat naming. please beware of duplicate name (even mesh and material cannot repeat in Maya)

• Be careful when you send by custom option to send. IF you get all updates, but you send only mesh you'll get updates of light, shade and camera not the same version with mesh.

• Need to unpack texture first in Blender scene. In a blender, if you have texture packing you need to unpack first because can not file a texture path in Maya.

• Expert animation with cache only. Not have a keyframe.

About this tool

I try to use a blender to speed up work and found the advantage of a blender. But not convenient for manual convert material and object, so made this tool.

Blender can use to support VFX process even not directly, but you can use it for a part or maybe finish your work. For example, if you need to fast render in your acceptable quality you can use Eevee for rendering. Use the many modeling add-on of Blender to help you faster modeling. Etc. 

next goal

• Increase supported material nodes for Vary in Maya.

• Support for Arnold and Redshift renderer in Maya.

• Support for 3ds Max for communicating with Maya and Blender.