We are having a small problem when rendering C4D + Redshift jobs. I’m not sure if this has anything to do with Deadline but maybe someone can help.
We have Redshift installed on a centralized network folder. And we set Evn Var for both Maya and Cinema 4D.
With Maya we have “no problems” and with Cinema the Env Var setup (C4D_PLUGINS_DIR) also works on the workstations, that is, when we launch C4D it sees the Env Var and loads Redshift.
But that doesn’t happen if we submit a job through Deadline. Is the submitted using that Env Var?
We are using Win 7 and 10 + C4D R18 latest update.
The new Deadline C4DBatch plugin relies on the “C4D_PLUGINS_DIR” env var, so if you are adding paths to this env var, make sure you “append” to this env and not overwrite it.
I should have asked you actually. Does the latest version of Deadline supports C4D19? In the Configure Plugins Window I can only see C4D 18 in my version ( 9.0.6.1 Release).
Ah! Now it’s down to us overriding that directory. I’d seen this in another thread but it didn’t click in my brain at the time, but this is where we’re running astray:
I think our problem here is that GetProcessEnvironmentVariable() is blank because it’s not checking the Sandbox’s environment (which should be around since you set it system-wide), it’s checking what would be set in the Override Environment Variables section. This should be an easy fix, we just have to include the system’s variables as well.
What’s the exact version of Deadline you’re on? I should be able to patch this pretty quickly by just putting os.environ[‘C4D_PLUGINS_DIR’] in place of GetProcessEnvironmentVariable() and add an import os line at the top.