AWS Thinkbox Discussion Forums

Cinema 4D linux command line render ?

Anyone using the c4d clr on linux?

Have set this up on centos 7.4 but can’t find/get any documentation on setup etc, was wondering if anyone successfully set this up?

Thanks
Ant

I have the install guide, it’s nothing beyond the obvious (attached)

no info on where to put the license.ini, so I copied it everywhere (/opt/maxon/… AND /root/MAXON/… and that’s stopped the license issue)

running c4d_clr --help gives

[code]General Options:
-nogui … start without user interface
-license [ip [port]] … specifies the license server
-noopengl … disable OpenGL and avoid loading OpenGL libraries
-oglversion=xxx … force a specific OpenGL version. xxx must be 100 * (major version) + (minor version)
-title … set the window title
-xembed winid … run c4d embedded (winid is the parent window as decimal number)
-layout filename … use a custom startup layout
-crashtest … causes an exception to test the built-in signal handler
-nocrashhandler … suppress use of the application’s crash handler
-nogui_nothreads … special commandline debug mode
-debug … enable debug output
-g_alloc=debug … enable debug memory allocator (leak detection)
-g_alloc=release … enable release memory allocator

Render Options:
-render filename … specify a file to render
-frame from [to [step]] … specify start frame, end frame and frame step. ‘to’ and ‘step’ are optional
-oimage imagename … override the image output path for rendering
-omultipass imagename … override the multipass output path for rendering
-oformat imageformat … override the image output format to TIFF/TGA/BMP/IFF/JPG/PICT/PSD/PSB/RLA/RPF/B3D
-oresolution width height … override output image size
-threads threadcnt … specify number of threads (0 for auto-detection)
-take takename … specify the take name for rendering[/code]

so now if I run a test directly on the machine, it renders out (of course missing windows mapped alembics etc)
/opt/maxon/cinema4d/19.024/bin/c4d_clr -render /mnt/servername/tests/c4d/r19_abc.c4d -oimage /tmp/test.jpg

If I run a render through Deadline I get all sorts of issues

2017-11-23 10:49:50: 0: STDOUT: argv[0] = (null) 2017-11-23 10:49:50: 0: STDOUT: argv[1] = -nogui 2017-11-23 10:49:50: 0: STDOUT: argv[2] = -DeadlineConnect 36982 389883408210 2017-11-23 10:49:50: 0: STDOUT: Could not initialize OpenGL system: Could not load dll. Error code: libGL.so: cannot open shared object file: No such file or directory. (relative:///libGL.so) [linux_dll.cpp(89)] 2017-11-23 10:49:50: 0: STDOUT: loading plugin directory: /tmp/Thinkbox/Deadline10/root/slave/linuxbox/plugins/5a141d353548b727acfcff0c 2017-11-23 10:49:50: 0: STDOUT: Error: HOME PATH not set 2017-11-23 10:49:50: 0: STDOUT: License Path does not exists () 2017-11-23 10:49:50: 0: STDOUT: License Directory does not exist [] 2017-11-23 10:49:50: 0: STDOUT: Loading LP_solve lib: /opt/maxon/cinema4d/19.024/bin/resource/modules/motiontracker/liblpsolve55.so 2017-11-23 10:49:50: 0: STDOUT: Warning! Unknown arguments: -DeadlineConnect 36982 389883408210 2017-11-23 10:49:50: 0: STDOUT: C4D END

The args supplied from the commandline are different to the ones from deadlin

argv[0] = (null) argv[1] = -render argv[2] = /mnt/servername/tests/c4d/r19_abc.c4d argv[3] = -oimage argv[4] = /tmp/test.jpg

There was no option in the plugin config for linux so I’m guessing this is something that has never been looked at by Thinkbox?
160812_R18 Installation Guide Linux Command_final.pdf (272 KB)

Excellent testing notes Ant! There was all kinds of trouble 11 months ago when we tried testing a beta version of this Linux build (C4D issues, not Deadline). Can you send us a private ticket/note on what customers are asking for this and that will help draw attention to the dev team.

Anyone else reading this thread, really want a Linux version of C4D to work on Deadline?

Thanks Mike,

I thought the c4d linux versions was one of those industry jokes, like Autodesk Flame on Windows :wink:

So I finally got a copy, it seems hard work extracting any kind of assistance or help with it though!

There’s no specific client, it’s just for testing as one of the reasons for using windows render nodes is C4D (the other being After Effects)

I’m interested in this as it maybe beneficial to cloud rendering etc.

It’s odd as there is no full linux release, and seemingly no method of path translation, maybe if you work on mac and map the linux drives under /Volumes/ it may work?

Majority of C4D users seem to prefer rendering directly with C4D than exporting to .ASS etc.

I think if there is the ability to run linux nodes then there’s most like to be the ability to export .ASS etc.

The painful bit is licensing as you still need to buy a C4D Commandline Render when just about everybody else hands out free commandline render licenses!

No need to add any resources unnecessarily, be interested to see if anyone is using it out there or is interested in using it?

Hey Mike,

I also really want a Linux version of C4D to work on Deadline :smiley:

You guys are ace! :sunglasses: I’m requesting a CLR from Maxon so I can test this out

10.0.12.1
Cinema 4D for Linux is now supported.
docs.thinkboxsoftware.com/produ … notes.html

We had to do some sneaky stuff with Python pathing, so it’s all of Grant’s efforts to get that working out of the box. :slight_smile:

I’ve installed the R19.053 on Centos 7

It needs a license.ini file creating in the bin folder like on Windows and OSX, so should pick this up once it’s been created

there is a setup_c4d_env file in the bin folder which contains the following

[code]# source this file to setup the Cinema 4D environment

C4D_BASE=$PWD/…

export LD_LIBRARY_PATH=$C4D_BASE/lib64:$C4D_BASE/bin/resource/modules/python/Python.linux64.framework/lib64
export PATH=$PATH:$C4D_BASE/bin
export LC_NUMERIC=en_US.UTF-8[/code]

This doesn’t seem to work but manually adding them does

Works great now, still have to do the export project before submitting a file with alembic though

Well, usually ‘env’ files are just sourced before using the application. I’m still not sure why they aren’t configuring these things within Cinema as a fallback plan. While it’s not quite the Unix way, making it easier on people is usually a win-win.

Back to c4d linux again!

I’m having an issue with the env vars being set by Deadline,

2019-11-28 11:07:59:  0: Loading Job's Plugin timeout is Disabled
2019-11-28 11:08:01:  0: Executing plugin command of type 'Sync Files for Job'
2019-11-28 11:08:01:  0: All job files are already synchronized
2019-11-28 11:08:01:  0: Plugin Cinema4DBatch was already synchronized.
2019-11-28 11:08:01:  0: Done executing plugin command of type 'Sync Files for Job'
2019-11-28 11:08:02:  0: Executing plugin command of type 'Initialize Plugin'
2019-11-28 11:08:02:  0: INFO: Executing plugin script '/root/Thinkbox/Deadline10/slave/GPU-01-A/plugins/5ddfa6250866c208188ce58e/Cinema4DBatch.py'
2019-11-28 11:08:02:  0: INFO: About: Cinema 4D Batch Plugin for Deadline
2019-11-28 11:08:02:  0: INFO: Render Job As User disabled, running as current user 'root'
2019-11-28 11:08:02:  0: INFO: The job's environment will be merged with the current environment before rendering
2019-11-28 11:08:02:  0: Done executing plugin command of type 'Initialize Plugin'
2019-11-28 11:08:02:  0: Start Job timeout is disabled.
2019-11-28 11:08:02:  0: Task timeout is disabled.
2019-11-28 11:08:02:  0: Loaded job: r20.059_simple (5ddfa6250866c208188ce58e)
2019-11-28 11:08:02:  0: Executing plugin command of type 'Start Job'
2019-11-28 11:08:02:  0: DEBUG: S3BackedCache Client is not installed.
2019-11-28 11:08:02:  0: INFO: Executing global asset transfer preload script '/root/Thinkbox/Deadline10/slave/xxx/plugins/5ddfa6250866c208188ce58e/GlobalAssetTransferPreLoad.py'
2019-11-28 11:08:02:  0: INFO: Looking for AWS Portal File Transfer...
2019-11-28 11:08:02:  0: INFO: Looking for File Transfer controller in /opt/Thinkbox/S3BackedCache/bin/task.py...
2019-11-28 11:08:02:  0: INFO: Could not find AWS Portal File Transfer.
2019-11-28 11:08:02:  0: INFO: AWS Portal File Transfer is not installed on the system.
2019-11-28 11:08:02:  0: INFO: Start Job called - starting up Cinema 4D Batch plugin
2019-11-28 11:08:02:  0: INFO: Not enforcing a build of Cinema 4D
2019-11-28 11:08:02:  0: CheckPathMapping: Swapped "Z:\xxx\r20_simple_export.c4d" with "/mnt/xxx\r20_simple_export.c4d"
2019-11-28 11:08:02:  0: INFO: [g_additionalModulePath] set to: /root/Thinkbox/Deadline10/slave/GPU-01-A/plugins/5ddfa6250866c208188ce58e
2019-11-28 11:08:02:  0: INFO: [LD_LIBRARY_PATH] set to /opt/maxon/cinema4d/20.026/bin/../lib64:/opt/maxon/cinema4d/20.026/bin/resource/modules/python/Python.linux64.framework/lib64:/opt/maxon/cinema4d/20.026/bin/resource/modules/embree.module/libs/linux64:
2019-11-28 11:08:02:  0: INFO: [PYTHONPATH] set to /opt/maxon/cinema4d/20.026/bin/resource/modules/python/Python.linux64.framework/lib/python2.7:/opt/maxon/cinema4d/20.026/bin/resource/modules/python/Python.linux64.framework/lib64/python2.7/lib-dynload:
2019-11-28 11:08:02:  0: INFO: [PATH] set to /usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/root/bin:/opt/maxon/cinema4d/20.026/bin
2019-11-28 11:08:02:  0: INFO: Cinema 4D socket connection port: 41353

The Deadline path points here
/opt/maxon/cinema4d/20.026/bin/resource/modules/python/Python.linux64.framework/lib64

The linux rendernode is actually here
/opt/maxon/cinema4d/20.026/bin/resource/modules/python/libs/linux64/python.linux64.framework/lib64/

So the python paths are different and I think this is what’s breaking it
/python/Python.linux64.framework/lib64
/python/libs/linux64/python.linux64.framework/lib64/

Is it possible to have the path options in the Deadline plugin options so you can modify this, would be handy for centralised installs also.

What I’ve done is edit the ‘Cinema4DBatch.py’ file in the c4d plugin folder

Changed this part

modLdPath = "%s/../lib64:%s/resource/modules/python/Python.linux64.framework/lib64:%s/resource/modules/embree.module/libs/linux64:%s" % ( c4dDir, c4dDir, c4dDir, ldPath )
modPyPath = "%s/resource/modules/python/Python.linux64.framework/lib/python2.7:%s/resource/modules/python/Python.linux64.framework/lib64/python2.7/lib-dynload:%s" % ( c4dDir, c4dDir, pyPath )
modPath = "%s:%s" % ( path, c4dDir )

to this

modLdPath = "%s/../lib64:%s/resource/modules/python/libs/linux64/python.linux64.framework/lib64:%s/resource/modules/embree.module/libs/linux64:%s" % ( c4dDir, c4dDir, c4dDir, ldPath )
modPyPath = "%s/resource/modules/python/libs/linux64/python.linux64.framework/lib/python2.7:%s/resource/modules/python/libs/linux64/python.linux64.framework/lib64/python2.7/lib-dynload:%s" % ( c4dDir, c4dDir, pyPath )
modPath = "%s:%s" % ( path, c4dDir )

I’ve just checked and the Deadline code is for R19, so this is changed in R20. R21 is the same as R20 but they’ve changed the app folder name!!

another odd thing was rendering locally was no problem, but through deadline it didn’t get a license, solved this issue by copying license.ini from bin to
~/MAXON/.
and
~/Maxon.

I’m not entirely sure this is an issue as tested another node this wasn’t required…

I’m back here again, looking at R25 on CentOS

Jumping through the usual hoops, have put the env vars required in /etc/profile.d/deadline.sh to make sure they get used, I don’t think adding them to .bashrc works

There’s an issue with using batch mode for translations (i’m on 10.1.22.5) , I got a fix for this from Karpreet

outputPath = RepositoryUtils.CheckPathMapping( outputPath )

needs to be added under DeadlineRepository10/plugins/Cinema4DBatch/Cinema4DBatch.py
on line #606.

But I still have the issue where Alembic references in the file aren’t translated.

1 Like

Dredging this old thread back up again. Having odd issues with 10.3.2.1 and the latest versions (2023/2024) on Rocky 8.8 / 9.4 where 2023 doesn’t work but 2024 does. Is this just OS compatibility issues? anyone else hitting these?

Error in PrivateGetNamedTupleMembers: Illegal argument: Condition type not fulfilled.  [parametric_type_impl.cpp(829)]

I’m manually setting the env vars from the setup outside of Deadline to check these, 2024 renders fine but 2023 doesn’t on Rocky 9

export C4D_BASE=/opt/maxon/cinema4dr2024.501
export LD_LIBRARY_PATH=$C4D_BASE/lib64:$C4D_BASE/bin/resource/modules/python/libs/python311.linux64.framework/lib64
export PATH=$PATH:$C4D_BASE/bin
export LC_NUMERIC=en_US.UTF-8
export PYTHONPATH=$C4D_BASE/bin/resource/modules/python/libs/python311.linux64.framework/lib/python3.11/lib-dynload

/opt/maxon/cinema4dr2024.501/bin/Commandline -render /mnt/jobs/tests/c4d/2024.0.c4d

export C4D_BASE= /opt/maxon/cinema4dr2023.202
export LD_LIBRARY_PATH=$C4D_BASE/lib64:$C4D_BASE/bin/resource/modules/python/libs/python310.linux64.framework/lib64
export PATH=$PATH:$C4D_BASE/bin
export LC_NUMERIC=en_US.UTF-8
export PYTHONPATH=$C4D_BASE/bin/resource/modules/python/libs/python310.linux64.framework/lib/python3.10/lib-dynload

/opt/maxon/cinema4dr2023.202/bin/Commandline -render /mnt/jobs/tests/c4d/2024.0.c4d

Submitting Deadline jobs fails as well, I notice in the logs it looks like it’s adding the wrong python version as Deadline takes care of the ‘setup’ script itself.

INFO: [LD_LIBRARY_PATH] set to /opt/maxon/cinema4dr2023.202/bin/../lib64:/opt/maxon/cinema4dr2023.202/bin/resource/modules/python/Python.linux64.framework/lib64:/opt/maxon/cinema4dr2023.202/bin/resource/modules/embree.module/libs/linux64:
INFO: [PYTHONPATH] set to /opt/maxon/cinema4dr2023.202/bin/resource/modules/python/Python.linux64.framework/lib/python2.7:/opt/maxon/cinema4dr2023.202/bin/resource/modules/python/Python.linux64.framework/lib64/python2.7/lib-dynload:
INFO: [PATH] set to /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/bin:/usr/bin:/sbin:/bin:/usr/bin:/bin:/usr/bin:/opt/maxon/cinema4dr2023.202/bin

These paths for 2023 are different…

LD_LIBRARY_PATH
deadline = python/Python.linux64.framework/lib64
c4dsetup = python/libs/python310.linux64.framework/lib64

PYTHONPATH
deadline = python/Python.linux64.framework/lib/python2.7
/python/Python.linux64.framework/lib64/python2.7/lib-dynload
c4dsetup = python/libs/python310.linux64.framework/lib/python3.10/lib-dynload

So I think the 2 issues I’m facing are possible 2023 non compatibility with rhel8> and the deadline c4d plugin writing it’s own setup envs and not including python3 options.

I started doing for Cinema4DBatch.py in 10.3.2.1 and realise it’s exactly the same as I’d done a few post above for R20…

so around line 216

#ORG        modLdPath = "%s/../lib64:%s/resource/modules/python/Python.linux64.framework/lib64:%s/resource/modules/embree.module/libs/linux64:%s" % ( c4dDir, c4dDir, c4dDir, ldPath )
#R20        modLdPath = "%s/../lib64:%s/resource/modules/python/libs/linux64/python.linux64.framework/lib64:%s/resource/modules/embree.module/libs/linux64:%s" % ( c4dDir, c4dDir, c4dDir, ldPath )
            modLdPath = "%s/../lib64:%s/resource/modules/python/libs/python310.linux64.framework/lib64:%s/resource/modules/embree.module/libs/linux64:%s" % ( c4dDir, c4dDir, c4dDir, ldPath )
#2024       modLdPath = "%s/../lib64:$s/resource/modules/python/libs/python311.linux64.framework/lib64:%s/resource/modules/embree.module/libs/linux64:%s" % ( c4dDir, c4dDir, c4dDir, ldPath )
#ORG        modPyPath = "%s/resource/modules/python/Python.linux64.framework/lib/python2.7:%s/resource/modules/python/Python.linux64.framework/lib64/python2.7/lib-dynload:%s" % ( c4dDir, c4dDir, pyPath )
#R20        modPyPath = "%s/resource/modules/python/libs/linux64/python.linux64.framework/lib/python2.7:%s/resource/modules/python/libs/linux64/python.linux64.framework/lib64/python2.7/lib-dynload:%s" % ( c4dDir, c4dDir, pyPath )
            modPyPath = "%s/resource/modules/python/libs/python310.linux64.framework/lib:%s/resource/modules/python/libs/python310.linux64.framework/lib/python3.10/lib-dynload:%s" % ( c4dDir, c4dDir, pyPath )
#2024       modPyPath = "%s/resource/modules/python/libs/python311.linux64.framework/lib/python3.11/lib-dynload:%s:%s/resource/modules/python/libs/python310.linux64.framework/lib" % ( c4dDir, c4dDir, pyPath )

I’ll test with 2024 at some point, but I’m getting this weird dot in the path mapping when using both software render and Redshift…
image
^File path set, path mapping options in Deadline are correct, but renders to
F:_repo\test\c4d\F_repo\test\c4d
image
logs load file fine
CheckPathMapping: Swapped "F:\_repo\test\c4d\c4d2023_rs.c4d" with "/mnt/_repo\test\c4d\c4d2023_rs.c4d"

I’m throwing version 2025 into the mix now too!!

running it outside of Deadline with the software render in either 2024 or 2025 works ok

/opt/maxon/cinema4dr2024.501/bin
source setup_c4d_env
/opt/maxon/cinema4dr2024.501/bin/Commandline -render /mnt/jobs/tests/c4d/2024.0.c4d -frame 0 0 -oimage /mnt/jobs/tests/c4d/
/opt/maxon/cinema4dr2025.000/bin
source setup_c4d_env
/opt/maxon/cinema4dr2025.000/bin/Commandline -render /mnt/jobs/tests/c4d/2025.0.c4d -frame 0 0 -oimage /mnt/jobs/tests/c4d/

but via Deadline it just hangs

2024-09-11 15:05:34:  0: CheckPathMapping: Swapped "Z:\tests\c4d\out\" with "/mnt/jobs/tests/c4d\out\"
2024-09-11 15:05:34:  0: INFO: Validating the path: '/mnt/jobs/tests/c4d/out/'
2024-09-11 15:05:34:  0: INFO: Rendering main output to network drive
2024-09-11 15:05:34:  0: STDOUT: Running Script: /var/lib/Thinkbox/Deadline10/workers/et-ws-lin-03/jobsData/66e19a567632c8e160c10f90/thread0_tempCoKxP0/c4d_Batch_Script.py

both setup envs have the same code

# source this file to setup the Cinema 4D environment

C4D_BASE=$PWD/..

export LD_LIBRARY_PATH=$C4D_BASE/lib64:$C4D_BASE/bin/resource/modules/python/libs/python311.linux64.framework/lib64
export PATH=$PATH:$C4D_BASE/bin
export LC_NUMERIC=en_US.UTF-8
export PYTHONPATH=$C4D_BASE/bin/resource/modules/python/libs/python311.linux64.framework/lib/python3.11/lib-dynload

The updated entried in the Cinema4DBatch.py replicate this
LD_LIBRARY_PATH

LD_LIBRARY_PATH=$C4D_BASE/lib64:$C4D_BASE/bin/resource/modules/python/libs/python311.linux64.framework/lib64
modLdPath = "%s/../lib64:$s/resource/modules/python/libs/python311.linux64.framework/lib64:%s/resource/modules/embree.module/libs/linux64:%s" % ( c4dDir, c4dDir, c4dDir, ldPath )

$C4D_BASE/lib64
%s/…/lib64

$C4D_BASE/bin/resource/modules/python/libs/python311.linux64.framework/lib64
$s/resource/modules/python/libs/python311.linux64.framework/lib64:%s/resource/modules/embree.module/libs/linux64:%s"

and PYTHONPATH

PYTHONPATH=$C4D_BASE/bin/resource/modules/python/libs/python311.linux64.framework/lib/python3.11/lib-dynload
modPyPath = "%s/resource/modules/python/libs/python311.linux64.framework/lib/python3.11/lib-dynload:%s:%s/resource/modules/python/libs/python310.linux64.framework/lib" % ( c4dDir, c4dDir, pyPath )

$C4D_BASE/bin/resource/modules/python/libs/python311.linux64.framework/lib/python3.11/lib-dynload
=
%s/resource/modules/python/libs/python311.linux64.framework/lib/python3.11/lib-dynload:%s:%s/resource/modules/python/libs/python310.linux64.framework/lib

I can see from the logs the env vars are being set

INFO: [LD_LIBRARY_PATH] set to /opt/maxon/cinema4dr2025.000/bin/../lib64:/opt/maxon/cinema4dr2025.000/bin/resource/modules/python/libs/python311.linux64.framework/lib64:/opt/maxon/cinema4dr2025.000/bin/resource/modules/embree.module/libs/linux64:
INFO: [PYTHONPATH] set to /opt/maxon/cinema4dr2025.000/bin/resource/modules/python/libs/python311.linux64.framework/lib64:/opt/maxon/cinema4dr2025.000/bin/resource/modules/python/libs/python311.linux64.framework/lib/python3.11/lib-dynload:

I tried trimming the env vars down to match the setup script

INFO: Setting Process Environment Variable LD_LIBRARY_PATH to /opt/maxon/cinema4dr2025.000/bin/../lib64:/opt/maxon/cinema4dr2025.000/bin/resource/modules/python/libs/python311.linux64.framework/lib64
INFO: Setting Process Environment Variable PYTHONPATH to /opt/maxon/cinema4dr2025.000/bin/resource/modules/python/libs/python311.linux64.framework/lib/python3.11/lib-dynload

but same issue where it hangs

STDOUT: Running Script: /var/lib/Thinkbox/Deadline10/workers/et-ws-lin-03/jobsData/66e1b30e7632c8e160c10fd6/thread0_tempqBln90/c4d_Batch_Script.py

Is it possible this script is breaking it with python versions?

Full Command: "/opt/maxon/cinema4dr2025.000/bin/Commandline" -nogui -noopengl -redshift-license-maxon-disable -redshift-log-console Debug "-DeadlineConnect 42507 1726138833 '/var/lib/Thinkbox/Deadline10/workers/et-ws-lin-03/jobsData/66e1b30e7632c8e160c10fd6/importTest_temp04Y4I0/importCheck.txt'"

I don’t know what the DeadlineConnect part is doing, but the script
c4d_Batch_Script.py
gets stuck and starts with the following code

#!/usr/bin/python
# -*- coding: utf-16-le -*-
import c4d
from c4d import bitmaps
from c4d import documents
from c4d.threading import C4DThread
import os.path

looking at this update
https://docs.thinkboxsoftware.com/products/deadline/10.1/1_User%20Manual/manual/python-upgrade.html
which disappeared in 10.3 docs…
and here

https://docs.thinkboxsoftware.com/products/deadline/10.3/1_User%20Manual/manual/python-upgrade.html

Digging back into the Cinema4DBatch.py file I see it’s creating the c4d_Batch_Script.py file

but even ignoring this and doing a non batch job it fails

INFO: Executable: "/mnt/sw/c4d/2025.002/bin/Commandline"
NFO: [LD_LIBRARY_PATH] set to /mnt/sw/c4d/2025.002/bin/../lib64:/mnt/sw/c4d/2025.002/bin/resource/modules/python/libs/python311.linux64.framework/lib64
NFO: [PYTHONPATH] set to /mnt/sw/c4d/2025.002/bin/resource/modules/python/libs/python311.linux64.framework/lib/python3.11/lib-dynload
INFO: [PATH] set to /root/.local/bin:/root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/bin:/usr/bin:/sbin:/bin:/usr/bin:/bin:/usr/bin:/mnt/sw/c4d/2025.002/bin
CheckPathMapping: Swapped "Z:\tests\c4d\2025.0.c4d" with "/mnt/jobs/tests\c4d\2025.0.c4d"
CheckPathMapping: Swapped "Z:\tests\c4d\out\" with "/mnt/jobs/tests\c4d\out\"
INFO: Validating the path: '/mnt/jobs/tests/c4d/out/'
INFO: Rendering main output to network drive
INFO: Argument: -nogui -noopengl -redshift-license-maxon-disable -arnoldAbortOnLicenseFail true -render "/mnt/jobs/tests/c4d/2025.0.c4d" -frame 0 0 -take "Main" -oresolution 1280 720 -oimage "/mnt/jobs/tests/c4d/out/Documents" -redshift-log-console Debug
INFO: Full Command: "/mnt/sw/c4d/2025.002/bin/Commandline" -nogui -noopengl -redshift-license-maxon-disable -arnoldAbortOnLicenseFail true -render "/mnt/jobs/tests/c4d/2025.0.c4d" -frame 0 0 -take "Main" -oresolution 1280 720 -oimage "/mnt/jobs/tests/c4d/out/Documents" -redshift-log-console Debug
INFO: Startup Directory: "/mnt/sw/c4d/2025.002/bin"
INFO: Process Priority: BelowNormal
INFO: Process Affinity: default
INFO: Process is now running
INFO: Process exit code: 139

Yet if I run the Full Command outside of Deadline it works fine

"/mnt/sw/c4d/2025.002/bin/Commandline" -nogui -noopengl -redshift-license-maxon-disable -arnoldAbortOnLicenseFail true -render "/mnt/jobs/tests/c4d/2025.0.c4d" -frame 0 0 -take "Main" -oresolution 1280 720 -oimage "/mnt/jobs/tests/c4d/out/Documents" -redshift-log-console Debug

output

[root@et-ws-lin-01 bin]# "/mnt/sw/c4d/2025.002/bin/Commandline" -nogui -noopengl -redshift-license-maxon-disable -arnoldAbortOnLicenseFail true -render "/mnt/jobs/tests/c4d/2025.0.c4d" -frame 0 0 -take "Main" -oresolution 1280 720 -oimage "/mnt/jobs/tests/c4d/out/Documents" -redshift-log-console Debug
Application start      : 10/21/24 at 16:18:11
Executable (T)         : 64 Bit
Version / Build        : 2025.0.2 / 2025_0_2_f4b54da0ba4e_1479846803
Debugger               : not available
Memory model           : release
Startup path           : file:///mnt/sw/c4d/2025.002/bin
Application path       : file:///mnt/sw/c4d/2025.002/bin/Commandline
Application executable : file:///mnt/sw/c4d/2025.002/bin/Commandline
Resource path          : file:///mnt/sw/c4d/2025.002/bin/resource
Library path           : file:///mnt/sw/c4d/2025.002/bin/library
Module path(s)         : file:///mnt/sw/c4d/2025.002/bin/corelibs; file:///mnt/sw/c4d/2025.002/bin/plugins; file:///root/Maxon/bin_35B49051_x/plugins
Temporary path         : file:///tmp
Prefs path             : file:///root/Maxon/bin_35B49051_x
Global Prefs path      : file:///root/Maxon
...
Command line arguments : "-nogui" "-noopengl" "-redshift-license-maxon-disable" "-arnoldAbortOnLicenseFail" "true" "-render" "/mnt/jobs/tests/c4d/2025.0.c4d" "-frame" "0" "0" "-take" "Main" "-oresolution" "1280" "720" "-oimage" "/mnt/jobs/tests/c4d/out/Documents" "-redshift-log-console" "Debug"
...
Avahi version 0.8 detected
argv[0] = (null)
argv[1] = -nogui
argv[2] = -noopengl
argv[3] = -redshift-license-maxon-disable
argv[4] = -arnoldAbortOnLicenseFail
argv[5] = true
argv[6] = -render
argv[7] = /mnt/jobs/tests/c4d/2025.0.c4d
argv[8] = -frame
argv[9] = 0
argv[10] = 0
argv[11] = -take
argv[12] = Main
argv[13] = -oresolution
argv[14] = 1280
argv[15] = 720
argv[16] = -oimage
argv[17] = /mnt/jobs/tests/c4d/out/Documents
argv[18] = -redshift-log-console
argv[19] = Debug
Loading LP_solve lib: /mnt/sw/c4d/2025.002/bin/resource/modules/motiontracker/liblpsolve55.so
...
Redshift Debug: PreviewScheduler: Caches Cleared
msg: override imagesize to 1280 720
Loading Project: /mnt/jobs/tests/c4d/2025.0.c4d
Rendering frame 0 at <Mon Oct 21 16:18:18 2024>Rendering frame 0 at <Mon Oct 21 16:18:18 2024>
Rendering Phase: Setup
Rendering Phase: Main Render
Progress: 0%
...
Progress: 99%
Rendering Phase: Finalize
Rendering successful: 0.142 sec.
Warning! Unknown arguments:  -nogui -noopengl -arnoldAbortOnLicenseFail trueWarning! Unknown arguments:  -nogui -noopengl -arnoldAbortOnLicenseFail true
Redshift Debug: PreviewScheduler: Flush/Clear Context
Redshift Debug: PreviewScheduler: End
Redshift Debug: PreviewScheduler: Flush completed
C4D END

removing the unknown arguments clears the warning messages, I don’t think this is causing the problem but will try and remove them from both scipts. I’m testing with 10.4.0.8 now.

I circled back round to another post I made where the fix was to not run Deadline as ‘root’ this get’s it’ back up and running!

Privacy | Site terms | Cookie preferences