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. script that might be used to apply various ENV VARs AND then startup the app in question such as C4D). 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. This “context” level is essentially applying it at “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. 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. ![]() ![]() Typically, ENV VARs are set either at machine level, user level or process level. “/plugins/Cinema4DBatch/Cinema4DBatch.py” Ok, see attached for single py file which should unzip and overwrite the same named file in your Cinema4DBatch plugin directory on your repo:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |