AWS Thinkbox Discussion Forums

C4D Environment Variable problem

Wierd, my version of RS is the latest.

I’ll try tomorrow and let you know.

Still doesnt work on the latest version :frowning:

=======================================================
Error

Error: Cinema 4D startup: Error getting connection from Cinema4D: Monitored managed process “Cinema4DProcess” has exited or been terminated.
at Deadline.Plugins.PluginWrapper.StartJob(String& outMessage, AbortLevel& abortLevel)

=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.SandboxedPlugin.SendMessageToSandbox(DeadlineMessage messageToSend)
at Deadline.Plugins.SandboxedPlugin.StartJob(Job job)
at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask(TaskLogWriter tlw)

=======================================================
Log

2017-09-19 15:31:36: 0: Loading Job’s Plugin timeout is Disabled
2017-09-19 15:31:38: 0: Executing plugin command of type ‘Sync Files for Job’
2017-09-19 15:31:38: 0: All job files are already synchronized
2017-09-19 15:31:38: 0: Plugin Cinema4DBatch was already synchronized.
2017-09-19 15:31:38: 0: Done executing plugin command of type ‘Sync Files for Job’
2017-09-19 15:31:38: 0: Executing plugin command of type ‘Initialize Plugin’
2017-09-19 15:31:39: 0: INFO: Executing plugin script ‘C:\Users\Admin\AppData\Local\Thinkbox\Deadline10\slave\gpu-1\plugins\59c1296763a7f807b8517584\Cinema4DBatch.py’
2017-09-19 15:31:39: 0: INFO: About: Cinema 4D Batch Plugin for Deadline
2017-09-19 15:31:39: 0: INFO: Render Job As User disabled, running as current user ‘Admin’
2017-09-19 15:31:39: 0: INFO: The job’s environment will be merged with the current environment before rendering
2017-09-19 15:31:39: 0: Done executing plugin command of type ‘Initialize Plugin’
2017-09-19 15:31:39: 0: Start Job timeout is disabled.
2017-09-19 15:31:39: 0: Task timeout is disabled.
2017-09-19 15:31:39: 0: Loaded job: FLUID_015.c4d - Cam1 (59c1296763a7f807b8517584)
2017-09-19 15:31:39: 0: Executing plugin command of type ‘Start Job’
2017-09-19 15:31:39: 0: INFO: Executing global job preload script ‘C:\Users\Admin\AppData\Local\Thinkbox\Deadline10\slave\gpu-1\plugins\59c1296763a7f807b8517584\GlobalJobPreLoad.py’
2017-09-19 15:31:39: 0: INFO: Looking for AWS Portal File Transfer…
2017-09-19 15:31:39: 0: INFO: Looking for File Transfer controller in C:/Program Files/Thinkbox/S3BackedCache/bin/task.py…
2017-09-19 15:31:39: 0: INFO: Could not find AWS Portal File Transfer.
2017-09-19 15:31:39: 0: INFO: AWS Portal File Transfer is not installed on the system.
2017-09-19 15:31:39: 0: INFO: Start Job called - starting up Cinema 4D Batch plugin
2017-09-19 15:31:39: 0: INFO: Not enforcing a build of Cinema 4D
2017-09-19 15:31:39: 0: INFO: Cinema 4D socket connection port: 59060
2017-09-19 15:31:39: 0: INFO: Parameters: -nogui -redshift-gpu 0 -redshift-gpu 1 “-DeadlineConnect 59060 558994857073”
2017-09-19 15:31:39: 0: INFO: Starting monitored managed process Cinema4DProcess
2017-09-19 15:31:39: 0: INFO: Stdout Redirection Enabled: True
2017-09-19 15:31:39: 0: INFO: Stdout Handling Enabled: True
2017-09-19 15:31:39: 0: INFO: Popup Handling Enabled: True
2017-09-19 15:31:39: 0: INFO: QT Popup Handling Enabled: False
2017-09-19 15:31:39: 0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: False
2017-09-19 15:31:39: 0: INFO: Using Process Tree: True
2017-09-19 15:31:39: 0: INFO: Hiding DOS Window: True
2017-09-19 15:31:39: 0: INFO: Creating New Console: False
2017-09-19 15:31:39: 0: INFO: Running as user: Admin
2017-09-19 15:31:39: 0: INFO: Executable: “C:\Program Files\MAXON\CINEMA 4D R18\Commandline.exe”
2017-09-19 15:31:39: 0: INFO: Argument: -nogui -redshift-gpu 0 -redshift-gpu 1 “-DeadlineConnect 59060 558994857073”
2017-09-19 15:31:39: 0: INFO: Full Command: “C:\Program Files\MAXON\CINEMA 4D R18\Commandline.exe” -nogui -redshift-gpu 0 -redshift-gpu 1 “-DeadlineConnect 59060 558994857073”
2017-09-19 15:31:39: 0: INFO: Startup Directory: “C:\Program Files\MAXON\CINEMA 4D R18”
2017-09-19 15:31:39: 0: INFO: Process Priority: BelowNormal
2017-09-19 15:31:39: 0: INFO: Process Affinity: default
2017-09-19 15:31:39: 0: INFO: Process is now running
2017-09-19 15:31:39: 0: STDOUT: Application start : 09/19/17 at 15:31:39
2017-09-19 15:31:39: 0: STDOUT: Executable : 64 Bit
2017-09-19 15:31:39: 0: STDOUT: Version / Build : 18.057 / RB203954
2017-09-19 15:31:39: 0: STDOUT: Debugger : not available
2017-09-19 15:31:39: 0: STDOUT: Memory model : release
2017-09-19 15:31:39: 0: STDOUT: Startup path : file:///C:/Program Files/MAXON/CINEMA 4D R18
2017-09-19 15:31:39: 0: STDOUT: Application path : file:///C:/Program Files/MAXON/CINEMA 4D R18/Commandline.exe
2017-09-19 15:31:39: 0: STDOUT: Application executable : file:///C:/Program Files/MAXON/CINEMA 4D R18/Commandline.exe
2017-09-19 15:31:39: 0: STDOUT: Resource path : file:///C:/Program Files/MAXON/CINEMA 4D R18/resource
2017-09-19 15:31:39: 0: STDOUT: Module path(s) : file:///C:/Program Files/MAXON/CINEMA 4D R18/modules
2017-09-19 15:31:39: 0: STDOUT: Temporary path : file:///C:/Users/Admin/AppData/Local/Temp
2017-09-19 15:31:39: 0: STDOUT: Prefs path : file:///C:/Users/Admin/AppData/Roaming/MAXON/CINEMA 4D R18_62A5E681
2017-09-19 15:31:39: 0: STDOUT: Global Prefs path : file:///C:/Users/Admin/AppData/Roaming/MAXON
2017-09-19 15:31:39: 0: STDOUT: OS version : Windows 10, 64 Bit, Professional Edition (build 14393)
2017-09-19 15:31:39: 0: STDOUT: Processor : 16(32)x Intel Xeon CPU E5-2620 v4
2017-09-19 15:31:39: 0: STDOUT: Computer name : GPU-1
2017-09-19 15:31:39: 0: STDOUT: Thread Count : 32
2017-09-19 15:31:39: 0: STDOUT: Cpu Speed (MHz) : 2100.000
2017-09-19 15:31:39: 0: STDOUT: Application Type : Modular
2017-09-19 15:31:39: 0: STDOUT: Command line arguments : “-nogui” “-redshift-gpu” “0” “-redshift-gpu” “1” “-DeadlineConnect 59060 558994857073”
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/c4dplugin.xdl64 with module(s) net.maxon.c4dplugin net.maxon.c4d.c4dplugin
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/crashhandler.module.xdl64 with module(s) net.maxon.crashhandler
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/crypt.module.xdl64 with module(s) net.maxon.crypt
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/drawport_general.module.xdl64 with module(s) net.maxon.drawport_general
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/drawport_opengl.module.xdl64 with module(s) net.maxon.drawport_opengl
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/drawport_selector.module.xdl64 with module(s) net.maxon.drawport_selector
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/gui.module.xdl64 with module(s) net.maxon.gui
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/image.module.xdl64 with module(s) net.maxon.image
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/math.module.xdl64 with module(s) net.maxon.math
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/mesh.module.xdl64 with module(s) net.maxon.mesh
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/misc.module.xdl64 with module(s) net.maxon.misc
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/network.module.xdl64 with module(s) net.maxon.network
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/opencl.module.xdl64 with module(s) net.maxon.opencl
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/opensubdiv.module.xdl64 with module(s) net.maxon.opensubdiv
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/render.module.xdl64 with module(s) net.maxon.render
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/shaderbase.module.xdl64 with module(s) net.maxon.shaderbase
2017-09-19 15:31:39: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/triangulation.module.xdl64 with module(s) net.maxon.triangulation
2017-09-19 15:31:53: 0: STDOUT: OpenGL root context initialized
2017-09-19 15:31:53: 0: STDOUT: Vendor : NVIDIA Corporation (NVIDIA)
2017-09-19 15:31:53: 0: STDOUT: Renderer : GeForce GTX 1070/PCIe/SSE2
2017-09-19 15:31:53: 0: STDOUT: OpenGL version: 4.5.0 NVIDIA 384.94
2017-09-19 15:31:53: 0: STDOUT: Driver version: 384.94
2017-09-19 15:31:55: 0: STDOUT: OpenGL root context initialized
2017-09-19 15:31:55: 0: STDOUT: Vendor : VMware, Inc. (VMWARE)
2017-09-19 15:31:55: 0: STDOUT: Renderer : Gallium 0.4 on llvmpipe (LLVM 4.0, 256 bits)
2017-09-19 15:31:55: 0: STDOUT: OpenGL version: 3.3 (Core Profile) Mesa 17.0.1 (git-)
2017-09-19 15:31:55: 0: STDOUT: Driver version: 17.0.1 (git-)
2017-09-19 15:31:58: 0: STDOUT: X-Particles running on Command Line Render.
2017-09-19 15:31:58: 0: STDOUT:
2017-09-19 15:31:58: 0: STDOUT: ----------------------------------------
2017-09-19 15:31:58: 0: STDOUT: X-Particles particle system successfully loaded
2017-09-19 15:31:58: 0: STDOUT: X-Particles Build 3.5.0411 Release
2017-09-19 15:31:58: 0: STDOUT: Thu Mar 02 14:02:31 2017
2017-09-19 15:31:58: 0: STDOUT: Copyright © INSYDIUM LTD
2017-09-19 15:31:58: 0: STDOUT: Registered To : Emily Brady mario@piranhabar.ie
2017-09-19 15:31:58: 0: STDOUT: X-Particles is offline, license time remaining is 23 days.
2017-09-19 15:31:58: 0: STDOUT: ----------------------------------------
2017-09-19 15:31:58: 0: STDOUT:
2017-09-19 15:31:58: 0: STDOUT: Warning: Unknown arguments: -redshift-gpu -redshift-gpu -DeadlineConnect 59060 558994857073
2017-09-19 15:31:59: 0: WARNING: Monitored managed process Cinema4DProcess is no longer running
2017-09-19 15:31:59: 0: Done executing plugin command of type ‘Start Job’

=======================================================
Details

Date: 09/19/2017 15:32:00
Frames: 9
Elapsed Time: 00:00:00:24
Job Submit Date: 09/19/2017 15:27:50
Job User: mario
Average RAM Usage: 7742345216 (6%)
Peak RAM Usage: 7742345216 (6%)
Average CPU Usage: 11%
Peak CPU Usage: 18%
Used CPU Clocks (x10^6 cycles): 149088
Total CPU Clocks (x10^6 cycles): 1355345

=======================================================
Slave Information

Slave Name: GPU-1
Version: v10.0.3.2 Release (072d054c6)
Operating System: Windows 10 Pro
Running As Service: No
Machine User: Admin
IP Address: 10.1.1.188
MAC Address: 0C:C4:7A:E4:23:86
CPU Architecture: x64
CPUs: 32
CPU Usage: 0%
Memory Usage: 6.9 GB / 127.9 GB (5%)
Free Disk Space: 26.286 GB
Video Card: LogMeIn Mirror Driver

Well, the GPU overrides have been there for over eight months now, but there is supposed to be text with them. Here’s the code that drives those arguments:

        selectedGPUs = self.GetGpuOverrides()
        if len( selectedGPUs ) > 0:
            for gpu in selectedGPUs:
                parameters += "-redshift-gpu %s " % gpu

Are you specifying any GPU overrides? They can be driven both by the Slave GPU override settings as well as the submitter. I’m assuming this is at the submission level at the moment and you should be able to see it in the job info. I’ll do some digging on our side here, but would you be willing to archive that job and send it over as well? The code for GetGpuOverrides() is supposed to be filtering out empty GPU text but they’re pretty clearly in your job report there…

I’m not specifying any Overrides. Yes I can archive and send it to you. See attached.
mario__Cinema4DBatch__FLUID_015.c4d__59c1280463a7f81554ad8aeb.zip (350 KB)

Okay, well from the archive (wasn’t able to import, so tore into data manually) the overrides are blank:

            "GPUsPerTask": "0",
            "GPUsSelectDevices": "",

How about your Slave GPU overrides? It should be this window:

Just trying to get you back on Batch mode success here while we figure out what’s wrong.

Ok so the only overrides I have are on one GPU slave. Which is a 8GPU rack where I have GPU Affinity set up. 4 slave instances, 2 gpu each.

All other GPU slave (workstations) overrides are off.

Shouldn’t deadline pass the Evironment Variable to the slaves? That C4D_PLUGINS_DIR that I use on my workstation should be passed to the slaves at submission/render time right? Royal Render used to do that.

Hi, any news on this?

I’ve just double-checked the GPU override code in DL 10.0.3.2 and I see absolutely nothing wrong here. As this thread is getting confusing with multiple issues in one thread. Could you clarify if the GPU issue is still actually an issue and if so, provide steps to reproduce? For the ENV VAR issue, is it now working for you, once you have followed Edwin’s temp patch to hard-code it to your system wide env var?

EDIT: Scrap that. I see what is going on here. Patch shortly. :wink:

Yep, I agree. Tks!

Let me just try to clarify the current situation.

Submitting with use batch not working. Get that error I pasted there.

Then the initial C4D_PLUGINS_DIR Environment Var is kinda solved.

I mean, It loads Redshift and all plugins when rendering but that’s because I’ve added that Env Var to the rack’s Windows Env Vars. But I was just wondering if that shouldn’t be handled by DL. It showld grab that Env Var from the workstation that submitted the job right? Or from the submitted file. (not sure how it actually works)

ok, see attached for single py file which should unzip and overwrite the same named file in your Cinema4DBatch plugin directory on your repo:
“<your_repo>/plugins/Cinema4DBatch/Cinema4DBatch.py”

Cinema4DBatch.py.zip (9.4 KB)

ENV VAR [C4D_PLUGINS_DIR] issue

Typically, ENV VARs are set either at machine level, user level or process level. Deadline provides the ability to override/inject ENV VARs into each Deadline job as an additional place to ‘apply’ ENV VARs which it does at the “process” level. Most studios apply ENV VARs at some kind of “context” level, such as within a batch/shell script which applies various ENV VARs when you execute the application such as C4D. This “context” level is essentially applying it at “process” level.

In either case, Deadline currently respects any “Deadline Job ENV VAR override” which would be added to the “Environment” section when you double-click a job and view its job properties in Monitor OR if any ENV VAR was set via that “context” level (a.k.a. script that might be used to apply various ENV VARs AND then startup the app in question such as C4D).

Sooo, the issue here as Edwin explained earlier is we were ignoring any machine level setting of this ENV VAR (which is where you set it, which is perfectly fine and valid and is probably the normal ‘way’ that Windows users do it) and relying on “inheriting” this ENV VAR value at the process level when Deadline starts up C4D, which SHOULD normally always work.

HOWEVER, we had a bug where if this ENV VAR was NOT set at Deadline job level as an override, we assumed it wouldn’t be present at the machine level and then completely overwrite this ENV VAR just during C4D ‘runtime’ of this app only, so that we can direct this ENV VAR to ‘find’ the Deadline-C4D Batch pyp plugin, which is needed to make the C4DBatch work in Deadline.

So, the FIX is for our C4D plugin to first check if the Deadline job ENV VAR override is present and if not, check for a machine level version of this ENV VAR and if still not present, then just apply it anyway by us, so we can direct the loading of our custom plugin. If the first 2 cases above, if the ENV VAR is present at job override level or machine level, then we combine that present value with our custom plugin path as well.

Redshift [-redshift-gpu X] issue

This looks like we simply need to ‘wrap’ the Redshift GPU CLI flags for each ordinal in another set of quotation marks so that the CLI arguments are passed to C4D in an acceptable manner. I’ve gone ahead and fixed this as well in the above provided patch.

I should add in both issues above, they were only C4D “Batch” plugin issues, so the non-Batch version of our C4D plugin should have always worked, which looking back at one of your old job reports provided in this thread, that seems to be the correct case here.

As I’m currently travelling, I can’t fully test these fixes, so would appreciate it if you could give it a go and report back. If these fixes work, as they are applicable to Deadline 9 as well, I will push them back to DL9 and they will also appear later on in a future build of DL10 as well.

Thanks for the feedback!

Tks for the very clear explanation.

I’ve replaced the .py file, deleted the Env Var at Machine Level on the GPU rack. Restarted Launcher and Slaves.

But I think it’s still not working:

=======================================================
Error

Error: Cinema 4D startup: Error getting connection from Cinema4D: Monitored managed process “Cinema4DProcess” has exited or been terminated.
at Deadline.Plugins.PluginWrapper.StartJob(String& outMessage, AbortLevel& abortLevel)

=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.SandboxedPlugin.SendMessageToSandbox(DeadlineMessage messageToSend)
at Deadline.Plugins.SandboxedPlugin.StartJob(Job job)
at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask(TaskLogWriter tlw)

=======================================================
Log

2017-09-21 13:01:37: 0: Loading Job’s Plugin timeout is Disabled
2017-09-21 13:01:38: 0: Executing plugin command of type ‘Sync Files for Job’
2017-09-21 13:01:38: 0: All job files are already synchronized
2017-09-21 13:01:38: 0: Synchronizing Plugin Cinema4DBatch from \3DSERVER\DeadlineRepository10\plugins\Cinema4DBatch took: 0 seconds
2017-09-21 13:01:38: 0: Done executing plugin command of type ‘Sync Files for Job’
2017-09-21 13:01:38: 0: Executing plugin command of type ‘Initialize Plugin’
2017-09-21 13:01:39: 0: INFO: Executing plugin script ‘C:\Users\Admin\AppData\Local\Thinkbox\Deadline10\slave\gpu-1-instance-01\plugins\59c3aa1763a7f82830b53d73\Cinema4DBatch.py’
2017-09-21 13:01:39: 0: INFO: About: Cinema 4D Batch Plugin for Deadline
2017-09-21 13:01:39: 0: INFO: Render Job As User disabled, running as current user ‘Admin’
2017-09-21 13:01:39: 0: INFO: The job’s environment will be merged with the current environment before rendering
2017-09-21 13:01:39: 0: Done executing plugin command of type ‘Initialize Plugin’
2017-09-21 13:01:39: 0: Start Job timeout is disabled.
2017-09-21 13:01:39: 0: Task timeout is disabled.
2017-09-21 13:01:39: 0: Loaded job: test2.c4d (59c3aa1763a7f82830b53d73)
2017-09-21 13:01:39: 0: Executing plugin command of type ‘Start Job’
2017-09-21 13:01:39: 0: INFO: Executing global job preload script ‘C:\Users\Admin\AppData\Local\Thinkbox\Deadline10\slave\gpu-1-instance-01\plugins\59c3aa1763a7f82830b53d73\GlobalJobPreLoad.py’
2017-09-21 13:01:39: 0: INFO: Looking for AWS Portal File Transfer…
2017-09-21 13:01:39: 0: INFO: Looking for File Transfer controller in C:/Program Files/Thinkbox/S3BackedCache/bin/task.py…
2017-09-21 13:01:39: 0: INFO: Could not find AWS Portal File Transfer.
2017-09-21 13:01:39: 0: INFO: AWS Portal File Transfer is not installed on the system.
2017-09-21 13:01:39: 0: INFO: Start Job called - starting up Cinema 4D Batch plugin
2017-09-21 13:01:39: 0: INFO: Not enforcing a build of Cinema 4D
2017-09-21 13:01:39: 0: INFO: [C4D_PLUGINS_DIR] set to: \Rock\gfx_repo\PLUGINS\Cinema4D\R19;C:\Users\Admin\AppData\Local\Thinkbox\Deadline10\slave\gpu-1-instance-01\plugins\59c3aa1763a7f82830b53d73
2017-09-21 13:01:39: 0: INFO: Cinema 4D socket connection port: 63637
2017-09-21 13:01:39: 0: INFO: Parameters: -nogui “-redshift-gpu 2” “-redshift-gpu 3” “-DeadlineConnect 63637 468997550201”
2017-09-21 13:01:39: 0: INFO: Starting monitored managed process Cinema4DProcess
2017-09-21 13:01:39: 0: INFO: Stdout Redirection Enabled: True
2017-09-21 13:01:39: 0: INFO: Stdout Handling Enabled: True
2017-09-21 13:01:39: 0: INFO: Popup Handling Enabled: True
2017-09-21 13:01:39: 0: INFO: QT Popup Handling Enabled: False
2017-09-21 13:01:39: 0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: False
2017-09-21 13:01:39: 0: INFO: Using Process Tree: True
2017-09-21 13:01:39: 0: INFO: Hiding DOS Window: True
2017-09-21 13:01:39: 0: INFO: Creating New Console: False
2017-09-21 13:01:39: 0: INFO: Running as user: Admin
2017-09-21 13:01:39: 0: INFO: Executable: “C:\Program Files\MAXON\CINEMA 4D R19\Commandline.exe”
2017-09-21 13:01:39: 0: INFO: Argument: -nogui “-redshift-gpu 2” “-redshift-gpu 3” “-DeadlineConnect 63637 468997550201”
2017-09-21 13:01:39: 0: INFO: Full Command: “C:\Program Files\MAXON\CINEMA 4D R19\Commandline.exe” -nogui “-redshift-gpu 2” “-redshift-gpu 3” “-DeadlineConnect 63637 468997550201”
2017-09-21 13:01:39: 0: INFO: Startup Directory: “C:\Program Files\MAXON\CINEMA 4D R19”
2017-09-21 13:01:39: 0: INFO: Process Priority: BelowNormal
2017-09-21 13:01:39: 0: INFO: Process Affinity: default
2017-09-21 13:01:39: 0: INFO: Process is now running
2017-09-21 13:01:40: 0: STDOUT: Application start : 09/21/17 at 13:01:39
2017-09-21 13:01:40: 0: STDOUT: Executable : 64 Bit
2017-09-21 13:01:40: 0: STDOUT: Version / Build : 19.024 / RB209858
2017-09-21 13:01:40: 0: STDOUT: Debugger : not available
2017-09-21 13:01:40: 0: STDOUT: Memory model : release
2017-09-21 13:01:40: 0: STDOUT: Startup path : file:///C:/Program Files/MAXON/CINEMA 4D R19
2017-09-21 13:01:40: 0: STDOUT: Application path : file:///C:/Program Files/MAXON/CINEMA 4D R19/Commandline.exe
2017-09-21 13:01:40: 0: STDOUT: Application executable : file:///C:/Program Files/MAXON/CINEMA 4D R19/Commandline.exe
2017-09-21 13:01:40: 0: STDOUT: Resource path : file:///C:/Program Files/MAXON/CINEMA 4D R19/resource
2017-09-21 13:01:40: 0: STDOUT: Module path(s) : file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs
2017-09-21 13:01:40: 0: STDOUT: Temporary path : file:///C:/Users/Admin/AppData/Local/Temp
2017-09-21 13:01:40: 0: STDOUT: Prefs path : file:///C:/Users/Admin/AppData/Roaming/MAXON/CINEMA 4D R19_BFE04C39
2017-09-21 13:01:40: 0: STDOUT: Global Prefs path : file:///C:/Users/Admin/AppData/Roaming/MAXON
2017-09-21 13:01:40: 0: STDOUT: OS version : Windows 10, 64 Bit, Professional Edition (build 14393)
2017-09-21 13:01:40: 0: STDOUT: Processor : 16(32)x Intel Xeon CPU E5-2620 v4
2017-09-21 13:01:40: 0: STDOUT: Computer name : GPU-1
2017-09-21 13:01:40: 0: STDOUT: Thread Count : 32
2017-09-21 13:01:40: 0: STDOUT: Cpu Speed (MHz) : 2100.000
2017-09-21 13:01:40: 0: STDOUT: Application Type : Modular
2017-09-21 13:01:40: 0: STDOUT: Command line arguments : “-nogui” “-redshift-gpu 2” “-redshift-gpu 3” “-DeadlineConnect 63637 468997550201”
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/browser.xdl64 with module(s) net.maxon.c4d.browser
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/c4dplugin.xdl64 with module(s) net.maxon.c4dplugin net.maxon.c4d.c4dplugin
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/crashhandler.module.xdl64 with module(s) net.maxon.crashhandler
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/crypt.module.xdl64 with module(s) net.maxon.crypt
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/drawport.module.xdl64 with module(s) net.maxon.drawport
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/drawport_general.module.xdl64 with module(s) net.maxon.drawport_general
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/drawport_opengl.module.xdl64 with module(s) net.maxon.drawport_opengl
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/drawport_selector.module.xdl64 with module(s) net.maxon.drawport_selector
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/embree.module.xdl64 with module(s) net.maxon.embree
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/geom.module.xdl64 with module(s) net.maxon.geom
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/gui.module.xdl64 with module(s) net.maxon.gui
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/image.module.xdl64 with module(s) net.maxon.image
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/image_openexr.module.xdl64 with module(s) net.maxon.image_openexr
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/image_winmf.module.xdl64 with module(s) net.maxon.image_winmf
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/io_obj.xdl64 with module(s) net.maxon.c4d.io_obj
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/math.module.xdl64 with module(s) net.maxon.math
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/mesh.module.xdl64 with module(s) net.maxon.mesh
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/misc.module.xdl64 with module(s) net.maxon.misc
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/mkmodeler.xdl64 with module(s) net.maxon.c4d.mkmodeler
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/network.module.xdl64 with module(s) net.maxon.network
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/opencl.module.xdl64 with module(s) net.maxon.opencl
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/opensubdiv.module.xdl64 with module(s) net.maxon.opensubdiv
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/render.module.xdl64 with module(s) net.maxon.render
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/shaderbase.module.xdl64 with module(s) net.maxon.shaderbase
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/tessellation.module.xdl64 with module(s) net.maxon.tessellation
2017-09-21 13:01:40: 0: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R19/corelibs/xtensions.xdl64 with module(s) net.maxon.c4d.xtensions
2017-09-21 13:01:56: 0: STDOUT: OpenGL root context initialized
2017-09-21 13:01:56: 0: STDOUT: Vendor : NVIDIA Corporation (NVIDIA)
2017-09-21 13:01:56: 0: STDOUT: Renderer : GeForce GTX 1070/PCIe/SSE2
2017-09-21 13:01:56: 0: STDOUT: OpenGL version: 4.5.0 NVIDIA 384.94
2017-09-21 13:01:56: 0: STDOUT: Driver version: 384.94
2017-09-21 13:02:03: 0: STDOUT: OpenGL root context initialized
2017-09-21 13:02:03: 0: STDOUT: Vendor : VMware, Inc. (VMWARE)
2017-09-21 13:02:03: 0: STDOUT: Renderer : Gallium 0.4 on llvmpipe (LLVM 4.0, 256 bits)
2017-09-21 13:02:03: 0: STDOUT: OpenGL version: 3.3 (Core Profile) Mesa 17.0.1 (git-)
2017-09-21 13:02:03: 0: STDOUT: Driver version: 17.0.1 (git-)
2017-09-21 13:02:04: 0: STDOUT: Warning: Unknown arguments: -redshift-gpu 2 -redshift-gpu 3 -DeadlineConnect 63637 468997550201
2017-09-21 13:02:05: 0: WARNING: Monitored managed process Cinema4DProcess is no longer running
2017-09-21 13:02:05: 0: Done executing plugin command of type ‘Start Job’

=======================================================
Details

Date: 09/21/2017 13:02:05
Frames: 3
Elapsed Time: 00:00:00:30
Job Submit Date: 09/21/2017 13:01:26
Job User: mario
Average RAM Usage: 6699671552 (5%)
Peak RAM Usage: 7434788864 (6%)
Average CPU Usage: 14%
Peak CPU Usage: 17%
Used CPU Clocks (x10^6 cycles): 247058
Total CPU Clocks (x10^6 cycles): 1764697

=======================================================
Slave Information

Slave Name: GPU-1-instance-01
Version: v10.0.3.2 Release (072d054c6)
Operating System: Windows 10 Pro
Running As Service: No
Machine User: Admin
IP Address: 10.1.1.188
MAC Address: 0C:C4:7A:E4:23:86
CPU Architecture: x64
CPUs: 32
CPU Usage: 11%
Memory Usage: 6.9 GB / 127.9 GB (5%)
Free Disk Space: 25.327 GB
Video Card: LogMeIn Mirror Driver

I’ve noticed this line:

[C4D_PLUGINS_DIR] set to: \Rock\gfx_repo\PLUGINS\Cinema4D\R19;C:\Users\Admin\AppData\Local\Thinkbox\Deadline10\slave\gpu-1\plugins\59c3ab1663a7f8350cee2e68

C4D’s Env Var cant handle multiple paths, maybe that’s the problem?

Looks like a Maxon bug in R18: plugincafe.com/forum/forum_p … ?TID=13666 but it should be working if you are now using R19…ie: multiple paths should now be supported in R19 and onwards.

Looking at the log report, it does seem like the plugins and in particular, Redshift is just not being loaded here and then of course, it errors out with an unknown CLI flag for Redshift. Can you confirm that Redshift does indeed load correctly on this machine in GUI mode and loads the redshift plugin from this network directory: “\Rock\gfx_repo\PLUGINS\Cinema4D\R19” and you don’t have a duplicate install of it locally on this machine and its the latest version?

I’m on C4D Beta and just talked with them. Multiple paths still don’t work…

The plugin is not being loaded because I deleted the local Env Var on that node to see if Deadline would bring it. And I think it did because it shows it here [C4D_PLUGINS_DIR] set to: \Rock\gfx_repo\PLUGINS\Cinema4D\R19; but because the scripts append two paths, it’s only reading the last one C:\Users\Admin\AppData\Local\Thinkbox\Deadline10\slave\gpu-1\plugins\59c3ab1663a7f8350cee2e68, exactly because C4D Limitation.

Theres another Env Var in C4D: C4D_SCRIPTS_DIR, can you use that instead for this path? C:\Users\Admin\AppData\Local\Thinkbox\Deadline10\slave\gpu-1\plugins\59c3ab1663a7f8350cee2e68

Using another ENV VAR will just break for another user if they are using it. I guess options are for us to also report this outstanding bug to Maxon directly. Please do log it yourself as well with Maxon to gain more attention. Another option is to just use the non-Batch plugin for now, which should work just fine for any of your workflows.

Sure, I understand. I’ll report it as a bug and I’ve talked about it several times in the forum. I think they will address it soon.

Even in the non batch mode it happens. If I don’t setup the Evn Var on the machine it doesn’t find Redshift and XPArticles.

Can you please explain what’s the main difference between modes, Batch and non Batch. I have an idea but I’m not completely sure.

I really appreciate all your help.

I’ve now emailed all the guys I know in Maxon as well. Let’s see how that goes.

The main difference is that Batch plugin keeps C4D open between tasks, thereby making it more efficient in rendering frames, as it only has to open the app once and resolve plugins, scripts, presets and load the scene file + textures once. Non-batch is pure execute this in the command-line and give me the result.

Yes, you should always add the C4D_PLUGINS_DIR env var to your machines if you want to re-direct your instances of C4D to obtain plugins from a network located path. Deadline will respect this. If not present, C4D will search its internal app directory paths by default only.

Tks this was a big help to understand how stuff works under the hood.

I guess for now I can install Redshift and Xparticles locally on all machines instead of using a network path. I notice that not using the bach mode slows down the render and brings some other problems. I can’t seem to add more slaves once the render is going fro example.

Don’t want to keep asking questions this thread is way longer than it should be but I’ll go for another last one.

What is this path needed for? C:\Users\Admin\AppData\Local\Thinkbox\Deadline10\slave\gpu-1\plugins\59c3ab1663a7f8350cee2e68

Is it really needed for C4D?

This path is needed to tell C4D where has Slave copied down the custom C4D plugin when it picks up a C4D job from the Deadline queue. This path is added to C4D_PLUGINS_DIR, so we can bootstrap this pyp plugin via C4D automatically searching this file path and finding it. If we didn’t do this, then we would need to find some other kind of mechanism of telling C4D to search a file path and load any C4D plugins it finds in this path. We don’t know of any other such mechanism in C4D.

By custom plugin you mean the Cinema4DBatch.py?

Privacy | Site terms | Cookie preferences