sorry if the question seems a little bit thoughtless. In our studio we use deadline for our network renderings from cinema4D and aftereffects.
Now, we want to buy the Octane Cinema4D Plugin and the Octane Standalone Version, to use the Octane Cinema4D Plugin inside Cinema4D as our Renderengine. Is it still possible for Deadline to render these Files from cinema4D now with Octane as the RenderEngine? Could there be a problem? Or is this nothing, Deadline cares about?
I can´t test this out, because the Demoversion of the Octane cinema4D Plugin comes without a saving option.
Hi
I think if Octane uses the native C4D render output like vrayc4d does, it shouldn’t be a problem. But i don’t konw anything about Octane so don’t take my word for it
The way that Deadline works, sending a command line instruction to C4D, it should work assuming Octane can work in such and environment, and the scene file can contain the information on the renderer. I would verify with the makers of Octane that their renderer will work for a command line C4D render with no UI.
Hi,
im sorry that i have to revive that threat, but did you find a way to get Octane working?
For me it’s the other way round, we are producing with octane in CInema 4D and are now looking for a render manager like deadline.
I set deadline up, so that it’s working just fine with “normal” C4D Advanced Renderer.
However i can’t render Octane Cinema 4D scenes though.
Any tips or deocumentiation about the workflow for that?
I think the last we’d seen on this, the customer had to check with the devs for octane, though I see no follow up reports. Can you provide logs of what you’re seeing?
Looking over the logs, I am seeing very prominently the following:
2015-01-15 16:48:23: 0: STDOUT: 2015-01-15 16:48:23.160 CINEMA 4D[43123:653436] setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.
2015-01-15 16:48:23: 0: STDOUT: Error: OS error loading plugin anima.dylib. Could not load dll. Error code: dlopen(/Applications/MAXON/CINEMA 4D R16/plugins/anima/anima.dylib, 6): Library not loaded: @rpath/libAnimaCore.dylib
2015-01-15 16:48:23: 0: STDOUT: Referenced from: /Applications/MAXON/CINEMA 4D R16/plugins/anima/anima.dylib
2015-01-15 16:48:23: 0: STDOUT: Reason: image not found. (file:///Applications/MAXON/CINEMA 4D R16/plugins/anima/anima.dylib) [osx_dll.cpp(76)]
2015-01-15 16:48:23: 0: STDOUT: Error: plugin (liboctane.dylib) doesn’t return c4d_main ptr. symbol ‘c4d_main’ is missing. error: dlsym(0x7f862b695290, c4d_main): symbol not found [osx_dll.cpp(109)]
2015-01-15 16:48:23: 0: STDOUT: Error: plugin (libcudart.6.5.dylib) doesn’t return c4d_main ptr. symbol ‘c4d_main’ is missing. error: dlsym(0x7f8634228890, c4d_main): symbol not found [osx_dll.cpp(109)]
2015-01-15 16:48:23: 0: STDOUT: Error: plugin (libiomp5.dylib) doesn’t return c4d_main ptr. symbol ‘c4d_main’ is missing. error: dlsym(0x7f8634228890, c4d_main): symbol not found [osx_dll.cpp(109)]
When we analyze the log here, it looks like there is an issue when there is no monitor present, which causes it to die pretty badly. I would check with the folks at Octane and see if this is something they can rule out when a network, command line render is happening.