Page 9 of 13

Re: Octane exporter for C4D version 0.12b (current)

Posted: Fri Jun 13, 2014 12:27 pm
by ingostan
Hi Again
Is a new exporter in work?

Re: Octane exporter for C4D version 0.12b (current)

Posted: Sat Aug 23, 2014 5:40 pm
by Alul
abstrax wrote:
shibinss wrote:how about c4d R15 version ?? possible ?
I don't have a r15 unfortunately, but does the R12 build version not work in R15? I can make a R14 build, but I don't know if that helps.
Hi. Exporter is not working in R15 for me.

Can you please check this out if I did something wrong. I'm in the middle of XSI>C4D switch so i can make mistakes

Re: Octane exporter for C4D version 0.12b (current)

Posted: Mon Sep 22, 2014 3:22 pm
by TonyBoy
How does Exporter 12B (for 11.5 or 12) work for Standalone 2.0?

Re: Octane exporter for C4D version 0.12b (current)

Posted: Fri Oct 03, 2014 11:51 pm
by b1siu
Hi ;)
Is Octane Exporter 12-14 works with version R16?

Re: Octane exporter for C4D version 0.12b (current)

Posted: Wed Oct 08, 2014 8:28 pm
by augdalmo
yes it works fine.
Nevertheless I have encountered the same limitation as in R15, the exported material will lose the link of the texture so you must recreate the material in Standalone, very boring and time consuming if the scene has several materials. I hope that Octane Render Team will correct this problem soon

Re: Octane exporter for C4D version 0.12b (current)

Posted: Wed Oct 08, 2014 8:33 pm
by abstrax
augdalmo wrote:yes it works fine.
Nevertheless I have encountered the same limitation as in R15, the exported material will lose the link of the texture so you must recreate the material in Standalone, very boring and time consuming if the scene has several materials. I hope that Octane Render Team will correct this problem soon
What exactly is the problem?

Just for your information: I didn't have time to work on the plugin for ages and if you want the real deal, you should use Ahmet's Octane for C4D plugin (http://render.otoy.com/forum/viewtopic.php?f=30&t=42257 and http://render.otoy.com/forum/viewtopic.php?f=30&t=42607).

Re: Octane exporter for C4D version 0.12b (current)

Posted: Sun Oct 12, 2014 11:53 am
by augdalmo
I refer to Octane Export plug in not to Octane render plugin for C4D.
As you create a material in C4D with the plugin of Octane Render for C4d and export to render on Octane Standalone with the OctaneExport plugin the link to the texture images of the materials will be lost, as you can see on the screen shots attached.
"Collect all texture images" doesn't works.
material output on Standalone
material output on Standalone

Re: Octane exporter for C4D version 0.12b (current)

Posted: Sun Oct 12, 2014 8:45 pm
by abstrax
augdalmo wrote:I refer to Octane Export plug in not to Octane render plugin for C4D.
As you create a material in C4D with the plugin of Octane Render for C4d and export to render on Octane Standalone with the OctaneExport plugin the link to the texture images of the materials will be lost, as you can see on the screen shots attached.
"Collect all texture images" doesn't works.
Yes it works but only with very simple materials and only when they are the standard C4D materials. That's mostly because OBJ/MTL doesn't allow any fancy materials and because the materials of the C4D Octane plugin are not documented and subject to change (and at the time I wrote the export plugin the Octance for C4D plugin didn't even exist).

But since you are already using the C4D plugin you can use the plugin to export the scene to Octane Standalone using the Octane Dialog and selecting File -> Save Ocs.

Re: Octane exporter for C4D version 0.12b (current)

Posted: Tue Oct 14, 2014 2:27 pm
by augdalmo
many thanks for your support!

Re: Octane exporter for C4D version 0.12b (current)

Posted: Wed Jan 28, 2015 7:44 pm
by César
Hello,

I just see that the new Octane version support multiple UV. Will you update this exporter to manage this feature ? I know that OBJ don't support it but you spoke about some possible tricks :
Octane tries to look for data that looks like additional UV sets in Alembic files and the plugins will have the possibility to export them, too, via the Octane API, but for now it's kinda tricky to use this feature if the source geometry doesn't supply multiple UV coordinates.
I am still more confortable with the standalone. I hope that it will be still possible to use it with multiple UV.