
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. options file contains a label control to show it, but does not let you edit it. The Job gets a Version value in the metadata that tells the integration plugin what version to look for in the executable paths.
The submitter that is sending the Job with the. Regarding the standalone rendering, you must add the version 2020 to two locations: Since you are not using 10.1.14 but 10.1.13, you must perform the manual fix as explained in the first link. 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. You can read about it here: Release History - Deadline 10.1.14.5 documentation You can read about the solution here: Maxon Support - for Cinema 4D, BodyPaint 3D and moreĭeadline 10.1.14 fixed the above by forcing the loading of the plugins to work around the MAXON bug. 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.Īre there additional steps required to force Deadline to correctly locate the Octane 2020 executable, or is it just unsupported with this method?Ĭinema 4D R23 had a bug (not on the Deadline side) where the command line would not properly load plugins. I did attempt to modify \DeadlineRepository10\plugins\Octane\Octane.param, adding an entry for 2020. We are using Deadline Client Version: 10.1.13.1 Release (4c7391f76). This predictably results in the error:Įrror: FailRenderException : Octane render executable was not found in the comma-separated list
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). orbx, so that we could submit it as an Octane job from Deadline Monitor. To work around this, we tried to export the C4D project as. 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. 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. We’re having trouble with both methods of rendering C4D R23 + Octane 2020.2.1.