Bug: OCIO or colorspace outputs wrong with 32-bit .EXR

[mlupo-hims]

Describe the bug

Recently, rendering a 32-bit EXR through a Service-Managed fleet in AWS Deadline cloud results in an output that is different from a local output in terms of rendered colors.

I suspect this is due to recent changes in #508 and #535 - I further suspect this may be due to recent changes on the service-managed or adaptor side of things as it occurs when testing multiple workstations using submitter versions with 0.12.2, 0.12.1, and possibly 0.11.4.

This appears to occur with both Physical renderer and Redshift. I appreciate any help in solving this for our pipeline!

Individual .exr files picture above can be found here: Local Render - AWS Deadline Cloud Render

Expected Behaviour

Deadline output of 32-bit .exrs should result in colors identical to local rendering.

Current Behaviour

• Incorrect colors occur with 32-bit .exr output, but do not occur with 8-bit png renders.
• This appears to occur with both tile and non-tile renders.
• This occurs when rendering to a regular image, as well as multi-pass images.

These are the current C4D default color settings used and tested:

Render Space: ACEScg
View Transform (Project): ACES 1.0 SDR-video
View Transform (Thumbnails): ACES 1.0 SDR-video
Display Space: sRGB
OpenColorIO Config: $OCIO
OpenColorIO File Rules: Yes

Reproduction Steps

1. Start a new C4D default project, or use this sample file I have been using.
2. Add Geometry and change output to 32-bit .exr
3. Submit to an AWS Deadline fleet and let run, and render a local copy
4. Download output and compare versions.

Environment

My Specs/environment

1. Operating system: MacOS Tahoe 26.6.2
2. Cinema 4D: 2026.3.3
3. The entire contents of the About panel:

AWS Deadline Cloud Submitter Information

submitter name: Cinema4D
submitter package name: deadline-cloud-for-cinema4d
submitter package version: 0.12.2
host application name: Cinema 4D
host application version: '2026303'
additional info:
release date: August 24, 2026
deadline dep versions:
deadline: 0.60.4
boto3: 1.43.71
click: 8.4.2
deadline-job-attachments: 0.1.3
psutil: 7.2.2
pyyaml: 6.0.3
qtpy: 2.4.3
typing-extensions: 4.16.0
botocore: 1.43.71
pyside6-essentials: 6.8.3
os name: macOS
os version: 26.6.2
os architecture: arm64
python version: 3.11.4
qt version: 6.10.3

4. Renderer used: Redshift 2026.3.0, also occurs with Physical renderer. Testing samples use Redshift.
5. Fleet configuration: Windows Spot and on-demand instances, GPU chips: a10g, l4

Logs

hims-creative farm_Spot-Instance-hims-creative queue_session-39f82357324741fbb901f928739db69c.log

[karthikbekalp]

Thanks for the detailed bug report. We really appreciate that as this can help us fix the issue quickly.

We will actively try to prioritize this issue but unfortunately, we cannot give a particular timeline for when we can fix.

[karthikbekalp]

and possibly 0.11.4.

The colour changes were merged in 0.12.1 so the workaround that I can suggest right now would be to use 0.11.4 while submitting the job to still get the correct colours.

[mlupo-hims]

Hi Karthik, thanks for taking a look!

I wanted to double-check my testing of 0.11.4 so I ran another render today with it.
My cube render test still finished with the darker colors.

I also tried using the Conda channel "deadline-cloud" instead of "deadline-cloud-v2" but found no difference. I'm afraid I lack the technical knowledge currently to create my own Conda channel with the 0.11.4 adaptor and test further.

I may be wrong but I'm assuming agnostic of the submitter I use, the Service-Managed fleet is configuring and running the newest release of the C4D adaptor still.

Submitter about page:

AWS Deadline Cloud Submitter Information

submitter name: Cinema4D
submitter package name: deadline-cloud-for-cinema4d
submitter package version: 0.11.4
host application name: Cinema 4D
host application version: '2026303'
additional info:
release date: June 18, 2026
deadline dep versions:
deadline: 0.60.4
boto3: 1.43.71
click: 8.4.2
deadline-job-attachments: 0.1.3
psutil: 7.2.2
pyyaml: 6.0.3
qtpy: 2.4.3
typing-extensions: 4.16.0
botocore: 1.43.71
pyside6-essentials: 6.8.3
os name: macOS
os version: 26.6.2
os architecture: arm64
python version: 3.11.4
qt version: 6.10.3

Attaching logs from this test as well.

hims-creative farm_Spot-Instance-hims-creative queue_session-1a083a5aff4c4d0f993f86aa11f25e73.log

[karthikbekalp]

Hi @mlupo-hims ,

Thanks for sharing your findings. This is interesting because I'm not aware of any color changes prior to 0.12.1 release.