Before I file a bug report: Anyone else noticed that import from C4D is dog-slow in Unity 3 (beta 3) ? It takes 5-10 seconds even for very simple objects to import.
By import do you mean save the C4D file into your Unity assets folder and let Unity import it as an fbx?
That has always taken 10-15 seconds for me even if it’s just a cube and I’m using 3ds max. I normally just use the fbx exporter in max instead.
I’m also using Unity 2.6 and haven’t tested the Unity 3 beta.
There is one significant change in C4D pipeline which might be affecting import of small objects: we start Cinema4D instance for export of each object - there was no other way to implement batch mode when using Cinema4D.
I noticed that when I started using C4D. However, this delay even happens if C4D is already running.
That’s because Unity has to start new instance of Cinema4D.
Ok, makes sense now.
Is there any way to avoid this delay, other than exporting FBX directly, which kind of defeats the purpose of having a C4D importer?
There is no C4D importer.
If you put C4D in, then unity will invisibly export it as FBX from Cinema4D again which is why you get the instance there in any case.
and there is away to shorten that, but I doubt you want to install C4D on a RAM drive 
Just as dreamora said it wouldn’t be any faster, because export to FBX - that’s what Unity does for you.
You can’t shorten that delay on your side, but I have several complains about Cinema4D export being slower than before, so I’ll think and/or talk to Maxon if there is any way in which I could speed it up.
Is this lag new to Unity 3?
I am a heavy Cinema 4d user, and in 2.6 it would take about 15 to 20 seconds.
In Unity 3 beta it has been taking more like 90 seconds.
And the import time is the same regardless of whether I’m doing it on my old 2.16 ghz MacBook Pro or my new 8-Core Mac Pro. It also doesn’t seem to make a difference If I’m using 32 of 64 bit C4D.
From 20 to 90 seconds is a bit too much. It all can’t be Unity fault (we switched default export plugin from fbx6 to fbx2010 too in Unity 3.0).
Could you run the following tests:
- How long does it take to start Cinema4D (starting it manually).
- Start Unity 2.6. Import single C4D file. How long does it take (the import)?
- Start Unity 3.0. Import same C4D file. How long does it take?
Thanks,
Paulius
hi Paulius,
I’m noticing the same thing.
To try that I just created a simple cube with a texture applied.
Importing that in unity 3b4 it takes about 90 seconds.
Importing the cube in unity iphone 1.7 it takes just a tenth of a second or so.
Starting c4d manually it takes 1-2 secs.
Thank you!
T!Z
Hm…this doesn’t add up:) Export time in 3.0 should be “Cinema4D startup time”+“export time”. I’ll do some more testing on that. I haven’t see such problems myself so far. Which Cinema4D version are you using?
v10.008…
I also updated it to 10.111, but timings don’t change.
I just installed the last version (cinema4d 11.53 demo version) to try with that one, but now I get the following error when unity tries to import a c4d file:
(get from the Editor log)
“”"
Cinema 4D could not be launched and perform the conversion.
Make sure that Cinema 4D is installed and the .C4D file has Cinema 4D as its ‘Open with’ application!
(Filename: /Applications/buildAgent/work/1441ce903e456852/Projects/…/Editor/Src/AssetPipeline/FBXImporter.cpp Line: 289)
“”"
Furthermore, in unity, if I double click on the c4d asset (in the project pane) or on the error in the console, cinema4d starts correctly by opening the file.
A last further information: my unity version is Unity 3b4 iPhone Basic.
Hope this additional infos could be useful
Do you get that every time? Is there anything strange about your installation: did you use any non-default options?
Yes I get this everytime.
Uhm… No any non-default options.
I will try to reinstall unity, I let you know!
Doesn’t the demo of c4d restrict exporting and saving of files?
not a registered demo… it is a 42 days full working version.
I noticed that even removing the older version, there is a problem with file association, this could probably due to the demo version, as I found here.
I’m considering to purchase 11.5 in the next weeks, so I will let you know if with a full registered version the problem disappears.
BTW, reinstalling Unity doesn’t solve the problem…
Yes, if I remember correctly you might have problems if you’re using demo version of Cinema4D. If you’re planing to purchase it later, then just export to fbx manually as a temporary workaround.
Same here. In addition to an average of 120+ seconds per object when opening a legacy project that contains c4d files, it has also become impossible to add c4d models directly to the assets folder of a new UT project (already running c4d in 32-bit mode and having dealt with the permissions issue on Macs that can arise). Trying to save a c4d object directly to assets will crash UT and on occasion cinema 4d also. This is 100% the case in betas 3 and 4 on both our Macs.
These import times were insignificant (below 5 seconds) in version 2.6. Unfortunately we cannot use older versions of UT anymore because of the registration scheme. Talk about being stuck.