Cinema4D Comand line R23, Octane 2020 and Deadline - Help

Hi there,

We are trying to install Cinema4D command line R23, Octane 2020 plugin and use it with Deadline.
But having no luck at all.

Could someone confirm if these latest versions of the software and plugin are supported?

Many thanks

Doesnā€™t show support for 2020 but likely should work

Which version of Deadline are you running? and which OS? and what is the issue? can you post the logs or error messages?

Weā€™re having trouble with both methods of rendering C4D R23 + Octane 2020.2.1. If we attempt to submit to Deadline directly from C4D (using batch mode or non-batch mode), it seems like C4D commandline is struggling to load the Octane plugins. However, we get the same error if we simply run the test job using commandline.exe (without Deadline) - so I donā€™t think this is a Deadline problem.

To work around this, we tried to export the C4D project as .orbx, so that we could submit it as an Octane job from Deadline Monitor. However, this does not help because Octane 2020 does not appear as an option in the submission window under Octane Options/version (2019 is the latest). This predictably results in the error:
Error: FailRenderException : Octane render executable was not found in the comma-separated list
We are using Deadline Client Version: 10.1.13.1 Release (4c7391f76).
I did attempt to modify \DeadlineRepository10\plugins\Octane\Octane.param , adding an entry for 2020. This did at least allow 2020 exe path options to show up in Monitorā€™s Configure Plugins\Octane section, but it did not change the submission window.

Are there additional steps required to force Deadline to correctly locate the Octane 2020 executable, or is it just unsupported with this method?

Two things to know:

Cinema 4D R23 had a bug (not on the Deadline side) where the command line would not properly load plugins. You can read about the solution here: https://support.maxon.net/kb/faq.php?id=115

Deadline 10.1.14 fixed the above by forcing the loading of the plugins to work around the MAXON bug. You can read about it here: Release History ā€” Deadline 10.1.23.6 documentation

The default C4D plugin folder is automatically added to the search paths when rendering with Cinema 4D R23, which works around a known issue in R23.

Since you are not using 10.1.14 but 10.1.13, you must perform the manual fix as explained in the first link.

Regarding the standalone rendering, you must add the version 2020 to two locations:

  • The .param file you modified already,
  • The submitter that is sending the Job with the .orbx file.

The Job gets a Version value in the metadata that tells the integration plugin what version to look for in the executable paths. The .options file contains a label control to show it, but does not let you edit it. In theory, you could switch it to an editable text field so you could type in any version you want, but it is better to include the version on submission.

The Monitor submitter located under \\DeadlineRepository\scripts\Submission\OctaneSubmission.py
contains a versions variable listing supported versions in line 185:

versions = ("1", "2", "3", "4", "2018", "2019")

You should add ā€œ2020ā€ there to make it an option if submitting through the Monitor.

2 Likes

Hey,
iā€™ve installed Octane 2020.2.4 Standalone with the newest Deadline, as described above and itā€™s rendering quite well until I check the Save-All-Enabled-Passes on submission.

Help - please :smiley: !

So in Monitor - get this task error ( in debug mode ) :

Job_2021-08-27_20-13-18_61292b3e6bded9241cf130e7.zip (2.9 KB)

And in Worker log :
full log:
Form_streamedlog.zip (7.8 KB)

interesting part >

DEBUG: ManagedProcess.HandleStdoutLine: parsing stdout: Started logging on 27.08.21 20:12:51
2021-08-27 20:13:14: 0: STDOUT: Started logging on 27.08.21 20:12:51
2021-08-27 20:13:14: 0: DEBUG: ManagedProcess.HandleStdoutLine: parsing stdout: OctaneRender Enterprise 2020.2.4 (10021600)
2021-08-27 20:13:14: 0: STDOUT: OctaneRender Enterprise 2020.2.4 (10021600)
2021-08-27 20:13:14: 0: DEBUG: ManagedProcess.HandleStdoutLine: parsing stdout: [string ā€œoctane_render_utils_luaā€]:200: bad argument #3 to ā€˜gsubā€™ (string/function/table expected) (line: 200)
2021-08-27 20:13:14: 0: STDOUT: [string ā€œoctane_render_utils_luaā€]:200: bad argument #3 to ā€˜gsubā€™ (string/function/table expected) (line: 200)
2021-08-27 20:13:14: 0: DEBUG: ManagedProcess.HandleStdoutLine: parsing stdout: Stopped logging on 27.08.21 20:13:14
2021-08-27 20:13:14: 0: STDOUT: Stopped logging on 27.08.21 20:13:14
2021-08-27 20:13:14: 0: DEBUG: ManagedProcess.Execute: m_process.IsRunning(): False m_process.IsStdoutAvailable(): False
2021-08-27 20:13:14: 0: DEBUG: ManagedProcess.Execute: child process has exited
2021-08-27 20:13:14: 0: DEBUG: PopupHandler.CheckForPopups: Getting popup handles
2021-08-27 20:13:14: 0: DEBUG: PopupHandler.CheckForPopups: Got 0 handles
2021-08-27 20:13:14: 0: DEBUG: PopupHandler.CheckForPopups: Returning
2021-08-27 20:13:14: 0: DEBUG: ManagedProcess.Execute: checking exit code
2021-08-27 20:13:14: 0: INFO: Process exit code: 100
2021-08-27 20:13:14: 0: DEBUG: ManagedProcess.Execute: calling CheckExitCode()
2021-08-27 20:13:14: 0: DEBUG: ManagedProcess.Execute: returning
2021-08-27 20:13:14: 0: Done executing plugin command of type ā€˜Render Taskā€™
2021-08-27 20:13:14: 0: Executing plugin command of type ā€˜End Jobā€™
2021-08-27 20:13:14: 0: DEBUG: EndJob: called
2021-08-27 20:13:14: 0: DEBUG: EndJob: returning
2021-08-27 20:13:14: 0: Done executing plugin command of type ā€˜End Jobā€™
2021-08-27 20:13:18: Scheduler Thread - Render Thread 0 threw a major error:
2021-08-27 20:13:18: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2021-08-27 20:13:18: Exception Details
2021-08-27 20:13:18: RenderPluginException ā€“ Error: Renderer returned non-zero error code, 100. Check the log for more information.
2021-08-27 20:13:18: at Deadline.Plugins.PluginWrapper.RenderTasks(Task task, String& outMessage, AbortLevel& abortLevel)
2021-08-27 20:13:18: RenderPluginException.Cause: JobError (2)
2021-08-27 20:13:18: RenderPluginException.Level: Major (1)
2021-08-27 20:13:18: RenderPluginException.HasSlaveLog: True
2021-08-27 20:13:18: RenderPluginException.SlaveLogFileName: C:\ProgramData\Thinkbox\Deadline10\logs\deadlineslave_renderthread_0-PANFILOV-TV-0000.log
2021-08-27 20:13:18: Exception.TargetSite: Deadline.Slaves.Messaging.PluginResponseMemento d(Deadline.Net.DeadlineMessage, System.Threading.CancellationToken)
2021-08-27 20:13:18: Exception.Data: ( )
2021-08-27 20:13:18: Exception.Source: deadline
2021-08-27 20:13:18: Exception.HResult: -2146233088
2021-08-27 20:13:18: Exception.StackTrace:
2021-08-27 20:13:18: at Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage bfi, CancellationToken bfj)
2021-08-27 20:13:18: at Deadline.Plugins.SandboxedPlugin.RenderTask(Task task, CancellationToken cancellationToken)
2021-08-27 20:13:18: at Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter ajm, CancellationToken ajn)
2021-08-27 20:13:18: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

In this case we donā€™t need to have verbose logging on the Octane plugin enabled, so Iā€™d turn that off as itā€™s just making this extra chatty. :slight_smile:

I havenā€™t worked with a lot of Octane failures myself, so this is going to be based on limited Octane knowledge. Line 200 of our DeadlineOctane4.lua isnā€™t calling gsub so that line 200 referenced in the error must be from the ā€œoctane_render_utils_luaā€ file that ships with Octane.

Iā€™d have to re-produce it so I can fiddle with settings - it sounds like weā€™re giving Octane a bad parameter but itā€™s not clear which as we create a octane_lua_args.txt file and stuff most of the parameters in there.

Would you be able to create a ticket at https://awsthinkbox.zendesk.com with a job archive and a scene file we could use to reproduce the issue? You can create a job archive by right clicking on the job in the Monitor after itā€™s done rendering. Reference this thread in the ticket so whoever gets the ticket get check here for any extra context.