Hi.
I have recently started using Xref in my workflow.
And i came across this strange behavior when submitting recent project to deadline.
The larger construction who is loaded in to the cinema4d file with Xref in generator mode. Is flickering around.
This image is the correct one and deadline rendered the first 45frames correctly before it started going crazy
Here is some of the faulty looking frames. Here is 4 different ones, but there is about 10-15 different combinations of material strangenesss xD
The total sequence is 200 frames.
So 0-45 is fine 46-98 is crazytown, then it renders correctly again from 98-144 then funky town again from 145-200 with some correct inbetween.
The job was submitted from innside C4D with batch mode enabled.
The worker working on the job on deadline was my local computer. Rendering the frames localy works just fine. Also. Resubmitting faulty frames/tasks on deadline will render them correctly the second time. Witch gives me a read/load issues vibes… “Looking intensly at batch mode”
I am not able to do test before later today, so right now i am just making a list of things to test, unless someone have experience with this issue.
- Submitt with Xref merged in to the scene just to confirm its a Xref thing.
- Submitt with Xref not in generator mode incase that reads the xref differently.
- Submitt without batch mode to let cinema 4D start fresh at each frame. gonna be slower tho
Cinema4d 2025.0.1
Redshift 2025.0.2
Windows 10 x64
Cheers