I’m testing a 30 days fully working demo version of Cinema 4D 11.5. The 11.5 version has a new FBX-Export Plugin (version 2010). What means >multi UV mesh support! We all have waited a long time…
But Unity3D has got a problem with the new Cinema 4D 11.5.
Unity3D guys always said by any interchange problems between Unity3D and Cinema4D >> THIS IS AN ISSUE OF THE FBX EXPORT PLUGIN FROM MAXON CINEMA 4D!!!
But as you can see in the screenshot: Unity3D is installing old versions of an own FBX export PlugIn into the PlugIn folder of Cinema 4D 11…
I copied that PlugIn folder from C4D11 to CD11.5 manually, because Unity3D promts first the error of an installation faild.
But without success > Importing C4D11.5 files into Unity3D is not working at all.
Can you already telling us, when Unity3D is working together with Cinema 4D 11.5?
Could you log this in our issue tracking system by doing Help->Report a problem? Please post your casenumber here as well. In the meantime, does your editor logfile give any more info on what exactly has gone wrong?
cause
unlike prior versions of Cinema4D the new installer messes up the rights of the installed files, only the Cinema 4D R11.5 root folder in the Applications (Applications/MAXON/Cinema 4D R11.5) directory has the neccessary rights to be accessible. Subfolders only have limited rights for write access. When Unity tries to install the export plugin it cant write the files so it shows the “Plugin installation failed” message.
solution
You simply need to select the Cinema 4d root folder and apply the rights of the root folder to all sub-folders. Easy as pie. Make sure Cinema is not running while you are doing that. After you have done that, just import any C4D file so that Unity will install the export plugin. after that you are good to go.
make sure the FBX export options in C4D are properly set up. You need to use FBX 6 without the Text-based option checked and disable embedded textures.
Try to reinstall Cinema4D if you messed around trying to install the plugin manually.
Actually it’s the OS. The application/program folders from Leopard onwards on OSX and from Vista onwards in windows are protected areas (this is for all applications, not just C4D). It’s not the installer messing up the rights, it’s just how the OS itself works.
Basically only the application and it’s installer is meant to be allowed direct access to modify it’s own folder structure, so although plugins are still allowed to be placed in the plugins folder (though usually you need to give permision to do so) they cannot modify data within the folder themselves, only outside of the apps folder as a whole, e.g. the user’s documents folder or the like. It may end up that it makes more sense to install the plugins to the user preferences folder instead (you can find this location easily either from the API or as a user by going to Edit->Preferences->Common and looking at the bottom of the page), though the downside (or upside depending on your needs) is that they then become local to that user, either way if they have any intermediate data it needs to be stored outside of the applications/programs folders on your machine.
I have tried everything I’ve read in this thread to link to c4d 11.5 files. I still get a “converter plugin installation failed” error.
What could I be missing?
-I changed C$D to run in 32 bit
-I manually installed the plug in the plug-ins director
-I also tried installing the plug-in files in the preferences/plugins folder
-I quit,re-opened, etc.
FBX has worked fine. Should I just use FBX and ignore the issue?
After modifying the permissions recursively on Cinema’s application directory, Unity was able to install the Cinema plugin for me - but now Unity chokes with a “Cinema 4D couldn’t convert the .C4D file to an fbx file” error on even the simplest files.
Does anyone have Cinema 4D 11.5 working with Unity Pro 2.6.1?
I have it up and running and now problems whatsoever…
I never had any problems besides the 32bit mode issue…
do not install the plugin manually, if conversion failed, shut down unity, shut down cinema, remove the unity plugin stuff from all directories in cinema and apply rights to the cinema application folder as mentioned above, then relaunch unity and hit Reimport on a C4d-File asset… the rest should work automatically…
if you get problems at this point, check the export settings for FBX 6 in cinema, make sure you export as a non-ascii file and without embedded textures…
of course, that is what i mentioned earlier on… but where is the harm in that? advantages of the 64bit version only kick in when doing some really have scene editing or rendering with a lot of objects/polys/etc on it, and i reckon that kind of data will not be suitable for direct unity import anyways…
of course being able to run 64bit would be better, but so far the advantages of being able to edit c4d files and have them automatically updated in unity far outway the downside of running c4d in 32bit mode.
besides, I think if someone would look into it, there would surely be a way to launch cinema one way or the other with a terminal command or something like that… having it launch in 32bit when started by unity, but also have a special shortcut to launch in 64bit…
What did you do to make it work? I’m completely fed up by this f**** limitation.
I tried all the things mentioned in this thread and no success.
I just need to put a .c4d file in an asset folder to make Unity stop working (spinning beach ball).
C4D 11.5 is set to run in 32bits, I’ve set the authorizations as suggested, and it does nothing.
The problem occurs both with Unity 2.6 and Unity 3.
What makes me crazy is that the tech support knows the problem for more than a year and they did nothing…
