Issues with Octane setup on Deadline Farm Tweet

[jxrgen]

Hey beautiful render people,

I'm currently trying to set up Octane for our renderfarm that is currently running with Thinkbox Deadline 10.1

First thing that I noticed is, that strangly the plugin-paths are preset up only up to Octane 2019, I just changed the path to the current version 2022 to ge the submission working (see screenshot). The paths are also linked to Enterprise lic, I have a Studio+, could that be an issue?

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

Any idea what the issue is?

[BK]

Hey beautiful render people,

I'm currently trying to set up Octane for our renderfarm that is currently running with Thinkbox Deadline 10.1

First thing that I noticed is, that strangly the plugin-paths are preset up only up to Octane 2019, I just changed the path to the current version 2022 to ge the submission working (see screenshot). The paths are also linked to Enterprise lic, I have a Studio+, could that be an issue?

plugins.PNG

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

Any idea what the issue is?

Hi jxrgen,

Thanks for the post.

The Plugin path/version and the .lua script error must be updated from the AWS side.

Please replace this .lua file from the post to fix the "200 bad argument error"
viewtopic.php?p=403251#p403251


cheers

[jxrgen]

Thank you so much, I will flag this in the Thinkbox forum too!

I replaced the DeadlineOctane4.lua with your cmdBatchRender.lua (renamed), this gets the worker to start rendering. Now I am running into the issue that it cannot save the file, maybe you have a hint on that too. I don't think it's a problem with our network, the farm is running stable 24/7 in general.

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

[BK]

Thank you so much, I will flag this in the Thinkbox forum too!

I replaced the DeadlineOctane4.lua with your cmdBatchRender.lua (renamed), this gets the worker to start rendering. Now I am running into the issue that it cannot save the file, maybe you have a hint on that too. I don't think it's a problem with our network, the farm is running stable 24/7 in general.

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

Hi Jxrgen,

Thanks again for the update.
Yes, Thinkbox dev would be the right team to fix their Plugin `DeadlineOctane4.lua` file.
They should be able to see our updates if you share our `cmdBatchRender_2020.2.lua`.
We are assuming the error might be related to their UI submitter if you are using GUI mode.

Would you please try submitting via commandline and see if it works?

cheers

[Kemet]

Hey beautiful render people,

I'm currently trying to set up Octane for our renderfarm that is currently running with Thinkbox Deadline 10.1

First thing that I noticed is, that strangly the plugin-paths are preset up only up to Octane 2019, I just changed the path to the current version 2022 to ge the submission working (see screenshot). The paths are also linked to Enterprise lic, I have a Studio+, could that be an issue?

plugins.PNG

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


Quite an interesting topic for me.
I am in the process of setting Deadline farm using C4D and Octane - do you use the export scene for octane and use only octane standalone for rendering?
(In my setup i use c4d command line and deadline plugin for c4d, so octane is called by c4d directly)

Any idea what the issue is?

[BK]

Quite an interesting topic for me.
I am in the process of setting Deadline farm using C4D and Octane - do you use the export scene for octane and use only octane standalone for rendering?
(In my setup i use c4d command line and deadline plugin for c4d, so octane is called by c4d directly)

Any idea what the issue is?

Hi Kemet,

Thanks for the response.

OctaneRender for C4d supports -exportORBX flag and then use OctaneRender Standalone for rendering with Deadline.
or can submit Cinema4d scenes directly. Please refer to our documentation for more details
https://docs.otoy.com/cinema4d/CommandL ... ering.html

Please note: the -octaneGPU "0:true 1:false" GPU selection/affinity flag only supports with Cinema 4d.exe only.
Check https://www.cineversity.com/wiki/Comman ... arameters/ for more on using cinema4d.exe

We hope the Deadline devs integrate/update Octane in their next release.

Cheers