Distributed Rendering 2 – Separate Asset Folders for Each Take

Hi everyone,

I’ve been using Distributed Rendering for a few years without major issues.
Since the latest update, however, I’m running into serious problems. I work on exterior scenes with lots of plants and grass, and a single product comes in many sizes and colors. I manage this via the Take System.

The main change is that for each Take, a complete, separate asset folder is now created. Over the weekend, this can easily result in 220 GB of data on the render servers. This never happened before the update. As a result, my render servers are now crashing every weekend!

Has anyone else noticed this behavior after the latest update? Is there a workaround or fix?

Hi @daCaMo Thank you for reporting this.

Please, let me know what’s the exact V-Ray and Cinema versions you are using?
Does this happen with a specific scene or with every scene you test?
Are you testing a newly created scene or an old one? If possible, could you test an old scene with your current builds and let me know if the issue reproduces again?

’m working with V-Ray 7.20.00 (always the latest update) and Cinema 4D 2026.1.3.

Right now I’m working on some older scenes, and the issue happens every single time I press the render button.
However, the same thing also happens in completely new scenes, so it doesn’t seem to be related to the specific project.

In every case, the files are always being written to the temp directory.

Any news regarding this problem?

Hi @daCaMo ,
The issue should be fixed in our stable V-Ray builds, available here Chaos