Jan12
Jan11

HowTo: Fix the Import-Integration of Cinema4D in Unity

The Upgrade to Cinema 11.5 was released a couple of month back and shortly there after the update to Unity 2.6 was out. And right after that there was a wave of complaints that the automatic Import of C4D files into Unity is not working any more.

I had this problem as well, but could figure out a solution rather quickly. I shared my solution on how to fix the problem and thought nothing more of it. Yesterday I stumbeled across several topics in the Unity Community in which people stated that the import is still broken for them and they are now doing manual conversion to FBX.

Here is how I fixed the Import:

  1. Make sure Unity and Cinema4D are not running
  2. Run Cinema4D in 32bit mode (goto ‘Applications’, Show Info of ‘Cinema 4D’ and check ‘Run in 32bit mode’)
  3. Set user rights on the ‘Maxon’ folder in ‘Applications’ to rwx for user, group and everybody
  4. Delete the folder ‘Unity-C4DToFBXConverter’ in plugins
  5. Open Unity and try to import a C4D file
  6. Unity will open Cinema4D and install the Converter and then trie to use it to convert the C4D automatically to an FBX file which it will store in the project library folder

If you install Cinema 11.5 newly, please make sure the FBX 6 exporter is configured correctly. These settings are working fine for me:

  • check Export Animations
  • Export Materials and Textures
  • check Export as FBX 5.0 compatible file
  • uncheck Export as Textfile
  • check Export Normals (please note that due to a bug in the converter, normals will not be imported correctly into Unity, you have to generate them with Unity using the ModellImportSettings)
  • uncheck both texture options

It looks like this for me (I am running a German version of the program)