Bug: Adobe Substance 3D Materials fail to render on Linux

[joel-wong-aws]

Describe the bug

When using Adobe Substance 3D Materials in Cinema 4D on Linux, rendering fails immediately with the error

Commandline: ./modules/io_substance/source/substance_framework/src/details/detailsengine.cpp:794: SubstanceAir::Details::Engine::Context::Context(SubstanceAir::Details::Engine&, SubstanceAir::RenderCallbacks*): Assertion `res==0' failed

or

/home/job-user/.conda/envs/hashname_f538d97c5a610d645f5c2e0c/Lib/deadline/cinema4d_adaptor/Cinema4DAdaptor/adaptor.sh: line 44: 10832 Segmentation fault      (core dumped) $C4DEXE ${ARGS[*]}

Workaround

If you use Adobe Substance 3D Materials in your scenes, please submit to Windows workers instead of Linux workers.

Reproduction Steps

This affects any scene that uses Adobe Substance 3D Materials.

Environment

1. Operating system (e.g. Windows Server 2022; Amazon Linux 2023; etc.): Amazon Linux 2023 workers (submission from Windows or Mac)
2. Version of Cinema 4D: 2025.3.1 and later
3. Version of Redshift: 2025.6.0 and later
4. Version of this package: Affects all versions of this package
5. If this is from a version installed by the Deadline Cloud Submitter installer, then what version of the submitter installer? Affects all installer versions

[joel-wong-aws]

We have reproduced this issue outside of Deadline Cloud, including directly using the Cinema 4D Commandline on Rocky 9 Linux. It appears to be a bug in Cinema 4D on Linux. We have filed a bug report with Maxon about this issue. If you use Substance 3D Materials, you can submit to Windows workers to work around the issue. Unfortunately, Maxon has not provided us a timeline for resolution of this issue. If you are affected by this issue, please 👍the issue so that we can inform Maxon about the number of customers impacted by this.

[joel-wong-aws]

In Cinema 4D 2026 on Linux, the behaviour with substance materials has changed. Scenes may now freeze when substance materials are included. To prevent tasks from becoming stuck, we recommend you use the task run timeouts feature under "Job-specific settings." A reasonable default timeout is two times the expected render time.

[joel-wong-aws]

The behaviour has changed in the latest Cinema 4D 2026.1.3 release with Redshift 2026.3.0. When scenes include substance materials, they will now fail with an error like:

/home/job-user/.conda/envs/hashname_f538d97c5a610d645f5c2e0c/Lib/deadline/cinema4d_adaptor/Cinema4DAdaptor/adaptor.sh: line 44: 10832 Segmentation fault      (core dumped) $C4DEXE ${ARGS[*]}

We continue to work with Maxon to resolve this issue.