Hi all,
as promised here is version 0.04 of the Octane exporter for CINEMA 4D. Polygon selections are now considered during export and the objects get split accordingly. I have also fixed a few bugs and tried to improve the export of the specular channel, which was way too strong in Octane. I haven't touched the export of the reflection channel though.
The plugin still only supports UVW texture mapping, but I have added a framework to easily add other texture mappings and converting them on-the-fly to UVWs. A first sign of that new stuff is the application of texture scale and offset of the texture tags to the UVW coordinates, i.e. texture scale and offset are now exported by modifying the UVW coordinates.
One other thing: As described in the last release, material names are extremely important if you are using the relink mechanism of Octane. It's essential to have unique material names. Until now, the plugin only added a "_<number>" to every duplicate of the material name in the exported material library (MTL). This is fine as long as you don't insert another material with the same name, which would then change all materials that come after the new material. To reduce that problem, the plugin now renames materials in the C4D scene to unique names, if they are not unique. This way only one material might be affected and not a long list, if you insert a new one with the same name. I'm still trying to find a persistent unique identifier that can be used to identify a material even after reloading the scene.
These are the PC builds of the plugin:
CINEMA 4D R9.6 (32/64bit):
CINEMA 4D R10.1 - 11.0 (32/64bit):
CINEMA 4D R11.5 (32/64bit):
These are the Mac builds of the plugin:
CINEMA 4D R9.6 (32bit):
CINEMA 4D R10.1 - 10.5 (32bit):
CINEMA 4D R11.0 (32/64bit):
CINEMA 4D R11.5 (32/64bit):
Cheers and happy rendering,
Marcus
Octane exporter for C4D version 0.04
Moderators: ChrisHekman, aoktar
Thank you very very much dude !
Win7 x64 - Intel Core i7 920 (2.67 GHz) - Geforce GTX 285 - 12Go RAM
www.wipix.fr
www.wipix.fr
works fine
Camera object is correctly exported by "render" action (Octane lanching),
but is not correctly exported by "Export OBJ/MLT only" action (and imported by mesh node in Octane).
Could we hope new release with animation export function, before the end of the current contest ?
Best regards,
but is not correctly exported by "Export OBJ/MLT only" action (and imported by mesh node in Octane).
Could we hope new release with animation export function, before the end of the current contest ?
Best regards,
Win7 x64 - Intel Core i7 920 (2.67 GHz) - Geforce GTX 285 - 12Go RAM
www.wipix.fr
www.wipix.fr
Thanks!really thanks
C4D + ZBrush User
Use AMD Phenom 9850, GeForce 8600 256MB, 8GB
Use AMD Phenom 9850, GeForce 8600 256MB, 8GB
OBJ/MTL doesn't store any camera information -> can't be exported this way.Vincent wrote:Camera object is correctly exported by "render" action (Octane lanching),
but is not correctly exported by "Export OBJ/MLT only" action (and imported by mesh node in Octane).
I will have a look at it on the weekend. If it's not complicated (what I hope), there should be animation support this weekend or beginning of the next week.Could we hope new release with animation export function, before the end of the current contest ?
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra