# AWS Deadline Cloud for Cinema 4D
[](https://pypi.python.org/pypi/deadline-cloud-for-cinema-4d)
[](https://pypi.python.org/pypi/deadline-cloud-for-cinema-4d)
[](https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/blob/mainline/LICENSE)
AWS Deadline Cloud for Cinema 4D is a python package that allows users to create [Deadline Cloud][deadline-cloud] jobs from within Cinema 4D. It provides both the implementation of a Cinema 4D extension for your workstation that helps you offload the computation for your rendering workloads
to Deadline Cloud to free up your workstation's compute for other tasks, and the implementation of a command-line
adaptor application based on the [Open Job Description (OpenJD) Adaptor Runtime][openjd-adaptor-runtime] that improves Deadline Cloud's
ability to run Cinema 4D efficiently on your render farm.
[deadline-cloud]: https://docs.aws.amazon.com/deadline-cloud/latest/userguide/what-is-deadline-cloud.html
[deadline-cloud-client]: https://github.com/aws-deadline/deadline-cloud
[openjd-template]: https://github.com/OpenJobDescription/openjd-specifications/wiki/2023-09-Template-Schemas
[openjd-adaptor-runtime]: https://github.com/OpenJobDescription/openjd-adaptor-runtime-for-python
[openjd-adaptor-runtime-lifecycle]: https://github.com/OpenJobDescription/openjd-adaptor-runtime-for-python/blob/release/README.md#adaptor-lifecycle
[service-managed-fleets]: https://docs.aws.amazon.com/deadline-cloud/latest/userguide/smf-manage.html
[default-queue-environment]: https://docs.aws.amazon.com/deadline-cloud/latest/userguide/create-queue-environment.html#conda-queue-environment
[deadline-cloud-submitter]: https://docs.aws.amazon.com/deadline-cloud/latest/userguide/submitter.html
[deadline-cloud-monitor]: https://docs.aws.amazon.com/deadline-cloud/latest/userguide/monitor-onboarding.html
[usage-based-licensing]: https://aws.amazon.com/deadline-cloud/features/
## Compatibility
This library requires:
1. Cinema 4D 2024 - 2025
1. Python 3.9 or higher; but Python 3.11 is recommended as this is the version Cinema 4D uses natively.
1. Windows or macOS operating system for job submission and Windows operating system for job rendering. There are some instructions below on how to setup the adaptors for job rendering on Linux but they are experimental.
## Getting Started
The Cinema 4D integration for Deadline Cloud has two components that you will need to install:
1. The Cinema 4D submitter extension must be installed on the workstation that you will use to submit jobs; and
2. The Cinema 4D adaptor must be installed on all of your Deadline Cloud worker hosts that will be running the Cinema 4D jobs that you submit.
Before submitting any large, complex, or otherwise compute-heavy Cinema 4D render jobs to your farm using the submitter and adaptor that you
set up, we strongly recommend that you construct a simple test scene that can be rendered quickly and submit renders of that scene to your farm to ensure that your setup is functioning correctly.
## Submitter
The Cinema 4D submitter extension creates a button in Cinema 4D (`Extensions` > `AWS Deadline Cloud Submitter`) that can be used to submit jobs to Deadline Cloud. Clicking this button reveals an interface to submit a job to Deadline Cloud.
It automatically determines the files required based on the loaded scene, allows the user to specify render options, builds an
[Open Job Description template][openjd-template] that defines the workflow, and submits the job to the farm and queue of your choosing.
There are two installation options:
1. Windows-only: Install the submitter using the official Deadline Cloud submitter installer for Windows
2. Windows or Mac: Manually install the submitter
For most setups, you will also need to install the [Deadline Cloud monitor](deadline-cloud-monitor).
## Install the submitter using the official Deadline Cloud submitter installer
The [official Deadline Cloud submitter installer](deadline-cloud-submitter) for Windows includes the Cinema 4D submitter. After installing, you can access the submitter in the Cinema 4D interface via `Extensions` > `AWS Deadline Cloud Submitter`.
## Manually installing the submitter
Manual installation is supported on Windows and Mac.
### Manually install the submitter
#### Windows
In Windows `cmd`
```
set SUBMITTER_LOCATION=%APPDATA%\DeadlineCloudSubmitter
"C:\Program Files\Maxon Cinema 4D 2025\resource\modules\python\libs\win64\python.exe" -m ensurepip
"C:\Program Files\Maxon Cinema 4D 2025\resource\modules\python\libs\win64\python.exe" -m pip install deadline-cloud-for-cinema-4d "deadline[gui]" -t %SUBMITTER_LOCATION%
md %SUBMITTER_LOCATION%\cinema_4d_plugins
curl https://raw.githubusercontent.com/aws-deadline/deadline-cloud-for-cinema-4d/refs/heads/mainline/deadline_cloud_extension/DeadlineCloud.pyp -o %SUBMITTER_LOCATION%\cinema_4d_plugins\DeadlineCloud.pyp
if not defined C4DPYTHONPATH311 (setx C4DPYTHONPATH311 %SUBMITTER_LOCATION%) else (setx C4DPYTHONPATH311 %SUBMITTER_LOCATION%;%C4DPYTHONPATH311%)
if not defined g_additionalModulePath (setx g_additionalModulePath %SUBMITTER_LOCATION%\cinema_4d_plugins) else (setx g_additionalModulePath %SUBMITTER_LOCATION%\cinema_4d_plugins;%g_additionalModulePath%)
```
Next time you open Cinema 4D and you load a scene, click on `Extensions` > `AWS Deadline Cloud Submitter` to view the submitter.
#### Mac
In a Mac terminal:
```
export SUBMITTER_LOCATION="/Users/$USER/DeadlineCloudSubmitter/"
mkdir $SUBMITTER_LOCATION
python3 -m ensurepip
python3 -m pip install deadline-cloud-for-cinema-4d "deadline[gui]" -t $SUBMITTER_LOCATION
mkdir $SUBMITTER_LOCATION/cinema_4d_plugins
curl https://raw.githubusercontent.com/aws-deadline/deadline-cloud-for-cinema-4d/refs/heads/mainline/deadline_cloud_extension/DeadlineCloud.pyp -o $SUBMITTER_LOCATION/cinema_4d_plugins/DeadlineCloud.pyp
echo \#\!/bin/zsh > ~/Desktop/Cinema4D.command
echo export C4DPYTHONPATH311=$SUBMITTER_LOCATION:\$C4DPYTHONPATH311 >> ~/Desktop/Cinema4D.command
echo export g_additionalModulePath=$SUBMITTER_LOCATION/cinema_4d_plugins:\$g_additionalModulePath >> ~/Desktop/Cinema4D.command
echo /Applications/Maxon\\ Cinema\\ 4D\\ 2025/Cinema\\ 4D.app/Contents/MacOS/Cinema\\ 4D >> ~/Desktop/Cinema4D.command
chmod +x ~/Desktop/Cinema4D.command
```
To open Cinema 4D, click `Cinema4D.command` on your desktop. After you load a scene, click on `Extensions` > `AWS Deadline Cloud Submitter` to view the submitter.
## Adaptor
Jobs created by the Cinema 4D submitter require the adaptor to be installed on your worker hosts.
The adaptor application is a command-line Python-based application that enhances the functionality of Cinema 4D for running within a render farm like Deadline Cloud. Its primary purpose for existing is to add a "sticky rendering" functionality where a single process instance of Cinema 4D is able to load the scene file and then dynamically be instructed to perform desired renders without needing to close and re-launch Cinema 4D between them. It also has additional benefits such as support for path mapping, and reporting the progress of your render to Deadline Cloud. The alternative to "sticky rendering" is that Cinema 4D would need to be run separately for each render that is done, and close afterwards.
Some scenes can take 10's of minutes just to load for rendering, so being able to keep the application open and loaded between
renders can be a significant time-saving optimization; particularly when the render itself is quick.
Both fleet types in Deadline Cloud support the Cinema 4D adaptor:
1. Service managed fleets
2. Customer managed fleets
The Cinema 4D integration for Deadline Cloud is supported on Windows fleets (service managed and customer managed).
Linux support is experimental and can only be done on customer managed fleets.
### Service managed fleets
On [service managed fleets](service-managed-fleets), the Cinema 4D adaptor is automatically available via the `deadline-cloud` Conda channel with the [default Queue Environment][default-queue-environment].
### Customer managed fleets
There are two options for setting up the Cinema 4D adaptor on customer managed fleets:
1. Manually installing on worker hosts
2. Using customer-managed Conda packages
#### Manually installing on worker hosts
Both the installed adaptor and the Cinema 4D executable must be available on the PATH of the user that will be running your jobs.
You can also set the `C4D_COMMANDLINE_EXECUTABLE` to point to the Cinema 4D executable. The adaptor must still be on the PATH.
The adaptor can be installed by the standard python packaging mechanisms:
```sh
$ pip install deadline-cloud-for-cinema-4d
```
After installation and adding it to the PATH it can then be used as a command line tool:
```sh
$ cinema4d-openjd --help
```
For more information on the commands the OpenJD adaptor runtime provides, see [here][openjd-adaptor-runtime-lifecycle].
#### Using customer-managed Conda packages
Cinema 4D Conda packages are available in the "deadline-cloud" Conda channel on service managed Windows fleets.
However, if you prefer, you can build the Cinema 4D Conda packages yourself. There are conda recipes in our samples Github repository for [`cinema4d-2025` on Windows](https://github.com/aws-deadline/deadline-cloud-samples/tree/mainline/conda_recipes/cinema4d-2025) and
[`cinema4d-openjd` on Windows and Linux](https://github.com/aws-deadline/deadline-cloud-samples/tree/mainline/conda_recipes/cinema4d-openjd).
For instructions on building conda recipes on Deadline Cloud, see [this article](https://aws.amazon.com/blogs/media/create-a-conda-package-and-channel-for-aws-deadline-cloud/).
Though it refers to Blender, the process applies to Cinema 4D recipes as well.
## Worker Licensing for Cinema 4D
### Service Managed Fleets
[Usage based licensing](usage-based-licensing) for Cinema 4D 2024 and 2025 is available on Deadline Cloud service managed fleets with no additional setup.
If you prefer to use your own licensing for service managed fleets, you can also [connect service-managed fleets to a custom license server](https://docs.aws.amazon.com/deadline-cloud/latest/developerguide/smf-byol.html).
### Customer Managed Fleets
You can use usage based licensing on customer managed fleets by [connecting them to a license endpoint](https://docs.aws.amazon.com/deadline-cloud/latest/developerguide/cmf-ubl.html).
You can also use your own licensing for customer managed fleets.
## Viewing the Job Bundle that will be submitted
To submit a job, the submitter first generates a [Job Bundle][job-bundle], and then uses functionality from the
[Deadline client library][deadline-cloud-client] package to submit the Job Bundle to your render farm to run. If you would like to see
the job that will be submitted to your farm, then you can use the "Export Bundle" button in the submitter to export the
Job Bundle to a location of your choice. If you want to submit the job from the export, rather than through the
submitter plug-in then you can use the [Deadline Cloud application][deadline-cloud-client] to submit that bundle to your farm.
[job-bundle]: https://docs.aws.amazon.com/deadline-cloud/latest/developerguide/build-job-bundle.html
## Security
We take all security reports seriously. When we receive such reports, we will
investigate and subsequently address any potential vulnerabilities as quickly
as possible. If you discover a potential security issue in this project, please
notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/)
or directly via email to [AWS Security](aws-security@amazon.com). Please do not
create a public GitHub issue in this project.
## Telemetry
See [telemetry](https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/blob/release/docs/telemetry.md) for more information.
## Troubleshooting
### Additional Python Libraries in the submitter
Some versions of Cinema 4D ( e.g. `Cinema 4D 2024.1.0`) have been found to be missing some libraries key to Deadline Cloud requirements ; in later versions such as `2024.4.0` this has been resolved.
A missing library error will manifest in errors that can be visible from the **Python** section of the **Extensions > Console** UI. These typically look like:
```
PySide6/__init__.py: Unable to import Shiboken from ...
```
To remedy these errors, you can switch to a later version of Cinema 4D which resolves the missing libraries, or you can manually add them specifically to the Cinema 4D python module, e.g in Windows it will be something like:
```
"C:\Program Files\Maxon Cinema 4D 2024\resource\modules\python\libs\win64\python.exe"-m ensurepip
"C:\Program Files\Maxon Cinema 4D 2024\resource\modules\python\libs\win64\python.exe"-m pip install MISSING_MODULE
```
## License
This project is licensed under the Apache-2.0 License.
Raw data
{
"_id": null,
"home_page": null,
"name": "deadline-cloud-for-cinema-4d",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.9",
"maintainer_email": null,
"keywords": null,
"author": "Amazon Web Services",
"author_email": null,
"download_url": "https://files.pythonhosted.org/packages/99/ba/96c9d1102878c0169f8b6ba3080d0495c0eeb95c5a83d8c8140799ed6532/deadline_cloud_for_cinema_4d-0.7.1.tar.gz",
"platform": null,
"description": "# AWS Deadline Cloud for Cinema 4D\n\n[](https://pypi.python.org/pypi/deadline-cloud-for-cinema-4d)\n[](https://pypi.python.org/pypi/deadline-cloud-for-cinema-4d)\n[](https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/blob/mainline/LICENSE)\n\nAWS Deadline Cloud for Cinema 4D is a python package that allows users to create [Deadline Cloud][deadline-cloud] jobs from within Cinema 4D. It provides both the implementation of a Cinema 4D extension for your workstation that helps you offload the computation for your rendering workloads\nto Deadline Cloud to free up your workstation's compute for other tasks, and the implementation of a command-line\nadaptor application based on the [Open Job Description (OpenJD) Adaptor Runtime][openjd-adaptor-runtime] that improves Deadline Cloud's\nability to run Cinema 4D efficiently on your render farm.\n\n[deadline-cloud]: https://docs.aws.amazon.com/deadline-cloud/latest/userguide/what-is-deadline-cloud.html\n[deadline-cloud-client]: https://github.com/aws-deadline/deadline-cloud\n[openjd-template]: https://github.com/OpenJobDescription/openjd-specifications/wiki/2023-09-Template-Schemas\n[openjd-adaptor-runtime]: https://github.com/OpenJobDescription/openjd-adaptor-runtime-for-python\n[openjd-adaptor-runtime-lifecycle]: https://github.com/OpenJobDescription/openjd-adaptor-runtime-for-python/blob/release/README.md#adaptor-lifecycle\n[service-managed-fleets]: https://docs.aws.amazon.com/deadline-cloud/latest/userguide/smf-manage.html\n[default-queue-environment]: https://docs.aws.amazon.com/deadline-cloud/latest/userguide/create-queue-environment.html#conda-queue-environment\n[deadline-cloud-submitter]: https://docs.aws.amazon.com/deadline-cloud/latest/userguide/submitter.html\n[deadline-cloud-monitor]: https://docs.aws.amazon.com/deadline-cloud/latest/userguide/monitor-onboarding.html\n[usage-based-licensing]: https://aws.amazon.com/deadline-cloud/features/\n\n## Compatibility\n\nThis library requires:\n\n1. Cinema 4D 2024 - 2025\n1. Python 3.9 or higher; but Python 3.11 is recommended as this is the version Cinema 4D uses natively.\n1. Windows or macOS operating system for job submission and Windows operating system for job rendering. There are some instructions below on how to setup the adaptors for job rendering on Linux but they are experimental.\n\n## Getting Started\n\nThe Cinema 4D integration for Deadline Cloud has two components that you will need to install:\n\n1. The Cinema 4D submitter extension must be installed on the workstation that you will use to submit jobs; and\n2. The Cinema 4D adaptor must be installed on all of your Deadline Cloud worker hosts that will be running the Cinema 4D jobs that you submit.\n\nBefore submitting any large, complex, or otherwise compute-heavy Cinema 4D render jobs to your farm using the submitter and adaptor that you\nset up, we strongly recommend that you construct a simple test scene that can be rendered quickly and submit renders of that scene to your farm to ensure that your setup is functioning correctly.\n\n## Submitter\n\nThe Cinema 4D submitter extension creates a button in Cinema 4D (`Extensions` > `AWS Deadline Cloud Submitter`) that can be used to submit jobs to Deadline Cloud. Clicking this button reveals an interface to submit a job to Deadline Cloud.\nIt automatically determines the files required based on the loaded scene, allows the user to specify render options, builds an\n[Open Job Description template][openjd-template] that defines the workflow, and submits the job to the farm and queue of your choosing.\n\nThere are two installation options:\n1. Windows-only: Install the submitter using the official Deadline Cloud submitter installer for Windows\n2. Windows or Mac: Manually install the submitter\n\nFor most setups, you will also need to install the [Deadline Cloud monitor](deadline-cloud-monitor).\n\n## Install the submitter using the official Deadline Cloud submitter installer\n\nThe [official Deadline Cloud submitter installer](deadline-cloud-submitter) for Windows includes the Cinema 4D submitter. After installing, you can access the submitter in the Cinema 4D interface via `Extensions` > `AWS Deadline Cloud Submitter`.\n\n## Manually installing the submitter\n\nManual installation is supported on Windows and Mac.\n\n### Manually install the submitter\n\n#### Windows\n\nIn Windows `cmd`\n```\nset SUBMITTER_LOCATION=%APPDATA%\\DeadlineCloudSubmitter\n\"C:\\Program Files\\Maxon Cinema 4D 2025\\resource\\modules\\python\\libs\\win64\\python.exe\" -m ensurepip\n\"C:\\Program Files\\Maxon Cinema 4D 2025\\resource\\modules\\python\\libs\\win64\\python.exe\" -m pip install deadline-cloud-for-cinema-4d \"deadline[gui]\" -t %SUBMITTER_LOCATION%\nmd %SUBMITTER_LOCATION%\\cinema_4d_plugins\ncurl https://raw.githubusercontent.com/aws-deadline/deadline-cloud-for-cinema-4d/refs/heads/mainline/deadline_cloud_extension/DeadlineCloud.pyp -o %SUBMITTER_LOCATION%\\cinema_4d_plugins\\DeadlineCloud.pyp\nif not defined C4DPYTHONPATH311 (setx C4DPYTHONPATH311 %SUBMITTER_LOCATION%) else (setx C4DPYTHONPATH311 %SUBMITTER_LOCATION%;%C4DPYTHONPATH311%)\nif not defined g_additionalModulePath (setx g_additionalModulePath %SUBMITTER_LOCATION%\\cinema_4d_plugins) else (setx g_additionalModulePath %SUBMITTER_LOCATION%\\cinema_4d_plugins;%g_additionalModulePath%)\n```\n\nNext time you open Cinema 4D and you load a scene, click on `Extensions` > `AWS Deadline Cloud Submitter` to view the submitter.\n\n#### Mac\n\nIn a Mac terminal:\n```\nexport SUBMITTER_LOCATION=\"/Users/$USER/DeadlineCloudSubmitter/\"\nmkdir $SUBMITTER_LOCATION\npython3 -m ensurepip\npython3 -m pip install deadline-cloud-for-cinema-4d \"deadline[gui]\" -t $SUBMITTER_LOCATION\nmkdir $SUBMITTER_LOCATION/cinema_4d_plugins\ncurl https://raw.githubusercontent.com/aws-deadline/deadline-cloud-for-cinema-4d/refs/heads/mainline/deadline_cloud_extension/DeadlineCloud.pyp -o $SUBMITTER_LOCATION/cinema_4d_plugins/DeadlineCloud.pyp\necho \\#\\!/bin/zsh > ~/Desktop/Cinema4D.command\necho export C4DPYTHONPATH311=$SUBMITTER_LOCATION:\\$C4DPYTHONPATH311 >> ~/Desktop/Cinema4D.command\necho export g_additionalModulePath=$SUBMITTER_LOCATION/cinema_4d_plugins:\\$g_additionalModulePath >> ~/Desktop/Cinema4D.command\necho /Applications/Maxon\\\\ Cinema\\\\ 4D\\\\ 2025/Cinema\\\\ 4D.app/Contents/MacOS/Cinema\\\\ 4D >> ~/Desktop/Cinema4D.command\nchmod +x ~/Desktop/Cinema4D.command\n```\n\nTo open Cinema 4D, click `Cinema4D.command` on your desktop. After you load a scene, click on `Extensions` > `AWS Deadline Cloud Submitter` to view the submitter.\n\n## Adaptor\n\nJobs created by the Cinema 4D submitter require the adaptor to be installed on your worker hosts.\n\nThe adaptor application is a command-line Python-based application that enhances the functionality of Cinema 4D for running within a render farm like Deadline Cloud. Its primary purpose for existing is to add a \"sticky rendering\" functionality where a single process instance of Cinema 4D is able to load the scene file and then dynamically be instructed to perform desired renders without needing to close and re-launch Cinema 4D between them. It also has additional benefits such as support for path mapping, and reporting the progress of your render to Deadline Cloud. The alternative to \"sticky rendering\" is that Cinema 4D would need to be run separately for each render that is done, and close afterwards.\nSome scenes can take 10's of minutes just to load for rendering, so being able to keep the application open and loaded between\nrenders can be a significant time-saving optimization; particularly when the render itself is quick.\n\nBoth fleet types in Deadline Cloud support the Cinema 4D adaptor:\n1. Service managed fleets\n2. Customer managed fleets\n\nThe Cinema 4D integration for Deadline Cloud is supported on Windows fleets (service managed and customer managed).\nLinux support is experimental and can only be done on customer managed fleets.\n\n### Service managed fleets\n\nOn [service managed fleets](service-managed-fleets), the Cinema 4D adaptor is automatically available via the `deadline-cloud` Conda channel with the [default Queue Environment][default-queue-environment].\n\n### Customer managed fleets\n\nThere are two options for setting up the Cinema 4D adaptor on customer managed fleets:\n1. Manually installing on worker hosts\n2. Using customer-managed Conda packages\n\n#### Manually installing on worker hosts\n\nBoth the installed adaptor and the Cinema 4D executable must be available on the PATH of the user that will be running your jobs.\n\nYou can also set the `C4D_COMMANDLINE_EXECUTABLE` to point to the Cinema 4D executable. The adaptor must still be on the PATH.\n\nThe adaptor can be installed by the standard python packaging mechanisms:\n```sh\n$ pip install deadline-cloud-for-cinema-4d\n```\n\nAfter installation and adding it to the PATH it can then be used as a command line tool:\n```sh\n$ cinema4d-openjd --help\n```\n\nFor more information on the commands the OpenJD adaptor runtime provides, see [here][openjd-adaptor-runtime-lifecycle].\n\n#### Using customer-managed Conda packages\n\nCinema 4D Conda packages are available in the \"deadline-cloud\" Conda channel on service managed Windows fleets.\n\nHowever, if you prefer, you can build the Cinema 4D Conda packages yourself. There are conda recipes in our samples Github repository for [`cinema4d-2025` on Windows](https://github.com/aws-deadline/deadline-cloud-samples/tree/mainline/conda_recipes/cinema4d-2025) and\n[`cinema4d-openjd` on Windows and Linux](https://github.com/aws-deadline/deadline-cloud-samples/tree/mainline/conda_recipes/cinema4d-openjd).\n\nFor instructions on building conda recipes on Deadline Cloud, see [this article](https://aws.amazon.com/blogs/media/create-a-conda-package-and-channel-for-aws-deadline-cloud/).\nThough it refers to Blender, the process applies to Cinema 4D recipes as well.\n\n## Worker Licensing for Cinema 4D\n\n### Service Managed Fleets\n\n[Usage based licensing](usage-based-licensing) for Cinema 4D 2024 and 2025 is available on Deadline Cloud service managed fleets with no additional setup.\n\nIf you prefer to use your own licensing for service managed fleets, you can also [connect service-managed fleets to a custom license server](https://docs.aws.amazon.com/deadline-cloud/latest/developerguide/smf-byol.html).\n\n### Customer Managed Fleets\n\nYou can use usage based licensing on customer managed fleets by [connecting them to a license endpoint](https://docs.aws.amazon.com/deadline-cloud/latest/developerguide/cmf-ubl.html).\n\nYou can also use your own licensing for customer managed fleets.\n\n## Viewing the Job Bundle that will be submitted\n\nTo submit a job, the submitter first generates a [Job Bundle][job-bundle], and then uses functionality from the\n[Deadline client library][deadline-cloud-client] package to submit the Job Bundle to your render farm to run. If you would like to see\nthe job that will be submitted to your farm, then you can use the \"Export Bundle\" button in the submitter to export the\nJob Bundle to a location of your choice. If you want to submit the job from the export, rather than through the\nsubmitter plug-in then you can use the [Deadline Cloud application][deadline-cloud-client] to submit that bundle to your farm.\n\n[job-bundle]: https://docs.aws.amazon.com/deadline-cloud/latest/developerguide/build-job-bundle.html\n\n## Security\n\nWe take all security reports seriously. When we receive such reports, we will\ninvestigate and subsequently address any potential vulnerabilities as quickly\nas possible. If you discover a potential security issue in this project, please\nnotify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/)\nor directly via email to [AWS Security](aws-security@amazon.com). Please do not\ncreate a public GitHub issue in this project.\n\n## Telemetry\n\nSee [telemetry](https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/blob/release/docs/telemetry.md) for more information.\n\n## Troubleshooting\n\n### Additional Python Libraries in the submitter\n\nSome versions of Cinema 4D ( e.g. `Cinema 4D 2024.1.0`) have been found to be missing some libraries key to Deadline Cloud requirements ; in later versions such as `2024.4.0` this has been resolved.\n\nA missing library error will manifest in errors that can be visible from the **Python** section of the **Extensions > Console** UI. These typically look like:\n\n```\nPySide6/__init__.py: Unable to import Shiboken from ...\n```\n\nTo remedy these errors, you can switch to a later version of Cinema 4D which resolves the missing libraries, or you can manually add them specifically to the Cinema 4D python module, e.g in Windows it will be something like:\n\n```\n\"C:\\Program Files\\Maxon Cinema 4D 2024\\resource\\modules\\python\\libs\\win64\\python.exe\"-m ensurepip\n\"C:\\Program Files\\Maxon Cinema 4D 2024\\resource\\modules\\python\\libs\\win64\\python.exe\"-m pip install MISSING_MODULE\n```\n\n## License\n\nThis project is licensed under the Apache-2.0 License.\n",
"bugtrack_url": null,
"license": null,
"summary": "AWS Deadline Cloud for Cinema 4D",
"version": "0.7.1",
"project_urls": {
"Homepage": "https://github.com/aws-deadline/deadline-cloud-for-cinema-4d",
"Source": "https://github.com/aws-deadline/deadline-cloud-for-cinimema-4d"
},
"split_keywords": [],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "5859d0aa5a71d4a1c92e3233b3a28284d1058d399a3dfd8c8acb00ae962cbca2",
"md5": "6fc7920032d097068f44b332b70df16b",
"sha256": "fcc414556f20f69de6df0495caa49da0cc4699b9fb9233579ac6700ed7b4c14f"
},
"downloads": -1,
"filename": "deadline_cloud_for_cinema_4d-0.7.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "6fc7920032d097068f44b332b70df16b",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9",
"size": 43678,
"upload_time": "2025-02-05T02:51:50",
"upload_time_iso_8601": "2025-02-05T02:51:50.448497Z",
"url": "https://files.pythonhosted.org/packages/58/59/d0aa5a71d4a1c92e3233b3a28284d1058d399a3dfd8c8acb00ae962cbca2/deadline_cloud_for_cinema_4d-0.7.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "99ba96c9d1102878c0169f8b6ba3080d0495c0eeb95c5a83d8c8140799ed6532",
"md5": "efa7e779d09eb2ee12d21bc9d03376a1",
"sha256": "7b087853ff3da64f08a6307753566b9ee9ed8a8262208bcb8825db3e51720178"
},
"downloads": -1,
"filename": "deadline_cloud_for_cinema_4d-0.7.1.tar.gz",
"has_sig": false,
"md5_digest": "efa7e779d09eb2ee12d21bc9d03376a1",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9",
"size": 33826,
"upload_time": "2025-02-05T02:51:52",
"upload_time_iso_8601": "2025-02-05T02:51:52.381792Z",
"url": "https://files.pythonhosted.org/packages/99/ba/96c9d1102878c0169f8b6ba3080d0495c0eeb95c5a83d8c8140799ed6532/deadline_cloud_for_cinema_4d-0.7.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-02-05 02:51:52",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "aws-deadline",
"github_project": "deadline-cloud-for-cinema-4d",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "deadline-cloud-for-cinema-4d"
}
JSON
