Choose 'Run Script' from the 'System' menu (Shift-F5).Navigate to where you've unzipped the zip file and double click on 'install.py'.In the next dialog, you need to navigate back to .the same directory (the same one where 'install.py' is located, not InstallFiles directory!) so that the install script can find the files it needs to install.

If the installation was successfull, a dialog 'Installation Complete' should pop up.

Restart modo.

After restarting you can add AppLink button to modo, by duplicating one of the existing buttons, (Horizontal Toolbars / modo Modes / Vertices) for example.You can do it by choosing System -> Form Editor from the menu, then hitting "Find Form" button and selecting Vertices selection mode button. You'll see Vertices item highlited in Form Editor, Right Click -> Duplicate on this item. Now rename duplicated item to 3DC AppLink, remove all text from 'command' field, enter this text instead and hit 'Return': @3dc_applink.lxmChoose custom icon, you should have 3dc_applink.png icon in your Luxology\Scripts folder.

AppLink should also work in older modo versions, such as 301 and 302. To use AppLink script in modo 30x on Windows OS, you should install Python 2.4 (even if you already have higher version of Python installed, such as 2.5/2.6/2.7/3.1, it won't help to run AppLink in modo 30x, install Python 2.4 - it could coexist with any and all Python versions already installed without any problem as long as it's installed in it's own folder - default installation option in Python installers). Download last Python 2.4 for Windows here:

In modo, select object(s) you want to edit in 3D-Coat, run AppLink UI via created button or by entering @3dc_applink.lxm in the 'command' field in the bottom-right of the modo UI, choose 3D-Coat Export Type and hit 'Export to 3D-Coat' button. Choose the name and location of the file and set file type to .obj

Run 3D-Coat (or bring the focus to it's window if 3D-Coat was started earlier), a dialog with options based on your 'Export Type' selection in AppLink script should pop up. Set needed options, hit 'OK' and edit imported mesh to your heart content, using 3D-Coat's rich features for Texture Painting, UV Editing, Retopo and Sculpting. When done, select File -> Open in Originall App from 3D-Coat main Menu.

Now go back to modo, hit 'Import from 3D-Coat' button to bring edited mesh with textures and maps created in 3D-Coat back to modo, shaders will be created and texture maps assigned to the correct shader effects (displacement, normals, specular and color). You can repeat the whole process as many times as needed.

Now you can send meshes to Modo straight from 3D-Coat, by using File -> Export to -> Modo menu in 3D-Coat.Modo will be started if needed, and mesh will appear in the scene automatically within 45 seconds (Use this time to choose export options and to save files in 3D-Coat).

If Modo started earlier, to get geometry and textures you've exported from 3D-Coat via File -> Export to -> Modo menu use "Get from 3D-Coat" button in AppLink GUI as usual.

!!!---IMPORTANT---!!!

To use Auto-Import functionality (originating from 3D-Coat, by using File -> Export to -> Modo) you should use normal AppLink at least once, so it could create needed files for Auto-Import functionality.

Hi guys. I'm a user of Modo and I bought this program to expand the possibilities. But now I found that applink not work for my configuration (OSX 10.8.2, modo 601,3DC-3.7). All of the install instructions in the forum did not work. Maybe I did not understand something or need to wait for the release of 3DC-v4?

Thanks for your reply Javis. I tried again step by step. The system says that the installation was successful but if I try export.. Modo issues "error evaluation failed script: Unhandled exception, line 42; 'SYSTEMDRIVE'"

Just would like to confirm that I am getting the same error message for Modo app link as the above user Jeemale (Modo 601 on Mac OSX-10.6. . In fact can't get the applink options menu to show drop down menu options. Just get a blank drop down and error message.

Hiif one of you that having Problems using a V4 Beta please have a look at your Exchange Folder in V3 of 3dCoat it was in a subfolder named 3d-CoatV3 in V4 Folder Name was3d-CoatV4.

In the Modo Applink in this Tread all Folder directions have the old pre V4 Beta Applink Path see here in source Code

\\Documents\\3D-CoatV3\\Exchange\\import.txt

you can try the manual Installation in this Forum a few posts later there the Folder is Hardcoded in Script to new Exchange Foldernormally if you have not deleted your old Exchange Folder in your Documents Folder all must work ok but if you deleted this Exchange Folderyou can make manually a new one or use the other manually install of Modo Applink for V4 Beta and higher.

Main problem is that in V3 all Applinks are searching a Exchange Folder in a Folder called 3d-coatv3 if Andrew leave all like it in this Beta worksthan with 3dCoat V5 all Users have tree 3d-coatVx Folders it was much better do now a break go out of that Folder to a Folder Like Documents Applinkor else.It is no real good Idea that 3dCoat works in a Folder called 3d-coatV4 but searching for Applink in a Folder called 3d-coatV3, all Applinks need thatthis Folder Exist the Path is in most ones hard coded.

Anyone figure out how to assign the V4 folder instead of the V3? I was able to install the Applink fine, but it's not working because the scripts have not been updated to look in the MyDocs/3D Coat V4 directory. And the ability to export from 3D Coat V4 directly to Modo (FILE > EXPORT TO > Modo) is not there. All because this script has not been updated.

Please fix. Thanks.

EDIT: I found that you have to first export a model from Modo to 3D coat, via the Applink, then you will have an EXPORT TO > Modo option in the FILE menu. You have to use that to send a mesh to Modo, then when in Modo, you have to select IMPORT from 3D Coat. If you try to just export it directly from 3DC in the FILE menu, that is not enough. The 3ds Max Applink, it is. The change will be there immediately on returning to Max. So, with these extra steps, it should work for the most part.