When I export an .fbx model file(or any other) from cinema4d with one material(with a texture), it does not export the texture even though I did set it to do that.
Same when I use unity to automagically convert a .c4d to .fbx.
How do I fix this? And if you need more info, please ask!
cinema4d verison:11.514
Not that it is a huge deal, it just means I have to put the textures in unity manually, but if I can fix it, it would be nice :).
Are you exporting textures in the C4D Illuminance channel by any chance? They won’t export into Unity if they are.
Make sure you have the latest FBX exporter 2010.2 installed for via online updater in C4D. The textures do come in to Unity in place.
I updated and exported and it still has no textures :(.
I usually have no probelm, however I exported a scene yesterday and of 8 materials with textures in C4D, Unity only imported 1 of the materials.
I reopened the fbx inside of C4D that I had previously exported and all the materials were present, so it must be on the Unity side of things. Really annoying as it is time consuming to go through and recreate the materials inside of Unity. This was on Unity PC. I will try with the Mac build.
Maybe it will be fixed with unity3 :).
The problem also exists in U3 beta 3.
I just tried exporting from C4D as FBX 6.0 and it works as it used to. One material created in Unity for each material that exists in C4D.
Tried FBX 2010.2 and it only imports one material still.
EDIT: I will send a bug report to UT.
This sounds like a bug in Cinema4D FBX2010 exporter. Unity 3.0 uses FBX2010 plugin as a default when exporting from Cinema4D.
Let me know the case number and will follow it up with Maxon.
Case 369349 thanks Paulius.
I am using C4D build r11.532
I don’t want to post a bug that has been posted already, soooo, just make sure to keep this thread updated :).
Sure, no problem.
I’m quite busy with other higher priority bugs, but I will try to address it before 3.0 is out.
Thanks :).
Hi
MAXON people have confirmed that it’s a bug on Cinema4D side and they have made a fix already, but I didn’t get an answer on when the fix will be available to the users.
Regards,
Paulius
Hey thanks man, great news.
Thank you!
I too am plagued by this bug. Is there any alternative workflow until Maxon gets the update out - I’d rather not recreate all the materials by hand?
Thanks in advance!
I just got a reply from Maxon support:
“there was a bug exporting materials, but this has been already fixed in R11.532 .
If there is still a problem it is something new or not yet known to us.
Btw. R11.532 was the last version of R11, we have already released R12, so there
will be no more updates for R11.5 available.”
So, either there is a problem on the Unity side, or their fix mentioned above is unrelated to the problem or was unsuccesful. I am worried by thier tone though. It seems to imply that if there is another bug in 11.5 you would have to upgrade to R12 to get access to a fix. Shady customer service to say the least.
(Edit: logged a bug with the Case ID 374377)
Hey Foxis,
I reported the bug with 11.532 originally. Maxon have acknowledged it is a bug.
I doubt a update to r11.5 will be forthcoming since Maxon seem bent on getting everyone on to r12 even though it apparently has major issues also getting to Unity.
That’s weird. As I wrote, to me they claimed there was no current problem they knew about.
Regarding R12 I am becoming increasingly annoyed with Maxon’s strategy of leaving bug fixes until paid upgrades. I don’t need the majority of the functionality in R12, but I need the fixes. Do they seriously expect me to pay roughly Euro 600 for fixing something that was broke to begin with? Grr.
So, what are you (and others) planning to do? Are there viable alternatives? Does Maya handle this better?
Cheers,
Dan
As I understand if you’re doing static models you could just export to FBX6 manually - it should export materials better.