Deadline 10.3.2.1 Cinema 4d and Redshift

Deadline
1

I’m experiencing a persistent bug where random textures go missing on random

Troubleshooting Steps I’ve Tried:

  • Reinstalled Cinema 4D 2025.0.2, Redshift 2025.1.1, and Deadline 10.3.2.1 multiple times.
  • Disabled concurrent tasks: This fixed the errors but didn’t utilize all GPUs.
  • Assigned GPU affinity: Assigned specific GPUs per worker to avoid conflicts.
  • Split workers into groups: Grouped workers, but the issue persisted.
  • Attempted to launch multiple workers: Couldn’t create more than master and slave workers.
  • Checked permissions: Verified permission to launch additional workers.
  • Adjusted job submission settings: Tweaked settings without resolving the GPU usage issue.
  • Explored pool and group configurations: Investigated pools and groups to better organize workers.
  • Changed concurrent tasks on worker stations: Adjusted concurrent task settings to prevent resource conflicts.
  • Checked VRAM: Verified VRAM usage to ensure the GPUs weren’t overloaded.
  • Changed my NAS to a static IP address.

Despite all of these efforts, I am still encountering the same texture errors.

Will this get sorted or am i moving over to Royal Render forever?

2

Is this problem caused by the storage?

Can you convert this object/texture to an RS proxy and does it still lose the texture?

Do the logs reveal anything at render time?

3

Thank you anthonygelatka :slight_smile: I don’t think it’s storage; I think the Redshift Proxy would work, but it’s just more work. I think the root cause is the Blender material—one being Standard Material and one being Material. Mixing of Uber shaders. It renders fine with Royal Render, so I’m just using that until this bug is resolved on Deadline’s, C4D’s, and Redshift’s end.

1 Like
4

have you tried with the batch option unchecked in the submission form? I think this creates a copy of the file which may cause issues with path mapping, worth a try to see if the random texture loss is fixed

5

I’ve the same problem since two month here, with Cinema 2025.1.2 + Redshift 2025.2.2. using now the newest deadline 10.4.0.12. “Use Batch Plugin” breaks rendering entirely. Not using it, produces broken frames, no errors, just random frames with lost shaders, for some frames on some objects. This is true not only for shaders with textures, or other external resources, but also for just plain shaders. You can see, the wrong shaders are eighter a pure white material, or randomly the 50% grey cinema4d default material. This problem ruins every image sequence entirely. It’s hard to manually delete broken frames, or use automated tools on it, as every frame looks randomly different broken. Any ideas?

6

Hi, I have the same problem.
The 1st time it helped me was to completely change the operating system on all farms.
But after a while i got the same problem again.
Have you found a way to solve it ?

7

don’t know if this is the real reason of your problems but consider this. what is OS of your NAS? If you have non server versions of the Windows, then it has limited number of concurrent connections. Royal Render can copy all resources prior rendering to the local clients so it may look it works better than Deadline which renders things from original location. If your OS is linux there aren’t such limitations

8

Same problem here for quite some time. Not all the frames render with white materials only some. It used to work without any problems.
Anybody knows the fix?

9

I’m currently working with Maxon to try to fix this issue, as I’m experiencing it as well, but we’re having trouble reproducing it on Maxon’s end without using Deadline.

A couple questions for you all:

  • Which C4D/RS versions are you getting it with? For me C4D 2024 seems to be ok, with the issues starting with C4D 2025.
  • Are you rendering in such a fashion where each GPU on a render node renders its own frame? (I,e - GPUs-Per-Task at 1 and Concurrent Tasks ~4 (something higher than one).

My current suspicion is that its somehow related to the machines rendering multiple frames simultaneously with C4D 2025+ (or something in RS 2025+)

10

We are using the latest version of c4d and redshift. It used to work ok but that was a long time ago. We have been having those problems for the past year or even longer

11

Thanks! That helps. Are you rendering in such a fashion where each GPU on a render node renders its own frame? (I,e - GPUs-Per-Task at 1 and Concurrent Tasks ~4 (something higher than one).

12

Yes we are rendering multiple frames on multiple gpus. usually 1 frame per GPU

1 Like
13

Thank you for the clarification!