Hey all,
I have a problem with Deadline 10.4.2.2 and Cinema 4D 2026.1.0.
I switched to 2026.1.0 and now I notice that Deadline is rendering strangely. I have a scene in AcesCG and want to render it as 32-bit OpenEXR. When I render the scene in TeamRenderer in Cinema 4D, the image is a true 32-bit image, but as soon as I render it with Deadline, I only get a 16-bit image, which is disguised as a 32-bit image. When I open the image in Photoshop, it still says 32-bit, but when I try to darken the highlights with curves, they break out.
Does anyone else have the same problem?
I rendered the same scene last month with the previous version of Cinema, and everything was fine there. (Unfortunately, I can’t show it due to NDA.)
And i cant switch the Cinema version to the old version, because we have now Jobs in the new Version of Cinema…
So, to summarize: When I render with Deadline, the image comes out as a 32-bit image, but it doesn’t have the dynamic range of a real 32-bit image. When I render with TeamRender, the image comes out correctly.
I also updated the submitter and the repository, but that didn’t help.
It would be really nice if someone could help.
Best regards to everyone!
Everything works perfectly in Cinema4d 2025. Strange
Are you using the RS Direct output, or are you saving via the standard C4D “Save” dialog?
I am using the cinema saving…
Try outputting through the RS Direct Output & see if the same thing occurs.
I think this is your thread.
Is this the solution?
But i will try your suggestion with RS direct output.
Best
Tobi
That specific issue was in regards to a gamma shift when attempting to bake the ACES transform into the rendered EXR (as opposed to doing the color transform in Comp). I didn’t look into the bit depth at all, so not sure there.
I installed your fix and now it works!!!
Now the renderings are back to being true 32-bit!! Hey, thanks so much for your work.
1 Like
I noticed that when you use “My Render Setting” from, for example, an old Cinema 4D 2025 scene in 2026.1.0, it works, but as soon as you create a new scene and use “My Render Setting,” it doesn’t work in 2026.1.0.
Could you share screenshots of the settings you’re using in:
- The C4D “Save” dialog
- Redshift → Globals → Color Management
- C4D Project Settings → Color Management
I’m not sure whether my fix would do anything for bit depth, as it was intended for a gamma adjustment.
I’m surprised myself. I rendered a 32-bit image without the fix and ended up with a darker image in which I no longer have any detail in the white values when using curves in After Effects, for example. With the fix, the renderings look the same as when I render with TeamRender or on my own computer.
I also spent hours comparing the My Render Settings from 2025 and 2026.1.0. They are 10000% the same, but the problem only occurs with the My Render Settings from 2026, without the fix. Maybe it’s some kind of bug in Cinema.
No idea, but it works now in any case! 
Here are the screenshots.
If I understand things correctly: your workaround is importing render settings from 2025 & using them in 2026.1?
In your 2025 settings was Bake View Transform and/or Compensate for View Transform enabled? Or were you rendering images in ACES color space and doing the transform in AE?
I don’t have any more workarounds, thanks to your fix somehow…
Now I don’t do anything else and just render. I am not using bake view transform.
I rendered the images in the ACES color space and did the transformation in AE.
before I inserted the code from you I noticed, funnily enough, that the error disappears when you open the render settings from 2025 in 2026, and then it works.
Sorry for my poor English if I can’t explain it very well.
All good; glad its working!
1 Like
Sorry for the rookie question but how do you get C4D/Redshift 2026 to render with deadline?
I’ve tried adding 2026 to the versions in the Cinema4DSubmission.py file and in the Cinema4d.param file adding 2026 to the RenderExecutable paths but I just get a redshift error with the classic “out of memory”
could you share the error massage and the param + submission .py?
Yeah sure thing, thank you! I’ve zipped them up for you
Deadline Files.zip (13.7 KB)
1: in the submission.py is the wrong (") letter.
Maybe it works now.
Another thing: try to open Cinema4d Commandliner 2026 and press Yes at the end.
Hope that helps
That’s a great spot! I’m remoting in from a mac to windows server so the " turns into a '.
I’ve given that a go but still get the same error unfortunately. I’ve also done the commandline thing and told it to use the maxon app (1 option).
Is there a certain way to manage the redshift installs? I know C4D have their own whereas redshift just has the one folder. It would be great if these could be version managed. I don’t know if I’m just getting that part wrong.
I’ve managed to get C4D 2024 running on deadline but can’t get 2025 or 2026 to work without that out of memory error. This is running the latest deadline installation V10.4.2.3 on the server and client
A bit late to the party, but the index needs to be changed on the second one as well.
