Issues setting up Octane Render on Deadline

Deadline
1

I’m currently trying to set up Octane for our renderfarm that is running with Thinkbox Deadline 10.1 at the moment.

First thing I noticed is, the plugin-paths are preset up only up to Octane 2019, I just changed the path to the current version 2022 to get the submission working. Will there be an update on that soon?

With this settings the worker did not not start throwing following errors:
Anyway, the plugin is found now but the worker cannot start the rendering, log says:

2023-04-13 20:44:44: 0: STDOUT: [string “octane_render_utils_lua”]:200: bad argument #3 to ‘gsub’ (string/function/table expected) (line: 200)
2023-04-13 20:44:44: 0: STDOUT: Stopped logging on 13.04.23 20:44:44
2023-04-13 20:44:45: 0: INFO: Process exit code: 100

Seeking help in the OTOY forum they pointed me to a custom lua script to solve this issue, apparently the built in submission script from the repository does pass wrong arguments. OTOY Forums • View topic - Issues with Octane setup on Deadline Farm

Anyway, with this repaired lua script I managed to get the worker rendering but it fails to save the result somehow …

2023-04-15 13:56:27: 0: STDOUT: Image loading: PNG: FreeImage_SaveU: failed to open output file
2023-04-15 13:56:27: 0: STDOUT: [string “DeadlineOctane4.lua”]:431: failed to save image (line: 431)
2023-04-15 13:56:27: 0: STDOUT: Stopped logging on 15.04.23 13:56:27

Does anyone know how to solve this issue or how to get Octane Jobs rendering with Deadline in general?

2

Thanks for reaching out, there is an internal ticket cut to our engineering team to add support for Octane’s latest versions up to 2022 I have added this forums post as a reference there. I cannot share an ETA when will the support be added.

Thanks for sharing the link to forums thread. The API to octane has been changed which is why Deadline needs to add support for this new API too. I have compared both the files and found out that the updated .lua script is very different from what we have already. So, I cannot make quick fixes in this case. We need to have to wait for the Octane 2022 support.

3

Thank you for looking into this!

Is this a thing that would be solved by AWS premium support too?

4

We would also very much appreciate support for Octane Standalone 2021+ with regard to AOV etc

5

Hello @jxrgen_vast
I do not think they can add support for new versions.
@GM1
Sure I will add your request to our internal ticket.

6

Hi there,

thanks for your support so far @zainali

Finally I managed to get rid of the “PNG: FreeImage_SaveU” bug somehow. I was some weeks off and it magically disappeared in the meanwhile, don’t know why, hope it doesn’t come back.

But moving on I ran into more issues from this point:

  1. when I submit an octane job via the monitor and activate save multipass exr it fails this way:
    2023-05-05 11:35:13: 0: STDOUT: OctaneRender Studio+ 2022.1.1 (12000102)
    2023-05-05 11:35:13: 0: STDOUT: [string “DeadlineOctane4.lua”]:936: bad argument #4 to ‘saveRenderPassesMultiExr’ (number expected, got boolean) (line: 936)

  2. I also tried to submit a job via the c4d sumisson script (tried C4D S26 and 2023), but when activated “Submit Export Job” + “Export Type Octane” the script gets stuck with the click on the “Submit” button. That could be also a problem on our side but I don’t know how to debug the issue, any hints on that?