Hello there. We are rendering with C4D 2024.3.1 and Octane 2023.1.2. Unfortunately, a simple test render is failing when rendering via Deadline.
The same render command run within a command line on the local machine is successful. I suspect that there is some non-zero exit code or some such coming from Octane.
The same simple test scene renders successfully through Deadline when using an engine other than Octane (ex: Redshift or Standard).
Here are lines from the worker log where the render fails:
2024-02-26 22:29:37: 0: STDOUT: Running Script: C:\ProgramData\Thinkbox\Deadline10\workers\ImageFluxWS08\jobsData\65dd81248f20e5fa62130b1c\thread0_templUGDj0\c4d_Batch_Script.py
2024-02-26 22:29:37: 0: STDOUT: (null)PendingDeprecationWarning: Since 2024.0 BaseList2D.GetData is deprecated and will be removed in 2025.0. Use BaseList2D.GetDataInstance instead.
2024-02-26 22:29:37: 0: STDOUT: Rendering frame 0 at <Mon Feb 26 22:29:37 2024>
2024-02-26 22:29:37: 0: STDOUT: init OCIO colorspace…
2024-02-26 22:29:37: 0: STDOUT:
2024-02-26 22:29:37: 0: STDOUT: FRAME:0 fps:30
2024-02-26 22:29:40: 0: STDOUT: Error: application crashed
2024-02-26 22:29:40: 0: STDOUT: C4DUnhandledExceptionFilter: writing exception info
2024-02-26 22:29:40: 0: STDOUT: C4DUnhandledExceptionFilter: writing call stacks
2024-02-26 22:29:41: 0: WARNING: Monitored managed process Cinema4DProcess is no longer running
2024-02-26 22:29:41: 0: Done executing plugin command of type ‘Render Task’
2024-02-26 22:29:41: 0: Executing plugin command of type ‘End Job’
2024-02-26 22:29:41: 0: INFO: End Job called - shutting down Cinema 4D Batch plugin
2024-02-26 22:29:41: 0: WARNING: Cinema 4D.exe was shut down before the proper shut down sequence
2024-02-26 22:29:41: 0: INFO: The process took 0ms to exit.
2024-02-26 22:29:41: 0: Done executing plugin command of type ‘End Job’
2024-02-26 22:29:45: Scheduler Thread - Render Thread 0 threw a major error:
2024-02-26 22:29:45: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2024-02-26 22:29:45: Exception Details
2024-02-26 22:29:45: RenderPluginException – Error: RenderTask: Unexpected exception (Monitored managed process “Cinema4DProcess” has exited or been terminated.)
2024-02-26 22:29:45: at Deadline.Plugins.PluginWrapper.RenderTasks(Task task, String& outMessage, AbortLevel& abortLevel)
2024-02-26 22:29:45: RenderPluginException.Cause: JobError (2)
2024-02-26 22:29:45: RenderPluginException.Level: Major (1)
2024-02-26 22:29:45: RenderPluginException.HasSlaveLog: True
2024-02-26 22:29:45: RenderPluginException.SlaveLogFileName: C:\ProgramData\Thinkbox\Deadline10\logs\deadlineslave_renderthread_0-ImageFluxWS08-0000.log
2024-02-26 22:29:45: Exception.TargetSite: Deadline.Slaves.Messaging.PluginResponseMemento d(Deadline.Net.DeadlineMessage, System.Threading.CancellationToken)
2024-02-26 22:29:45: Exception.Data: ( )
2024-02-26 22:29:45: Exception.Source: deadline
2024-02-26 22:29:45: Exception.HResult: -2146233088
2024-02-26 22:29:45: Exception.StackTrace:
2024-02-26 22:29:45: at Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage bgu, CancellationToken bgv)
2024-02-26 22:29:45: at Deadline.Plugins.SandboxedPlugin.RenderTask(Task task, CancellationToken cancellationToken)
2024-02-26 22:29:45: at Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter ajz, CancellationToken aka)
2024-02-26 22:29:45: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Any advice would be greatly appreciated. Many large frames to render…
It looks like Cinema 4D exits before Deadline asked it to exit hence the error. To troubleshoot further I think you can jump on the render node open up “Windows Event Viewer” and look for Cinema 4D under (left pane) Windows Logs> Application. In here you can search with the name Cinema by using search from the right pane. Share what you find.
Check to see why and how it exited. It might be some corrupted plugin (just a guess).
Does this happen on all the frames of that heavy job?
Does this happen on all the render nodes or just some and is there a pattern? say all machines which have new Cinema installation present this error?
Also did you test with Cinema 4D non batch (command line) plugin on the same render node which presents this error in batch mode? If not please render with Cinema Non Batch plugin on the same render node then follow here to isolate the issue from Deadline if you are able to reproduce.
Thanks for the response. I’ll test via the Windows Event Viewer this morning.
To answer your questions…
This happens on all frames of this job, which is not heavy but a very simple test scene (just a cube).
It happens on all render nodes running the same versions of C4D, Octane and Deadline.
No plugins are installed aside from Octane and Redshift.
Regarding non-batch, there is a bug as of C4D 2024 wherein ALL renders fail. This is true regardless of render engine (Standard, Redshift, Octane). In that case the error is:
at Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage bgu, CancellationToken bgv)
at Deadline.Plugins.SandboxedPlugin.RenderTask(Task task, CancellationToken cancellationToken)
at Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter ajz, CancellationToken aka)
This might have been a silly issue with drive mapping / pathing. The simple test file was at the root of a mapped network drive. When I submit with “Submit Cinema 4D Scene File” enabled, these errors go away.
Likewise, when I put the scene file one directory deeper on the mapped drive the errors go away.
So it appears to have been some issue parsing the path to the scene file when it’s sitting at the root of the mapped network drive. Does that sound reasonable or am I going crazy?
I’m getting this on 2024.3.2 and it has nothing to do with mapped drives. If I back down a version it works fine. It still allows the render to “complete” but it spits out empty frames.
Are you able to reproduce the issue if you submit the same job with Cinema 4D command line plugin? To do that uncheck the option “Use Batch Plugin” in the submitter and submit the same job.