How to create an Octane file from Cinema 4d to be submitted by Deadline

Deadline
1

I’m having an issue when submitting Octane file (.ocs or .orbx) from Deadline. I see the render going through but not results on the output folder.

Log files:
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] Flag Type Value Prefix Description
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] ------------------------- ------- ---------- ------------ --------------------------------------------------------------------------------
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] daemon release 1 “daemon” Enables general logging of the slave daemon.
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] daemonDetail release 1 “daemon” Enables detailed logging of the slave daemon.
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] logAppendToFile release 1 “” If enabled, logging will be to the already existing log file appended
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] logFlags release 1 “” If enabled, all log flags will be dumped during startup
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] logFlushTime release 100 “” The time (ms) after which the log is flushed. If set to 0, the timer based flush will be disabled.
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] logForceFlush release 0 “” If enabled, every logged line will be flushed
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] logJuce release 0 “JUCE” If enabled, JUCE logging will go through the logging framework of Octane
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] logPrefix release 1 “” If enabled, each log line will have a prefix
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] logTime release 1 “” If enabled, each log line will have a timestamp
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] logToDebugConsole release 0 “” If enabled, logging will go to the debug console (Windows only)
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] logToFile release 1 “” If enabled, logging will go to a log file
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] logToStdout release 1 “” If enabled, logging will go to standard out (when set to 1) or standard error (when set to 2)
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323]
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] daemon : Command line:
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] daemon : -q --script C:\Users\d1motion\AppData\Local\Thinkbox\Deadline10\slave\D1-RN-TEST01\plugins\5bec7ad221562d06a876eae3\DeadlineOctane.lua -a %F.%e -a “R:\C4D Renders” -a png16 -a 1 -a 1 -a Square_Cream_3D_v2 --stop-after-script -t Square_Cream_3D_v2 “O:\MOTION_SOFTWARE\RF Admin\Test\Projects\Minute_Frame_Test\Minute_Frame_Test.ocs”
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] ERROR : unknown command line argument ‘-q’
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] ERROR :
2018-11-14 11:43:27: 0: STDOUT: command line syntax:
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] ERROR : octane_slave_daemon.exe --port --slave “” [–alias “”] [–gpus “”] [–out-of-core [k|K|m|M|g|G][,[k|K|m|M|g|G]]
2018-11-14 11:43:27: 0: STDOUT: [19:43:27.323] ERROR :
2018-11-14 11:43:27: 0: STDOUT: (k/K = KiloByte, m/M = MegaByte, g/G = GigaByte)

2

It definitely looks like we’re either Octane is too new or Deadline is too old"

What version of Deadline are you using here? Same question for Octane. Essentially, we’re not talking with Octane the way it’s expecting us to.

3

Actually, we got it figured out. On the plugin menu, make sure that the octanec_cli.exe and octance.exe is loaded to the executable path.

Octane version 3.08.3 and Deadline version 10.0.21.5

4

Ah! Of course that’ll do it. Good job there.

For those who may not know, you can configure application search paths and Deadline opens whatever you tell it to, even if it’s not the right application. It seems counter intuitive, but makes loading custom pipelines possible.