c4dtoa // deadline // ge_container.cpp (756)

[calle.thor]

Hi,

We have a scene that stops after one frame at on each worker. Every worker can render one frame but cant move on to the next frame in task. The scene can be rendered locally without problems. Other scenes can render fine on deadline.

This is the output from the deadline log where it stops.

0: STDOUT: CRITICAL: Stop [ge_container.cpp(756)]

Cheers,

[Stephen.Blair]

That message is always printed, whether or not there's a problem.

If the worker cannot "move on", is it because of an error in the current render? An error launching the next frame? Do you have more details?

[calle.thor]

Ok, i see. Seems to be related to a shader. Deleted all shaders and now its rendering all frames.

Still though, weird that the command-line renderer is failing but GUI is able to render the same scene.

[peter.horvath6V6K3]

Could you please check the Arnold log if there are any errors? By default errors are printed to the console, but you can also setup writing logs to a file, see https://docs.arnoldrenderer.com/display/A5AFCUG/Log

[calle.thor]

Might be related to OCIO?

Stops at this

2021-02-15 20:49:51: 0: STDOUT: [c4dtoa] 00:00:00 1054MB | [color_manager_ocio] using config file T:\OCIO\aces_1.0.3\config.ocio

[Stephen.Blair]

I doubt it.
The next thing after that is the automatic maketx step. Do you have auto-tx enabled? Try disabling it, or even enabled Ignore Textures.

[calle.thor]

You are correct. Indeed it's the make-tx step. I set tx-generation to "none" and now it's working.

Any idea why this is happening while rendering through deadline and not when rendering locally?

Thanks,

[Stephen.Blair]

How many machines are rendering under Deadline? If there's more than one machine, there can be conflicts when multiple machines try to update the same tx file.

If that's not the problem, then it could be something about the user account and permissions of the render job.

[calle.thor]

Ok, any CLI switches that can be sent upon rendertime to disable tx-generation? Would be easier than going through the settings to disable/enable when needed.

Tried running the job previously with one sigle machine and it failed as well. Maybe a permission thing when initiated by the deadline worker as the machines can render when started from GUI.

[Stephen.Blair]

@Calle Thor
Unfortunately no, there's no command-line flag for autotx

https://docs.arnoldrenderer.com/display/A5AFCUG/Command+line+render

[peter.horvath6V6K3]

Instead of autotx, you can:

A) Use tx files everywhere in the project: open the Tx Manager window and generate Tx files with the Replace texture with Tx option enabled.

B) Generate Tx files in the Tx Manager window and set Tx generation to 'manual'.