In this case, a user installed the latest MtoA, but when he went to load mtoa.mll in the Plug-in Manager, he got this error:
--------------------------- Settings/Preferences: maya.exe - Entry Point Not Found --------------------------- The procedure entry point ?IsRenderablePath@CArnoldSession@@SA_NVMDagPath@@@Z could not be located in the dynamic link library mtoa_api.dll.
From past experience, I knew that the problem was probably the Maya.env file. And sure enough, it looked something like this:
MAYA_RENDER_DESC_PATH = C:\solidangle\mtoadeploy\2013.0.22.0 PATH = %PATH%;C:\solidangle\mtoadeploy\2013.0.22.0\bin; solidangle_LICENSE=5053@SOLIDANGLE-PC MAYA_RENDER_DESC_PATH = C:\solidangle\mtoadeploy\2013.0.22.1 PATH = %PATH%;C:\solidangle\mtoadeploy\2013.0.22.1\bin;
Notice that there are two MAYA_RENDER_DESC_PATH and PATH settings. Maya reads just the top two, which are for an older version of mtoa, so when Maya loads mtoa.mll we end up with a “missing entry point” error.
How did this happen? Well, in this case, in-between installs and uninstalls of different versions MtoA, the user had updated Maya.env with his own MAYA_RENDER_DESC_PATH and PATH settings for MtoA. And then the next install of MtoA appended its own settings to the Maya.env file.
The MtoA Installer works like this:
- Installs make a backup of the existing Maya.env, and then append the environment settings to the existing Maya.env.
- Uninstalls restore the backup version of Maya.env.
So if your Maya.env already has MtoA settings for MAYA_RENDER_DESC_PATH and PATH settings, then when you install another MtoA, you end up with a problem (because the new settings will be at the bottom, where they are ignored).
Ok, so that’s problem solved. Just remove those extra entries from Maya.env.